[Andre]

I have a theory about this. It may be that the Shrapnel server hosting our Lobby server is requiring all connections to have a hostname associated with the IP address that is trying to connect. I noticed that the IP address that NightStalker is using does not have a hostname. Again, I'm not sure this is actually the problem, but it I've seen this type of behavior from servers before now that I think about it.

I've contacted a couple other users that have IP addresses w/ no associated hostname, and have not played an online game of LOL v1.0, and I hope to hear back that they can confirm the issue for themselves or disprove the theory by connecting (assuming they connect from the same IP as when they signed up). It's kind of a longshot.

NightStalker, is it possible for you to try connecting from a computer that actually has a hostname for itself? You can test this by running "ipconfig" and grabbing your IP address for the ethernet adapter in the report, then run "nslookup [YOUR_IPADDRESS]" to see if there's an associated hostname for your IP. If it does have a name for that IP, then I'm guessing you could connect from that computer.

The reason it may have worked before is that you were connecting to the server that was running on our DEV box back in the day, and not the new Shrapnel server that v1.0 is running on. This new server may be enforcing this hostname rule on a level above our application. I'm assuming you have the same internet connection/provider now that you did a few months back during the BETA when you could connect.