by Mike van Bokhoven >> Wed, 5 Jan 2000 4:43:42 GMT
Hi all,
Just a quick question about some strange TCP/IP behaviour.
A short time ago, I wrote a simple listen server, using Jade's TcpIpConnection class. This worked fine; I initially tested it on Win98, using the Telnet client as the client, then later, writing my own client in Jade.
I have now upgraded to Windows 2000 RC2, and find that this no longer behaves as it used to. My Jade client, run from the same node as the server, still connects fine to 127.0.0.1, but will no longer connect to my external IP address. And, if I start another Jade node on the same machine, neither 127.0.0.1 nor my external IP address respond to the client. Similarly, Telnet simply responds with 'Connect Failed' to either. NT4 behaves identically to 2000. A test on a Win98 machine verifies that everything still works fine in that situation.
So, my question is: Does anyone know why this is happening? It appears that there is some difference in the behaviour of TCP/IP between Windows 98 and NT4/Windows 2000 as far as Jade is concerned. If someone is able to shed some light on this, I'd be very grateful.
Mike.