Bad response from server (not rc1 vs rc2)

[gvolpicelli]

Here's the setup, I have 4 machines on my netgear router, all of them are win2k sp4. My server has port 8767 open to it, and I have been using the server for about 2 months connecting from my gaming machine. No problems at all. I have a buddy who connects to it using the external ip addres, and he has no trouble either.

So I set up a ts2 client on a different machine behind my router and am getting the "bad response from server" error when I connect. I can still connect fine using the client on my other machine.. The server is set up with no password, no registered users, no restrictions.

So I uninstalled both the server and the clients, rebooted the machines, downloaded the newest versions of both and still get the same problem from only one of the client machines. I have never seen an (rc1) client or server version, so I am absolutely 100% sure this is not the issue. I downloaded the newest versions as of ten minutes ago. I can connect to server version 2.0.19.40 using client version 2.0.29.47 on one machine, but not on the other. I can ping the server, the server can ping me. I have the exact same protocols on all machines, and I don't use any form of software firewall. All three machines are behind the router so I am using the internal ip addresses. my server is 192.168.0.3 the clients are 192.168.0.2 and 192.168.0.5. I have tried specifying the port number at the quick connect screen, and tried using the external ip address, but since the other client works with just the ip there's no reason why I should have to add extra/different info for this one. I have rebooted my router as well.
Any ideas?

[woutur]

It's a router problem. If you have moved the server to another computer you need to tell your router that you don't want packets forwarded to the first computer anymore but instead need to be forwarded to your new box. That would take care of the external IP being forwarded.

For the internal network: that's odd and I don't have a reply to this yet.

[gvolpicelli]

The server hasn't moved machines. I have 8767 still forwarded to the same internal ip address. The server shows itself as 192.168.0.3 and the dhcp table from the router administration webpage shows the same ip address for that machine. Two people can connect to my server from outside using my external ip address, I can connect to it from inside with one machine using the internal ip address, but not the other machine. It's very odd.

[gvolpicelli]

Here's the log

27-07-03 15:45:02,404,ERROR,ProcedureInfo,Client Open,EidSocket: Socket Error # 10061
Connection refused.

[gvolpicelli]

I also just rebooted the router, rewired the machines, got new internal ip addresses, released/renewed both machines after rebooting them just in case. Then I redid the port forwarding for the new address, reinstalled the server and client, and I still get the same error from that log. I can still connect from the other machine with the new internal addresses, and my buddy can also connect from down the street..

[SatanClaus]

http://www.sockets.com/err_lst1.htm#WSAECONNREFUSED

what does the server.log say?