Skip to Content
avatar image
Former Member

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]

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • Best Answer
    avatar image
    Former Member
    Feb 20, 2007 at 02:59 PM

    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.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Feb 20, 2007 at 01:23 PM

    Dear Jerry,

    the "waiting for response" popup with an already half way passed progress bar indicates that the message server was reached. This is good, the GUI reached the server 😊

    After starting the N4S system it may take up to several minutes until something happens. How long did you wait? If after 15 minutes nothing happens, there might be a problem, but until then it may just be the slow machine.

    Best Regards,

    Hannes Kuehnemund

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    May 14, 2007 at 10:30 AM

    Well i m also getting the same problem when i try to connect from windows gui its hang on "waiting for response".Even i try from linux platin gui to log in SAP it again stop on "connecting" . i changed it to ms port 3601 but still nopthing is coming.

    Guys please help me if any body solve this problem plz let me know

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jun 05, 2007 at 03:46 PM

    When I see the netstat output the only things I have note is that the system don't have its ip address.Probably you don't have set up correctly the ip addres of the N4S : try to simply associate the ip of your machine with the name of the N4S systems in /etc/hosts.

    Add comment
    10|10000 characters needed characters exceeded