Hi, I have a windows 2000 client, which is using JNDI to make TCP/IP socket connection to the LDAP server on solaris machine. I'm having the following problem: 1) Quite frequently, I was receiving CommunicationException in JNDI ( Meaning, the socket connection is reset by peer) on the client application. After debugging through network snoop of the server, I found out that, once in a while, the client is sending "Rst" requests to the server. So, the next time, a query is performing using the stale connection, we get a "socket connection reset by peer" exception. The connection reset is not being initiated by the application using JNDI definitely. But, somehow, the underlying TCP/IP driver on Windows 2000, is sending Rst request to the server. Hence, the connections are being reset and the next query is having a stale connection. My concerns are: 1) As to why the Windows 2000 client is sending these reset requests, without being initiated by the client ? 2) I went through some of the documentation, could not find any info on any issues with JNDI on Windows 2000. I'm using JDK 1.3.1 version. 3) The funny thing is that, this client always talked to another Solaris server, and never had these problems. Now, we recently changed the server behind to another Solaris box. I do not understand as to why the client suddenly reacts to the change on server and keeps sending these Reset requests. Any thoughts ?