mpossible
asked on
Client Access Disconnects
We are experiencing clients being disconnected at random times but frequently.
I have worked with both Cisco and IBM and am on my own now. I would like to know how to proceed.
PC5250 Traces (IBM Client Access Traces) show the the Client (User's Computer) is receiving a Socket Error 10054 (Connection reset by peer)
the TRCCNN IBM server trace shows the ACK for the RST on the server.
Wireshark shows that Client is requesting a Retransmission .
However we have multiple clients that are experiencing this and it just started out of the blue about a month ago. I think the problem might be application related but i'm in the dark on how to troubleshoot something like that.
I have worked with both Cisco and IBM and am on my own now. I would like to know how to proceed.
PC5250 Traces (IBM Client Access Traces) show the the Client (User's Computer) is receiving a Socket Error 10054 (Connection reset by peer)
the TRCCNN IBM server trace shows the ACK for the RST on the server.
Wireshark shows that Client is requesting a Retransmission .
However we have multiple clients that are experiencing this and it just started out of the blue about a month ago. I think the problem might be application related but i'm in the dark on how to troubleshoot something like that.
It looks like you're losing TCP packets on your network. Packet loss indicates duff network hardware, drivers, switches, cables, NICs etc. Connect the client to the server direct through a new switch or CAT 5 cable - can you replicate the problem?
ASKER
Well i suppose we could ;however, this is at a remote location and it would be costly to drive out there. I have captured and analyzed wireshark captures from the same side of the network as the server and they seem normal and no one on that side appears to be disconnecting. All the clients that are disconnecting are on the remote side of the VPN.
The captures on the ASA show no dropped packets so I might have too easily dismissed the ASA 5505s . What I discovered today was some ISAKMP keepalives that had been tampered with (Probably because of the VPN going up and coming down all the time) I disabled the keep alives in that tunnel-group and it's only been 2 hours but no one disconnected today.
I'll post back tomorrow.
I can not recreate the problem for sure, Client Access gives the Disconnect screen for several reasons and not knowing the exact reason (aside from Socket Error 10054) makes it very challenging. I did go there and replace the entire Layer 1. Tried switching out the switches ( Layer 2 ) and the same thing happened. Even threw in a Layer 3 device closest to the clients to segment the network and explore that option.
The captures on the ASA show no dropped packets so I might have too easily dismissed the ASA 5505s . What I discovered today was some ISAKMP keepalives that had been tampered with (Probably because of the VPN going up and coming down all the time) I disabled the keep alives in that tunnel-group and it's only been 2 hours but no one disconnected today.
I'll post back tomorrow.
I can not recreate the problem for sure, Client Access gives the Disconnect screen for several reasons and not knowing the exact reason (aside from Socket Error 10054) makes it very challenging. I did go there and replace the entire Layer 1. Tried switching out the switches ( Layer 2 ) and the same thing happened. Even threw in a Layer 3 device closest to the clients to segment the network and explore that option.
ASKER
Well so far no one has disconnected today at all.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ah .perhaps I should have done a little more explaining . Thank u blue for all the help. However it seems now that when they connect to a public ip address that is 1to1 natted to the server ip. They get disconnected .however the vpn sessions do not. This is opposite of what was happening before.
ASKER
Never mind about the disconnects to the public IP not through the VPN that was a couple of configuration errors. They weren't really getting disconnected, they were never connecting.
all is well after the editing of the ISAKMP keepalives in the tunnel-group .
all is well after the editing of the ISAKMP keepalives in the tunnel-group .
Wikid. Glad you got it sorted and sorry I couldn't be more helpful.
ASKER