FiveTech Software tech support forums

This is NOT a FWH issue, but perhaps others have experienced the same problem.

When my computers, networked with the Advantage Database Server, and all running Windows 10, were upgraded with he April 2018 release from Microsoft, suddenly connections to the Advantage Database Server were lost.

I realize Microsoft made changes to the networking, including dropping Homegroup ( which was not being used anyway ) and apparently it reset networking settings to default. I've observed that using File Explorer, you can no longer see available Network computers although you can map to them.

My main problem is that now I find my program can no longer connect to Advantage Remote. First I found that the firewall had removed the port necessary on the server ( 6262 ) but I reinstalled those openings. Still is doesn't work.

I ask here simply because perhaps some others have also experienced this ( I know a lot of people use ADS ). Sadly, it's specific to this Win 10 upgrade and I have been unable to find any documentation so far.

Any observations would be appreciated.

Tim

I backed up all my files and did a fresh install of Spring Creator 64 bit 10 pro on my production laptop and after the install I could NOT connect to any computers in my workgroup via a unc, nor see them in my workgroup network folder .... I was really upset\disappointed and thought it was a fluke ..

I went back and re-installed the Fall Creator on my laptop and verified my workgroup share(s) to other computer were working and then took my Spring Creator install stick and did an 'in place' Spring upgrade ... that fixed my \\share unc problem .. I can now see all my workgroup computers ...

I saw nothing on the internet about losing workgroup shares on a fresh install ... I had a walk in customer come into the store that manages several Restaurants and he was complaining about the same thing ... his POS database would not connect to his clients .. amazingly enough ... if I opened a folder ( while he was remoted into his restaurants network) .. I manually typed in the \\ unc path in lower case to one of his client machines and it worked, even though none of his workgroup workstations were in the network connection folder ...

This problem only seems to be common to Win 10 Pro and not Home premium .. fresh installs of Spring Creator 64 bit Home premium seems to see all the workgroup computers and you can easily connect to any other machine with a \\unc.

Rick Lipkin

ps ... I think I tried this fix and it did not work ...
https://www.ghacks.net/2018/04/17/fix-p ... 3-upgrade/

Thanks for sharing. If I have to do a full reinstall of the update on every client's computer, that simply is not going to work out.

I have tried to get support from ADS but their forum has gone missing and so has support, though they still charge for the product. I emailed my contact but she is not responding. I'm sure I will get a bill soon, but aside from that ... this is crazy.

I tried the link and nothing. My machines are running Windows 10 pro. I have a feeling I may need to revert them back to 1709 but that is a major pain.

So if anyone has other observations or Ideas, they would be appreciated.

Hello Tim,
we had similar Problems with RDP Connections.

https://blogs.technet.microsoft.com/yon ... mediation/

Best regards,
Otto

Microsoft took the liberty of making significant changes in networking with Win 10 Pro, and shutting off a number of necessary services. Here is an article on what needs to be reset:
https://answers.microsoft.com/en-us/win ... 6264691930

Even with this occurring, ADS is NOT working with Win 10 1803. I first rolled back the server to 1709. That did not help. I am now reverting a workstation to 1709.

ADS Remote will work on the computer where it is installed, but not across the network. I have reached out to my contact at ADS ( SAP ) but have had absolutely no response. If anyone else has any better luck, please let me know.

Tim

Tim

If you re-install the Fall creator W10 pro ( and get everything working again ) .. eventually each of those clients will be updated whether you like it or not. This is a Microsoft problem they need to fix quickly ..

On my ( working 1803 ) laptop, As far as the services mentioned ... they were set to manual and the SMB was checked on



Rick Lipkin

Here is what I have found so far:

Microsoft turned off all services that relate to "discovery" on computers. One has to go in to services, and set the following to Automatic, and turn them on:
Function Discovery Services ( both services )
SSDP Discovery
UPnP Device Host

In addition, ADS uses ports to discover their server. These may also have been blocked by the firewall:
extended-sys.mcast.net:2989
port 138

ADS is apparently still trying to figure out what else may have been altered.

In some cases, using an ADS.INI file will work. YOU MUST SPECIFY THE IP ADDRESS HOWEVER.

To add to this, the connections are not stable. In other words, once the connection is made, it may continue to work, or not ....

Of course rolling back to Win 10: 1709 is the "fail safe" solution.

As mentioned previously, Windows 10 : 1803 April ( May ) 2018 release, removed the homegrown capabilities and reverted all sharing services to OFF. In any case, after doing this update it is likely you will need to go back into Network settings and turn on these features, and go into Services to reset essential services to Automatic and turn them on.

IF you have paths properly set when the upgrade occurs, direct connections ( ie. using Peer To Peer ) may work, but then again, they may not. Apparently some connection data was stored internally, and in some update cases it remains, and in others it does not. In addition, when you do establish a connection to your databases, it may retain the path and work for awhile, then stop working. All of this has been verified.

ADS has some specific issues. Most people set it up on computers with dynamic IP assignments, so it must search for the server. Ports 6262, 2989, and 138 might all be blocked by the firewall, but all must be open. Even then, it might not communicate. I have tested this extensively on 4 different computers networked and the behavior is not stable.

The only RELIABLE way to get the ADS server back online with your workstations is to create an ADS.ini file. The docs explain this. Your server needs to have a STATIC IP, and it must be specified in the .ini file. With this in place, the ADS connection will operate correctly. There are reports that once the connection is established, the .ini file could be removed and the connection still works. I can verify this, but it doesn't continue forever. On a future boot up, it might be lost again.

The people at SAP are working on this to find a way to assure network discovery can be on and reliable. Microsoft is totally silent on the subject even though it is their changes that created the whole problem. I am working with an individual at SAP and sharing our testing findings. If I get more definitive info, I will share it here.

Hi Tim

From here , fonud solution , ( deactivate SMB1 and activate SMB2 or higher )
https://blog.mertech.com/windows-10-ver ... plications

So, SMB2 is not present on all Win 10 computers, and SMB1 is off. Note, the problem stated here says it may be related to Windows Defender ...

I've spent a lot of time with ADS ( SAP ) testing various options here. Ultimately we will come up with some definitive answers, but for now, the one solution that works immediately is to not depend on discovery, and to use the ads.ini file.

Otto wrote:Hello Tim,
we had similar Problems with RDP Connections.

https://blogs.technet.microsoft.com/yon ... mediation/

Best regards,
Otto

Hi Otto,

I have found a solution like that.

The problem with that is it makes your computer vulnerable to some very strong viruses, and that is why it was disabled. VULNERABLE means you accept the risk of being hacked or penetrated by serious malware.

In an earlier post I specified 4 services that can be set to Automatic and turned on. These should then allow Remote Desktop to work, but be sure to used Fixed Local IPs and specify those when setting up the connection. I have absolutely no problem with Remote Desktop doing this.

This can be solved in this way

Cmd.exe /c netsh advfirewall firewall add rule name=AdsAllowPort protocol=TCP action=allow dir=OUT localport=6262

It is actually not appearing to be a firewall issue. I have been working directly with ADS on this, and it appears it may be related to security changes in Windows Defender. The firewall port rules are in place and that does not resolve the problem. Apparently those using AVG find it still works ( with Defender off ) but that is not the best long term solution. The ADS.ini file resolves the problem immediately because network discovery is not needed.

To access the network I had to change all the system access commands like this:

\\SERVER:6262\UNC_SHARED\Directory\mydictionary.add

Ads,Ini