Failed to connect to lobby

misbehavingmal · Post by **misbehavingmal** » Mon Sep 11, 2006 9:06 am

I can't connect to the lobby either, the current time is 1:58 AM (PST) on Monday, September 11, 2006.
I'm not a technical newbie (about to take the A+ certification tests, so no "Do you know what PORT FORWARDING is?"), with my router set to DMZ hosting for my Wireless G connected computer.
A few questions:
1. How sensitive is the connection to lobby to packet loss? (1-10 packets lost/garbled=dead connection?)
2. Is the server ever down ?(At late hours and such)
3. What are you wearing?

All these questions are of the utmost urgency As far extreme late night gaming and lewd encounters go

Another note: I can see the MotD and I was able to auto-update. If the lobby, MotD, and Auto-Update servers are one and the same, and I am not able to connect to lobby then it is probably some odd configuration phenomena.
So...are they?

Post by **Raveen** » Mon Sep 11, 2006 11:56 am

Hi Mal, first off, you'd be better posting a new thread for all help requests. Hopefully one of the mods will split this off though.

As for your questions, I can't help you with 1) but for 2), the servers do occasionally go down, but not often and not with any regularity (no 22:00 off for 15min servicing or anything).

Beyond that the helpline guys will want you to post your specs according to the posting template in the readme if you're still having trouble.

ImmortalZ · Post by **ImmortalZ** » Mon Sep 11, 2006 1:34 pm

The MoTD and Autoupdate work on the the normal port 80 (HTTP). So you'll be able to see that without port forwarding. If you could complete the template in the READ ME FIRST and post it in a new topic, we'll be able to better assist you.

Thanks.

misbehavingmal · Post by **misbehavingmal** » Tue Sep 12, 2006 7:49 pm

Allegiance doesn't like DMZ Hosting, you have to manually forward the ports and turn off DMZ, which is extremely odd, considering DMZ hosting is the equivalent of a direct connection, with no NAT interference on the ports.

ImmortalZ · Post by **ImmortalZ** » Tue Sep 12, 2006 8:27 pm

We've found out over the years that whenever Alleg misbehaves, its sign of something else wrong with the system. Assume your router sucks /tongue.gif" style="vertical-align:middle" emoid=":P" border="0" alt="tongue.gif" />

So, did you manage to get in?

Psychosis · Post by **Psychosis** » Tue Sep 12, 2006 9:30 pm

when in doubt, try toggling the uPnP option, for some reason that tends to work when other things dont.

misbehavingmal · Post by **misbehavingmal** » Wed Sep 13, 2006 6:03 pm

Yes I got in, but I had to turn off DMZ hosting. Like I said, it just doesn't like it. Some things don't work with DMZ hosting, like Quake III, you can't run a server with DMZ hosting on.

Post by **Raveen** » Wed Sep 13, 2006 6:45 pm

As far as I can tell Alleg picks any and all reasons to be contrary about connecting. The fact that it doesn't like DMZ doesn't surprise me in the slightest.

At least you got in /mrgreen.gif" style="vertical-align:middle" emoid=":D" border="0" alt="mrgreen.gif" />

ImmortalZ · Post by **ImmortalZ** » Thu Sep 14, 2006 6:23 am

We should keep the non-NAT Alleg exes around as "The best network/system stress tester on the planet". /mrgreen.gif" style="vertical-align:middle" emoid=":D" border="0" alt="mrgreen.gif" />