on 12-20-2007 5:49 PM
Hi all
I am getting the following error while loggin on to SAP remote server -
Partner not reached
WSAEWOULDBLOCK: Resource temporarily unavailable
What could be the reason for the same? I have disabled the windows firewall. Furthur, I am unable to ping the application server.
I am a non-technical person, so what can I do to connect to the application server?
Thxs in advance
Hrishi
Hrishi,
I am at a client site and had similar issue
- when I hookup my laptop, I could connect to the SAP systems, ping servers.
- when I connect through client VPN, I could ping the servers but can not connect to the SAP systems or ssh to the servers
After lot of troubleshooting, the issue was with VPN profile. Once it was changed my issue got resolved. So I would definetely take a close look at your profile.
thanks
BMG
Edited by: Murali Godavari on Feb 6, 2008 4:27 PM
p.s: I was getting the same error message
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Different cause, similar issue:
On LAN (wired), and can connect to network drives, other apps, exchange(outlook) and SAPGUI to R/3 or BW.
When I dial up to ISP w/o disconnecting LAN, I can connect to network drives, other apps, exchange, but not SAP. Gives error:
connection to host 138......, sapdp01 timed out.
Component: Network interface
..
Method: NiPConnect
Return Code: -12.
Since internet impossible here, I have to dial-up often, but can't afford to drop SAP connection via LAN.
BTW, SAP connects fine through vpn over internet from same laptop.
I'm receiving the same error on clean installation I just did. Everything is up and running but I can't connect with my SAPgui. Any help would be appreciated. Thanks.
Michael
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Typically, if you can't ping the server, then it is a networking issue, or a VPN concentrator (server) configuration setting.
Many VPN servers are set to disallow pings to internal connections (reduces the chances of a denial of service attack from an outside computer).
VPN connections are also pretty notorious for not working correctly with DNS. If you are trying to connect via a name, change it to the IP address and try it again.
Hope it helps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.