Revision history  [back]

Hello ,

I have issue with TCP/IP server that exchange data with clients dcl (xml) format , the issue occurs once a day , sometimes twice , and goes as follows suddenly all clients cannot connect to the server , while on the server itself, the server is still appear to be listening and seems to be operational , but no connection could be done. During normal communication the data exchange finish with RST deliberately to avoid "TCP Time wait" as attached below https://drive.google.com/open?id=0B0asUZ-L8gUfWkVNc3pwZ1dMXzQ

The server run under Windows 2008R2 , we made sure that firewall and base filtering service is off During the Wireshark trace on it , we can see that prior to the indecent several clients announce Zero Window https://drive.google.com/open?id=0B0asUZ-L8gUfLU9mZGNwV1V1UWs

https://drive.google.com/open?id=0B0asUZ-L8gUfbEdTczFDVjFuSkk

, but i don't know if its related , During the incident we can see clearly that's server kind of rejecting connection but we not sure of the source , since as for server logs seems to operate ok, and he exchange data with others same type of servers during the clients outage as seen blows image. https://drive.google.com/open?id=0B0asUZ-L8gUfaUk1aXNxOWQ5ZTQ

Now we are kind of stucked , and hope someone could pin point something I missed trace is shared here Thanks Please advice

[trace Sample](https://drive.google.com/open?id=0B0asUZ-L8gUfajlOX25vRXo1NUE)

Hello ,

I have issue with TCP/IP server that exchange data with clients dcl (xml) format , the issue occurs once a day , sometimes twice , and goes as follows suddenly all clients cannot connect to the server , while on the server itself, the server is still appear to be listening and seems to be operational , but no connection could be done. During normal communication the data exchange finish with RST deliberately to avoid "TCP Time wait" as attached below https://drive.google.com/open?id=0B0asUZ-L8gUfWkVNc3pwZ1dMXzQ

The server run under Windows 2008R2 , we made sure that firewall and base filtering service is off During the Wireshark trace on it , we can see that prior to the indecent several clients announce Zero Window https://drive.google.com/open?id=0B0asUZ-L8gUfLU9mZGNwV1V1UWs

https://drive.google.com/open?id=0B0asUZ-L8gUfbEdTczFDVjFuSkk

, but i don't know if its related , During the incident we can see clearly that's server kind of rejecting connection but we not sure of the source , since as for server logs seems to operate ok, and he exchange data with others same type of servers during the clients outage as seen blows image. https://drive.google.com/open?id=0B0asUZ-L8gUfaUk1aXNxOWQ5ZTQ

Now we are kind of stucked , and hope someone somone could pin point something I somthing missed trace is shared here Thanks Please advice

[trace Sample](https://drive.google.com/open?id=0B0asUZ-L8gUfajlOX25vRXo1NUE)
[link text](https://drive.google.com/open?id=0B0asUZ-L8gUfajlOX25vRXo1NUE)

Hello ,

I have issue with TCP/IP server that exchange data with clients dcl (xml) format , the issue occurs once a day , sometimes twice , and goes as follows suddenly all clients cannot connect to the server , while on the server itself, the server is still appear to be listening and seems to be operational , but no connection could be done. During normal communication the data exchange finish with RST deliberately to avoid "TCP Time wait" as attached below https://drive.google.com/open?id=0B0asUZ-L8gUfWkVNc3pwZ1dMXzQ

The server run under Windows 2008R2 , we made sure that firewall and base filtering service is off During the Wireshark trace on it , we can see that prior to the indecent several clients announce Zero Window

, but i don't know if its related , During the incident we can see clearly that's server kind of rejecting connection but we not sure of the source , since as for server logs seems to operate ok, and he exchange data with others same type of servers during the clients outage as seen blows image. Now we are kind of stucked , and hope somone could pin point somthing missed trace is shared here Thanks Please advice

[link text](https://drive.google.com/open?id=0B0asUZ-L8gUfajlOX25vRXo1NUE)

Hello ,

I have issue with TCP/IP server that exchange data with clients dcl (xml) format , the issue occurs once a day , sometimes twice , and goes as follows suddenly all clients cannot connect to the server , while on the server itself, the server is still appear to be listening and seems to be operational , but no connection could be done. During normal communication the data exchange finish with RST deliberately to avoid "TCP Time wait" as attached below The server run under Windows 2008R2 , we made sure that firewall and base filtering service is off During the Wireshark trace on it , we can see that prior to the indecent several clients announce Zero Window

, but i don't know if its related , During the incident we can see clearly that's server kind of rejecting connection but we not sure of the source , since as for server logs seems to operate ok, and he exchange data with others same type of servers during the clients outage as seen blows image. Now we are kind of stucked , and hope somone could pin point somthing missed trace is shared here Thanks Please advice

[link text](https://drive.google.com/open?id=0B0asUZ-L8gUfajlOX25vRXo1NUE)

Hello ,

I have issue with TCP/IP server that exchange data with clients dcl (xml) format , the issue occurs once a day , sometimes twice , and goes as follows suddenly all clients cannot connect to the server , while on the server itself, the server is still appear to be listening and seems to be operational , but no connection could be done. During normal communication the data exchange finish with RST deliberately to avoid "TCP Time wait" as attached below The server run under Windows 2008R2 , we made sure that firewall and base filtering service is off During the Wireshark trace on it , we can see that prior to the indecent several clients announce Zero Window

, but i don't know if its related , During the incident we can see clearly that's server kind of rejecting connection but we not sure of the source , since as for server logs seems to operate ok, and he exchange data with others same type of servers during the clients outage as seen blows image. Now we are kind of stucked , and hope somone could pin point somthing missed trace is shared here Thanks Please advice

[link text](https://drive.google.com/open?id=0B0asUZ-L8gUfajlOX25vRXo1NUE)

Hello ,

I have issue with TCP/IP server that exchange data with clients dcl (xml) format , the issue occurs once a day , sometimes twice , and goes as follows suddenly all clients cannot connect to the server , while on the server itself, the server is still appear to be listening and seems to be operational , but no connection could be done. During normal communication the data exchange finish with RST deliberately to avoid "TCP Time wait" as attached below The server run under Windows 2008R2 , we made sure that firewall and base filtering service is off During the Wireshark trace on it , we can see that prior to the indecent several clients announce Zero Window

, but i don't know if its related , During the incident we can see clearly that's server kind of rejecting connection but we not sure of the source , since as for server logs seems to operate ok, and he exchange data with others same type of servers during the clients outage as seen blows image. Now we are kind of stucked , and hope somone could pin point somthing missed trace is shared here Thanks Please advice

[link text](https://drive.google.com/open?id=0B0asUZ-L8gUfajlOX25vRXo1NUE)

Hello ,

I have issue with TCP/IP server that exchange data with clients dcl (xml) format , the issue occurs once a day , sometimes twice , and goes as follows suddenly all clients cannot connect to the server , while on the server itself, the server is still appear to be listening and seems to be operational , but no connection could be done. During normal communication the data exchange finish with RST deliberately to avoid "TCP Time wait" as attached below The server run under Windows 2008R2 , we made sure that firewall and base filtering service is off During the Wireshark trace on it , we can see that prior to the indecent several clients announce Zero Window

, but i don't know if its related , During the incident we can see clearly that's server kind of rejecting connection but we not sure of the source , since as for server logs seems to operate ok, and he exchange data with others same type of servers during the clients outage as seen blows image. Now we are kind of stucked , and hope somone could pin point somthing missed trace is shared here Thanks Please advice

[link text](https://drive.google.com/open?id=0B0asUZ-L8gUfajlOX25vRXo1NUE)