Forums Connection Issues mirc shows servers IP as my host IP

This is a strange one folks - I hope someone can help me.
Recently got Time Warner Cable - never have a problem with mirc -been running for years. When I went to connect to our IRC server, it wasn't connecting properly and dropping often with a software abort.

Suddenly I noticed during the opening preamble, that the mirc server was reporting that it couldn't resolve my hostname and was using my IP instead. Nothing all that unusual there.. except.. the IP it was reporting belonged to the IRC server - not me!

This is our IRC server, I am one of the admins. When the incoming connection is seen on the server side, it is correctly identifying my public IP (Client connection on port 6667: Marsman@my_public_ip). What I see coming back from the server is: Welcome to the blah IRC Network Marsman!marsman@irc_server_ip

I have tried reverse DNS lookup from the server for my IP and it IS able to resolve my hostname(despite that it claims it can't) - but even if it doesn't - WHY IS IT RETURNING THE SERVER'S IP ????

Not only does it do this for our IRC server, It has the same problem with other IRC servers. I've tried multiple machines from here - all have the same issue with this Time Warner Connection. The other admin of our IRC server also has Time Warner - no problem (though he is in a different IP range than I am).

I've talked to Tier 4 support at Time Warner - they are just as baffled as I am - nothing appear wrong on their end - yet it is specifically this connection. If I hit the unlocked WiFi in the area, it works fine.

It's not just the preamble text - it actually sets my local IP and hostname to the irc server's when I connect. Yet I can watch my incoming connect attempts from server come in as my username@my_public_ip - It's just weird!!! Does ANYONE have ANY idea how this is happening and what I can do to fix it?

If this is happening with different IRC servers, the most likely reason is that the IP address was only recently assigned and is still propagating, so a reverse DNS may or may not work until the propagation is complete, which can take up to two days.

If an IP address is specified in the numeric 001 reply (only some servers include it), mIRC will use it as your local IP address, since that is what it should be, instead of performing /userhost later on. I was not aware that some servers replace it with their own IP address if a reverse DNS fails. Unfortunately that makes the reply unreliable. It may be that the server does the same to /userhost replies as well, which would mean that mIRC would be unable to lookup your local IP address.

No - this address has been out for months now. It is well propagated. I have done a reverse lookup on the ip on the irc server and it resolves fine. Even if it couldn't find the host name to use, it should still use the inbound ip - which strangely the server sees correctly inbound, but what comes back from the server to mirc is me@server_ip - which then results in a software abort after a few seconds.

At this point, I am not certain which side is to blame - is it mirc since the server sends back it's own IP which mirc then uses as local host ip? Would almost seem so as inbound connection from the server side report me connecting from my true public ip. It's what is coming back from the server to mirc that is incorrect. Do you think if I used a script to force my local ip back to my true public IP that it would then work?

Well I just used the /localhost command in my perform to force my localhost and ip to the correct value - still disconnects. So it would appear it's not just the mirc side. Really don't understand what is happening here as there appears to be conflicting information.

Since you said this is your server, you should check 001 like Khaled mentioned. Make sure it's returning the right information. See if that solves your IP problem.