Page 1 of 2
Posted: Mon Jul 26, 2004 1:45 pm
by Acheron
got adsl today after 6 years waiting .. good thing i move in two weeks to start uni gg. anyway how do i config my router so Loial can join my games. We are sharing internet using Modem build in router and switch.. HOw do i avoid problem with him being FWED when joining MY game.
Posted: Tue Jul 27, 2004 5:28 pm
by Archer
If you're using NAT, only one of you can host on any Playmyth game. Set it to forward 3453 to one of your machines, and use that machine to host all the time.
Annoying, but such is the nature of NAT.
~J
Posted: Wed Jul 28, 2004 9:08 am
by Acheron
Archer wrote:If you're using NAT, only one of you can host on any Playmyth game. Set it to forward 3453 to one of your machines, and use that machine to host all the time.
Annoying, but such is the nature of NAT.
~J
Yeah I noticed that.. when i tried open his local IP for port 3453 it said; error unable to add NAT entry.. BUUUT thats is not the problem.. the problem is that he cannot join my game when I host.. Everybody else can but he gets fwed message,
Posted: Wed Jul 28, 2004 9:26 am
by Doobie
and you're sure your both behind an NAT router? cause that's not their normal behavoir.
Do either of you have any other firewall software running (including XP's built in firewall if you're using XP).
I suppose it could be worth trying to put the host machine in the DMZ in the router settings, but then you lose any benefit you would have gained from your NAT router.
Edited By Doobie on 1091036442
Posted: Wed Jul 28, 2004 9:36 am
by Acheron
from their site: "Services
• Bridging
• IP routing
• NAPT, DHCP, DNS
• Embedded firewall
• WAN protocol model:
- Routed PPPoE/PPPoA
- Relayed PPPoA and DHCP-to-PPP Spoofing
- Bridged Ethernet/Routed Ethernet
- Classical IPoA
• UPnP Internet gateway device including NAT traversal"
We are both using os x 10.3 we are both connected to this router using a switch.
Posted: Wed Jul 28, 2004 12:43 pm
by Doobie
Ok, this sounds significantly more complicated than your typical NAT router/firewall setup. Without actually looking at this stuff myself, i'm at a bit of a loss as to what to do next. I take it you don't have access to a DMZ (de-militarized zone) setting? You might have to get support from your provider.
just out of curiosity, what are your machines IP addresses?
Posted: Wed Jul 28, 2004 12:56 pm
by Orlando the Axe
I would check with the router's tech support, they should be able to help.
Posted: Wed Jul 28, 2004 4:13 pm
by Acheron
Hereis a picture of my main menys.. router
i went through everything without seeing anything named DMZ..
I called up my ISP.. "we have never heard bout this before, ITS NOT A PROBLEM IN OUR NET" LOL! gg
he also said "have you tried and restarted your computer and modem" 
lol
my comp 10.0.0.1 loials 10.0.0.2
Edited By Acheron on 1091050808
Posted: Wed Jul 28, 2004 9:58 pm
by Archer
I'd say the first step is to try to set up an intranet game of Myth. TCP/IP or Rendezvous, the choice is yours. Let us know if that fails.
~J
Posted: Thu Jul 29, 2004 2:37 pm
by Acheron
Archer wrote:I'd say the first step is to try to set up an intranet game of Myth. TCP/IP or Rendezvous, the choice is yours. Let us know if that fails.
~J
ok tested this:
Hosted myth2 TCP/IP game on my computer
From loials computer I first try to join the game using the IP we got together out to the net 80.x.x.x.x this is the IP other users see when they ping us probably we share this. Now i get firewalled!
Next i try join with 10.0.0.1 which is my local IP on the LAN.. now he gets into the game right away..
what does this tell?
Posted: Thu Jul 29, 2004 3:09 pm
by Doobie
It tells us that people outside your LAN can't join your host. But you already told us that's not true, and that only your brother can't join, others can join fine.
Seems to me there is some kind of problem with how your computers communicate with each other via your external IP (since the internal IP addresses worked fine). I have no idea what the solution might be, other than to say it's likely caused by a perculiar setup with your ISP.
Posted: Thu Jul 29, 2004 5:01 pm
by Archer
Basically, as Doobie said, it tells us that the problem is showing up somewhere when the connection gets put back to your external IP.
Just to double-check, are you absolutely sure the person hosting had 3453 forwarded to their machine? Probably yes, but last night I spent an hour trying to fix a problem on my computers that turned out to be caused by a similarly simple error, so it's worth checking
~J
Posted: Thu Jul 29, 2004 7:27 pm
by lank
i think i have this exact problem on my LAN, which connects to the outside world through a router with a NAT firewall. to connect to my machine from within the LAN, you have to use my machine's LAN IP (192.168.1.2), but external machines have to use my ISP-assigned IP. (i have port forwarding set up so that my machine can host to the outside world and not get firewalled.)
so if i host a tcp/ip game, my housemates can join using my local IP, and others can join using my external IP. problems arise when someone in the LAN hosts on a metaserver and someone else on the LAN tries to join that host. why? because the LAN client is trying to connect to a local machine using the external address. we can both join games hosted by other people at the same time, and problems don't seem to arise.
it seems similar with hotline servers and clients in this setup. if acheron sets up a hotline server and his friend tries to connect using the local IP it'll be fine (same if ach uses a client to connect to himself, too). however, if either of them tries to use the external address to connect, they won't be able to.
maybe there's a way around it, but i just don't know of it.
Posted: Thu Jul 29, 2004 8:15 pm
by CIK
Make a snap shot of your NAPT screen under Advanced setup. It's not unusual for local machines to not be able to join via your public IP address(the 80.xx.xx.xx one). But once you setup port forwarding for the Myth port(3453 people outside your network should be able to join ok).
Posted: Fri Jul 30, 2004 4:56 am
by Acheron
Archer wrote:Basically, as Doobie said, it tells us that the problem is showing up somewhere when the connection gets put back to your external IP.
Just to double-check, are you absolutely sure the person hosting had 3453 forwarded to their machine? Probably yes, but last night I spent an hour trying to fix a problem on my computers that turned out to be caused by a similarly simple error, so it's worth checking
~J
yes if portforwarding means that my local IP is open for 3453.. This works.. proved by that I hosted a game on playmyth last night,.
