Failed to connect to lobby

[Perryman]

-------------------------------------------------------------------------------------------------------------------
Windows Version (and Service Packs): XP Pro SP2
Processor Speed: 2.01 GHz
RAM: 1 GB
Video Card (Make and Model#): ATI RADEON X800 GT
Sound Card (Make and Model#): Nvidia Nforce Audio (integrated, details unknown?)
Connection Type (Dialup, Cable, DSL, other): DSL
Modem (Make and Model#): Actiontec GT701-WG
Router (Make and Model#): n/a -> integrated with DSL modem
Internet Service Provider(company name): Qwest
Location(State/Province/Locality, and Country): Idaho, USA

Problem Encountered at Step #: 8
Which Program (ASGS/Allegiance): Allegiance
What Error Message: Failed to connect to lobby
Comments (What you tried, description, etc):

-I have installed the latest updates for SP2.
-I do not use any additional firewalls and have confirmed windows firewall is set to OFF
Step 2. Devices
-I have my local IP address configured as DMZ, and in addition have the required ports forwarded to my IP after initially having connection issues.
-I couldn't locate a uPNP option in my DSL modem configuration [firmware current as of last month]


I'm really at a loss here and will appreciate any help. The MOTD comes up fine and patched me up the first time I ran it.
I have a straightforward internet connection at home and don't usually have any problems with connectivity for gaming. Thanks in advance for any ideas as to what I should try to do.

-Perryman
-------------------------------------------------------------------------------------------------------------------

[Perryman]

Ok, perryman. What you're going to want to do is randomly fiddle with settings. First, try turning on windows firewall, getting the message, allowing it, and trying again. When that doesn't work, try turning off your DMZ settings.

It worked???

Some sort of conflict with the ports being forwarded but already being forwarded by the DMZ perhaps? Firewall is off either way on the modem. You guys think this is a DSL modem / firmware issue?

[GreyVulpine]

QUOTE (Perryman @ Aug 15 2006, 02:41 AM) It worked???

Some sort of conflict with the ports being forwarded but already being forwarded by the DMZ perhaps? Firewall is off either way on the modem. You guys think this is a DSL modem / firmware issue?

Glad to see you've solved it on your own.

Port forwarding is really the process of telling the modem/router, "Hey, when some packets hit through this port(s), send it over to this IP address". DMZ is a more... brute force method of that same deal except it'll forward ALL ports to the one IP address that you specified. Now, when you DMZed and set a port forward rule, that modem/router probably just conked out...

Basically the DMZ is there for situations where port forwarding just doesn't work.. and you just say "Fug it" and set a DMZ, accepting the increased risk of intrusion for convenience.

-GreyVulpine

[Perryman]

Well, I originally had the DMZ set for when I was sharing using the routing of the DSL and my router configured as a switch. He'd set up whatever port forwarding he needed, and I set up DMZ, and it had worked fine for me, up until this instance. In my thinking, DMZ should basically make it the same as if there were no "router features" in my modem. I guess that wasn't the case here.