April 12, 20215 yr I have a new PC with Windows 10 Pro. When I start little nav connect I get the following error message: Server cannot be started: The address is protected. Despite several attempts to restart little navconnet, the error remains. But sometimes it happens when the computer is restarted that the little Navconnect can be started without errors. Does anyone have any idea where to look here?i start lillte Navconnect i becam . Sorry for my bad english, this is a translation about babelfish.
April 12, 20215 yr 25 minutes ago, Dete said: Server cannot be started: The address is protected. There can be many reasons of that problem - firewall settings, system operating settings, local group policies, domain policies - as it's Pro version and policies can be inherited from domain server. But IMHO the most probable if fact that other Windows process takes exactly the same TCP port that is used by LittleNavConnect and that's why it can't be assigned to LNC. It's only my guessing, the exactly reason have to be investigated step by step to eliminate this problem. Regards, Piotr Never give up ... - here are details of the whip-round: https://zrzutka.pl/en/pewr2d -> to help my younger son fights against Acute Lymphoblastic Leukemia (blood cancer).
April 12, 20215 yr I had a report of the same problem by a user per email. Sadly, I did not get any feedback if my proposal worked. 😞 Did you enable/install Windows Defender Network protection? https://docs.microsoft.com/en-us/microsoft-365/security/defender-endpoint/network-protection?view=o365-worldwide This seems to be a Windows peculiarity. Alex Alex' Projects: Little Navmap
April 23, 20215 yr Author The problem seems to have been with the UEFI bios. Since the computer was bought new, it was taken for repair because of further problems. Now, after the BIOS update, little NAVConnect starts without any problems. Detlef
Archived
This topic is now archived and is closed to further replies.