NT to 2000 TCP/IP issue

[glwatson]

I have an application that was written on NT It uses Sockets and TCP/IP to communicate to a real time system via a dedicated IP address and ethernet cable.

Works fine on NT.

Migrate to Win2000 professional.

The general communications seem to work fine.

However, we have a reliability test that sends a series of messages down the pipe and are then looped back from the application at the far end. We then check for errors.

This test takes FOREVER and we start seeing errors in the communications sent back.

Is there a Win2000 setting, security level, whatever, that needs to set/disabled to allow this to work as it does on NT?

[evilmrb]

Have you tried Microsoft Knowledge Base article 244826?

http://support.microsoft.com/?id=244826

Mark B