Solution : https://service.sap.com/sap/support/notes/26086 (SAP Service marketplace login required)
Summary :
TCP/IP connections in SAP environments may experience disruptions involving larger data packets due to mismatches in maximum transmission unit (MTU) sizes across different network segments. Symptoms manifest as "connection to partner broken" errors in SAPGUI and "Connection timed out" in R/3 systems. The issues arise when data packets exceed the MTU limit, necessitating fragmentation that may not be supported by all network components. Common in networks where FDDI and Ethernet coexist, troubleshooting with tools like 'niping' is recommended to identify and adjust MTU settings appropriately to stabilize connections.
Key words :
netstat -ithe normal ethernet packet size, /3-system additional key words mss, running tcp/ip connections break, applications send data-packets larger, reassemble fragmented tcp/ip packets, specific tcp/ip configruation, receiving larger data packets, tcp/ip-stack, normal mtu-size, defragment packets larger
Related Notes :
| 500235 | Network Diagnosis with NIPING |
| 413330 | Network timeouts |
| 155147 | WinNT: Connection reset by peer |
| 107407 | Win95: Connection Reset by Peer |
| 67098 | Connection termination for ISDN lines. |
| 21971 | Connection between SAP GUI and application server terminated |