In recent days I faced this issue for one location users, we know that when users from one location are unable to access SAP and soon they login they are getting the this error and terminating the session.

When network team checked the network connection, they found every thing fine except SAP. Finally after two days struggle, after replacing the network card IP , it started working fine. The root cause is yet to know.

But, since network team does basic checks from their side and SAP Basis team check from their end and found all fine, so where is the issue. To find that network team should have some idea how SAP  works and how to find what went wrong.

SAP GUI communicate with TCP/IP protocol, where as the ping command uses the ICMP protocol. So ping command / tracert results can confirm the issues if there is no connectivity between client and SAP application. Where as NIPING to be used to test the connectivity and its consistency between SAP client ( GUI ) and Server. Please go through the below Url for additional details

https://wiki.scn.sap.com/wiki/display/SI/FAQ+Network+Interface

NIPING will work based on client server communication, so you have to start NIPING on Server side ( From exe folder ) and then start niping on client machine where SAP exe files are available  ( Ex:   C:\Program Files\SAP\FrontEnd\SAPgui  – you can find Niping in this location )).

If you are ending with an error while testing with 500 bytes samples , ask your network team to trouble shoot the network . In my case after changing the router IP configuration all went fine.

All the best ………….. Keep watching my Blog