Connecting to server running on the same ip adresses

[TGYoshi]

Yesterday I switched to a fiber optic network and I have a little problem running a server back up again.
It's basically opposite of 99.999% of the problems like this: Other people are able to connect to the server, but myself (on the same (LAN) IP) can't connect (Socket 10061 error). I'm using port 6660 for the server, 6661 for P2P and 6662 for XML-RPC. All are open. My own client is using some other random ports for their stuff, probably default ones.

Basically I'm unable to connect to a server on the same address, I was able to do so on my previous router/network. Any idea what's wrong here, or is there any way to connect to 192.168.2.1:6660 while other just join normally?

Additional information:

Bump.

I found this topic: http://www.tm-forum.com/viewtopic.php?f ... &sk=t&sd=a - didn't work tho.
I also figured out my new router does not support NAT-loopback. The old one does.
I do not care about LP earned on the server, not for myself and not for anybody else.
I'm unable to find the server in the LAN list as well, also using port 2367.
Other players can connect, and some weird port-check website still tells the ports are open.

EDIT: Got it working. I messed around with client ports, now I can connect via LAN, and others normally.

[frymaster]

that error code means your connection was actively rejected by the other party (it's the actual error code from windows, so it's google-able). I'm assuming you are behind a NAT router? 99% of home routers won't port forward a connection from the LAN back to the appropriate ip:port on the LAN (because it's technically a different firewall rule to do so) - chances are your client is trying to connect to a trackmania server running on your router instead

I don't think you can do direct IP connect in TM2; I've not seen the URL format for it, at least. You might be able to use the LAN tab to find the server, but I suspect, with it being the same computer, you might not.

[TGYoshi]

Yes, it's a NAT router afaik.
The set-up of the stuff around here is the same as before, the only thing that has changed that the router is a new thingy and instead of an antenna or so on it, it got a connection to the fiber optic network. Router - PC is wired like before.
I might try translating the port to some alternate number, to see if the conflict gets fixed by that. I'm afraid the server gets confused by that tho, since there is no setting related to that. This wasn't required before tho.

And yes, you can direct-ip connect: #join=111.222.33.44:1234. This doesn't seem to work for local ip's tho.
And no, it's not in the LAN tab in TM itself, already tried looking there.

[frymaster]

if your router's changed I'm guessing the old one was one of the 1% that would take packets coming from inside the LAN with the address of the WAN IP and NAT them back to the LAN. Most won't do this

[TGYoshi]

I've always hated my old router. And my new one as well btw.

But allright, maaaaaany people got a server to work anyway.. I did it myself for a lot of people through teamviewer etc., the only part where it might fail is port-forwarding. But I got that working. They are able to connect to their own server as well. Somehow I am not.

[TGYoshi]

Bump.

I found this topic: http://www.tm-forum.com/viewtopic.php?f ... &sk=t&sd=a - didn't work tho.
I also figured out my new router does not support NAT-loopback. The old one does.
I do not care about LP earned on the server, not for myself and not for anybody else.
I'm unable to find the server in the LAN list as well, also using port 2367.
Other players can connect, and some weird port-check website still tells the ports are open.