Forums Connection Issues My debugging info

for some very odd reason, my connections have been refused and/or timed out from a majority of the servers i try to connect to. this was never an issue before.

this is from one particular server that i'm trying to join:

-> irc.gamesurge.net NICK Asylo39130
-> irc.gamesurge.net USER sedts "" "irc.gamesurge.net" :sddfs
<- NOTICE AUTH :*** Looking up your hostname
<- NOTICE AUTH :*** Checking Ident
<- NOTICE AUTH :*** Couldn't look up your hostname
<- NOTICE AUTH :*** No ident response
<- PING :808500153
-> irc.gamesurge.net PONG :808500153
<- :Slim.NY.US.GameSurge.net 513 Asylo39130 :Your client may not be compatible with this server.
<- :Slim.NY.US.GameSurge.net 513 Asylo39130 :Compatible clients are available at http://www.gamesurge.net/links/
<- ERROR :Closing Link: Asylo39130 by Slim.NY.US.GameSurge.net (Registration Timeout)
-> 208.146.35.105 NICK Asylo39130
-> 208.146.35.105 USER sedts "" "208.146.35.105" :sddfs
<- NOTICE AUTH :*** Looking up your hostname
<- NOTICE AUTH :*** Checking Ident
<- NOTICE AUTH :*** Couldn't look up your hostname
<- NOTICE AUTH :*** No ident response
<- PING :1319463114
-> 208.146.35.105 PONG :1319463114
<- :NuclearFallout.WA.US.GameSurge.net 513 Asylo39130 :Your client may not be compatible with this server.
<- :NuclearFallout.WA.US.GameSurge.net 513 Asylo39130 :Compatible clients are available at http://www.gamesurge.net/links/
<- ERROR :Closing Link: Asylo39130 by NuclearFallout.WA.US.GameSurge.net (Registration Timeout)

this happens with almost every server i try to connect to. gamesurge is just the example i decided to use. on some servers i get both the connection timeout and a ping timeout upon reconnecting.

i am not behind a firewall, but i am behind a router. nothing new was inserted or taken out of the loop. i was able to connect just fine to any irc server with the setup i have right now.

i have tried forwarding the ports but with no success. i have tried setting my pc up as a DMZ host (allowing all traffic to flow through), and still no success. i also unchecked all the options that have anything to do with filtering any traffic, including ident port 113.

when i take my router out of the loop and connect directly to my modem, i get about a 50% success rate. this includes pinging and tracert.

now i'm aware it's most likely my router, but what gets me is a lot of the time i still get the same error when directly connected through the modem.

so i've tried a thousand times to get this working again on my own, and i'm not having any luck. hopefully someone here can assist me, and i'll do my best to pay it forward if someone else is in a situation like this.

OS: Windows XP Home & Windows XP MCE
mIRC: latest version & 6.12
Router: WRT54G v5; firmware v1.00.9 (6/2006)
ISP: ATT ADSL (modem also up to date)

EDIT: i can ping and connect to some servers just fine, the same goes for tracert. this is all done with the router in the loop.

sorry. another edit: the ones that i pinged successfully won't connect via any irc client.

in dos
IPCONFIG /flushdns

if no help?

Then in the WRT54g see what the WAN ip is, is it your internet IP or is it another LAN ip 192.168.?.? or 10.?.?.? by any chance? Most adsl modems are also routers, yours maynot be, but most are. It might eb a problem in the adsl/router that is compounding as it has to pass through the linksys as well.

You don't show what your IP is, but:

The servers are telling you what their problem is - they can't ident you.

Set up a static internal IP on that computer. (Linkys won't forward to leased IPs, nor should they.)

Forward 113 TCP to that IP.

The reason things may have changed for you recently is that the servers you're trying to connect to may have recently changed their policies and now refuse unidented connections. (BTW, if your modem does NAT, you'll still have problems. The proper forum for this sort of thing, IP problems and setting up routers, is PortForward.)

He also said, he has full dmzed all ports and it doesnt work, removed the router and it does work 50% of the time, which if hes being accurate, would lead me to beelive he already has ident on or the server dont really care if he doesnt. Still ya never know.



Most Linksys well forward to WHATEVER IP they are told to forward too, be it static or dynamicly directed, I have never had a problem with them doing this, what linksys are u using?

The newer firmware on the WRT54x routers usually doesn't.

Hmmm good point, the one I have is a v3.1 with Firmware Version : v4.00.7, but we buy new ones often for places.
I might consult linksys, if they have done stupid things to disable stuff.

They were doing stupid things - they've fixed it now.

What sense does it make to forward ports to a leased address when there's no way of knowing what address that computer will get the next time it boots? You'd have to reset the port forwarding daily in some LANs.