Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Cannot Connect from Windows SAP GUI

I have installed 2004s test drive, but I am unable to connect from Windows. It just hangs with a message "waiting for response". However, using netstat, it appears that there is an established connection.

I have no firewall running, and I don't see any suspicious messages in /usr/sap/N4S/DVEBMGS01/work.

Can someone suggest what else to try? Thanks.

[code]

root@turf /usr/sap/N4S/DVEBMGS01/work $ netstat -plant | grep sap

tcp 0 0 0.0.0.0:3200 0.0.0.0:* LISTEN 3876/en.sapN4S_SCS0

tcp 0 0 0.0.0.0:3201 0.0.0.0:* LISTEN 3927/dw.sapN4S_DVEB

tcp 0 0 0.0.0.0:50113 0.0.0.0:* LISTEN 3899/sapstartsrv

tcp 0 0 0.0.0.0:8100 0.0.0.0:* LISTEN 3875/ms.sapN4S_SCS0

tcp 0 0 0.0.0.0:8101 0.0.0.0:* LISTEN 3926/ms.sapN4S_DVEB

tcp 0 0 0.0.0.0:3601 0.0.0.0:* LISTEN 3926/ms.sapN4S_DVEB

tcp 0 0 0.0.0.0:1401 0.0.0.0:* LISTEN 3928/co.sapN4S_DVEB

tcp 0 0 0.0.0.0:3900 0.0.0.0:* LISTEN 3875/ms.sapN4S_SCS0

tcp 0 0 0.0.0.0:3901 0.0.0.0:* LISTEN 3926/ms.sapN4S_DVEB

tcp 0 0 0.0.0.0:50013 0.0.0.0:* LISTEN 3861/sapstartsrv

tcp 0 0 192.168.1.201:3200 192.168.1.100:1450 ESTABLISHED 3876/en.sapN4S_SCS0

[/code]

Former Member
Former Member replied

Hello Jerry...

One comment here that might help you. If you look at the netstat output a little bit more carefully, you should see, that the instance listening on the systemnumber 00 (the port 3200) is not the N4S, but the SCS0 instance. The Netweaver 2004s instance is listening on system number 01, that is, port 3201, or if you want to use the message server, 3601.

Best regards,

Heikki Karhunen

PS. I got the same 'waiting for response' message when I initially tried to connect to the systemnumber 00, which we used to use as the default systemnumber for new installations.

0 View this answer in context
Not what you were looking for? View more on this topic or Ask a question