WSAEWOULDBLOCK - SAPGUI client issue

[dude95]

I have the following setup:

Windows Server 2012 - SAP Solution Manager 7.2 - SAPLogon 7.4 - Can logon from the server

Windows 10 - SAPLogon 7.5 - Same network - Can logon

Windows 7 - SAPLogon 7.4 - Same network - Can logon

Windows 10 - SAPLogon 7.5 - Same network - Can't logon with WSAEWOULDBLOCK error . Can ping both the IP and hostname of the SAP server. I opened up outbound ports 32,33,36,80 before totally shutting off the firewall of the client. I shut off the firewall of the server before realizing that the other computers worked. I'm not a network guy - but it's obviously something on my one laptop. It's a fairly new laptop that had McAfee on it, but is now disabled. Windows defender is the only security on it now. Again - this laptop is on the same network and I can ping both the IP and the hostname of the SAP solution. It has the exact installation of SAP GUI 7.5 as the other Windows 10 computer that I am able to login with.

Anyone have any thoughts for someone who really doesn't know much about networks?

[jude_bradley]

Can you please provide a screenshot of the the issue.

[dude95]

untitled.png

[TammyPowlas]

Hi Tim - I searched and I recommend taking a look at this SAP Note: https://launchpad.support.sap.com/#/notes/0002499735 - good luck

[dude95]

I did see this note - but I'm not sure how this helps (although it's 100% specific to my issue). When I execute niping - I get the error: "partner '208.xx.xxx.xx:3298' not resolved". I get that error when I niping the IP address or the hostname. Interesting that it resolves the hostname to the IP address.

Also interesting that the hostname resolves to a different IP when executing from a working client computer, but still gets an issue. It resolves to the server IP - 'partner '10.xx.xxx.xx:3298' not resolved"

Firewall is still off on the client, so I shouldn't have to open up any ports(like 3298)????