ADS unable to connect Win10 after 1803 update

[Former Member]

I am also unable to connect to the server on Win 10 machines after updating to 1803 Error 7077 from applications, 6420 from the Architect. Using Adv 12 32bit. Win 7 machines are okay. I have tried most of what I can find from Google. Any ideas please?

[michael_loop]

Hello Charles,

Thank you for your question. In order to keep this discussion focused on the original question, please create a new question thread. (Go to Actions > Create new question) This will increase the chances that more members see your question.

Please also do not cross-post questions in multiple threads or primary tags.

Regards,

Mike Loop - SAP Product Support

[michael_loop]

Make sure that Windows Firewall or other security tools are not blocking extended-sys.mcast.net:2989 on UDP. Advantage uses this address and port when trying to discover servers. It does not attempt to access SAP or any address outside of the local subnet.

Port 138 is also used for discovery. This is the same port as "Network Discovery" or "File and Printer Sharing". Neither of these are enabled by default in Windows. Enabling one of these services may be easier than configuring the firewall.

I believe that only one of the above ports needs to be open for discovery, but if opening one does not work, try the other, or both. We don't know yet what Windows has changed.

Specifying the server name and port in the connection string or ADS.INI should bypass discovery.

Regards,

Mike Loop
Senior Product Support Engineer
SAP Product Support

[a555bacon]

Try opening port 2989 for UDP both inbound and outbound on the server.

[Former Member]

Thanks to the above details, I was able to solve the problem at one of our customers whose Win 10 machine had just upgraded to 1803. (Simply setting the "6262" parameter in the connection string was all I needed to do).

This morning, at another customer, the same problem arose - 6420 error - Aha thought I - this should be simple - simply put the "6262" in the connection string.

Yes, the 6420 error is gone but now I get a 6097 error - I have put the IP address and port in the ADS.INI file, have opened port 6262 for UDP and TCP (in and out) on the Win 10 machine, have checked that Network Discovery is allowed through the firewall but still no joy.

I am out of ideas to try - anyone have any suggestions what to look for. (All the other machines, running Win7 are all working OK)

Thanks

[former_member584270]

Heads up on our experience here.

Server: Windows 10 (recently updated to 1803)

Client: Windows 7

Client was not working no matter what we tried (and we tried everything related to 1803 and networking issues).

Solution was to add the port(6262) to the connection string on the client.

Why would that have fixed it do you think?

[michael_loop]

Many firewalls and routers will not allow multicasts to pass, which is what discovery uses. It appears that Microsoft has, intentionally or otherwise, introduced a new layer that intercepts multicasts but allows direct connections through. When you specify the port in your string, you bypass the multicast.

If your connection is over TCP/IP, that could also be part of the puzzle. Multicast always uses UDP, which could be blocked, whereas TCP/IP may be open.

Mike Loop - SAP Product Support

[former_member604454]

My dev computer ran this update over the weekend. I'm now getting a 6420 from the ODBC driver accessing ADS locally. Any updates on how to most easily and securely fix this?

Edit: False Alarm. Another reboot put this back to normal.

[Former Member]

After extensive testing, and sharing observations with Michael ( thanks so much ), I have found that the key is to bypass discovery. My suggestion:

1). Set the server to a STATIC IP

2). Create a simple ADS.ini file on each workstation with the following:

[SERVERNAME]

LAN_IP=192.168.1.xxx. ( xxx would be the assigned IP )

LAN_PORT=6262

[SETTINGS]

ADS_SERVER_TYPE=2

3). Go to Advanced Network Settings and be sure Password Protection is OFF and File and Printer Sharing is ON

4). Make sure your firewall has Rules to permit UDP ports 6262 for both inbound and outbound

The 1803 installer may leave some settings in place, and it may not, during the update process. Primarily, when it disabled Homegroup, it reverted ALL settings for discovery to the original values, and crippling some Services.

[Former Member]

I tried all of the suggestions but discovery simply is being blocked.

Adding the ADS.ini file with the IP port specified does work, but not all systems have a STATIC IP ... so that is a more time consuming solution.

The extended-sys port is not shown on the Firewall settings so perhaps it is being blocked. The firewall is set to block anything not specifically exempted.

[michael_loop]

In answer to your earlier question, I am able to reproduce the problem, once I got the test machine set up.

I had read online that enabling SMB1 resolved some networking problems introduced by Windows 1803. I have not pursued this yet. SMB1 contains the vulnerabilities that enabled the Wannacry and Petya exploits. SMB2 was disabled because of similar vulnerabilities, so re-enable it with caution.

I found that I could connect if port 6262 (or other ADS port) is opened in the firewall and I specified the port in the connection string. I could discover the server if I enabled ports 2989 and 138. I am not sure yet whether both are required.

Something else is going on, though, because if I disabled the new rules after having made a successful connection, I was still able to discover and connect. I think specific allowed connections are being cached.

For some reason I also needed to use a server-side alias because my client was not able to retrieve information about network shares. I'm not sure this is related.

We are still testing. Once we find the minimum number of configuration changes required, I will publish a Knowledge Base Article.

Mike Loop - SAP Product Support

[former_member604454]

Where do Knowledge Base Articles get posted these days? (I really miss the old site.)

[michael_loop]

https://launchpad.support.sap.com/. There is a search field at the top of the page, make sure "Knowledge Base" is selected.

Mike Loop - SAP Product Support

[Former Member]

I have got it working by changing the connection string to \\servername:6262\ It had been a mapped drive.

I have tried that before without success.

I also found on the local machine Control Panel\Programs\Turn Windows Features on\ that 'SMB Direct' was unticked on on the updated machine and ticked on a not updated machine.

I ticked it and the connection worked and it continues to work with it unticked.

Another machine updates tonight so hoping for the best.

Thanks for your help.

Peter

[former_member541656]

> Enabling SMB2 on the server seems to solve the problem

It doesn't here (SMB2 was already enabled).

[former_member1017453]

Enabling SMB2 on the server seems to solve the problem

[Former Member]

Thank you. I have tried unblocking and creating the ads.ini but without success.

Are you able to replicate the problem or is it just me?

Regards

Peter