on 08-28-2015 2:49 AM
This usually means port 3200 from the /../..etc/services is not connecting to your backend. Can you telnet from the PC with the issue via port 3200 to the backend IP address? If not, verify your PC's firewall isn't active and if you are in a domain with a firewall then that port will need to be authorized.
I am surprised ping worked? That was typically used in Denial of Service Attack's in the late 1990's. Most Network Security Admins will lock that down.
Other suggestion is to move on to SAP GUI 7.40 Patch 4 Hotfix 1.
Cheers,
Dan Mead
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
I use telnet to test with the port 3300 which the system admin gave me and it indicated the port is ok.
And the firewall is not active.
I noticed that in the services file there are settings like this, "sapdp00 3200/tcp" "sapgw00 3300/tcp", is there anything wrong with the setting?
thanks,
Shuang
Hi Shuang,
You are getting into the role of what's called a BASIS Administrator when asking about Instance Number's. Depending on your landscape each instance will be assigned a two digit number. You can access this information through your SAP GUI 7.xx console. The Dialog Ports, sapdp##, will always begin with 32 and end with the Instance Number. Your Gateway ports begin with 33 and Message Server ports start with 33.
Depending on your backend version, either NW730 or higher, your service file may need sapdp##, sapgw##, or sapms_SID in order for the SAP GUI client to connect.
Cheers,
Dan Mead
Hi SS,
I saw you posting on using SAPGUI + IP = Instance number. What exactly is sapgui.exe doing and what is the expected result supposed to be out of curiosity. Somehow I think this needs to use a valid port. But, if I use 3200 I can see it generates an error "Cannot split connection string". I usually only allow ports I have set up in ICM. I tried the telnet command leveraging the sapdp00 port 3200. In my situation the Instance Number is different and as I expected my network firewall isn't allowing it.
Cheers,
Dan Mead
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.