July 29, 20232 yr Hi Alex I have just updated P3D to v5.4. at the same time I updated Little Navmap to latest version 2.8.12 from 2.8.10 (and of copurse Little Navconnect). Since then, I have not been able to run Little Navmap remotely due to the above problem. I have seen a post converning Defender and Protected Networks, but I have checked and this is not enabled on my PC's. Neither are any firewalls enabled. I rolled back to the older version, but I still see the problem. Other connections (ASPP3D) are working fine. Which server are we even talking about? I'm attaching a bit of the log file (after the rollback). I'm hoping you can shed some light on this... BRGDS Sven Sorensen, EKCH [2023-07-29 19:49:04.680 INFO ]: Little Navconnect [2023-07-29 19:49:04.680 INFO ]: Version 2.8.5 32-bit (revision 89bd0b0). [2023-07-29 19:49:04.681 INFO ]: Data Version 11. Reply Version 5. [2023-07-29 19:49:04.681 DEBUG]: bool atools::win::ActivationContext::loadLibrary(QString) "D:\\FS Addon\\Little Navmap\\Little Navconnect\\SimConnect.dll" [2023-07-29 19:49:04.708 DEBUG]: bool atools::fs::sc::SimConnectApi::bindFunctions(atools::win::ActivationContext&) [2023-07-29 19:49:04.708 DEBUG]: bool atools::fs::sc::SimConnectApi::bindFunctions(atools::win::ActivationContext&) done [2023-07-29 19:49:04.708 DEBUG]: atools::fs::sc::XpConnectHandler::XpConnectHandler() [2023-07-29 19:49:04.708 DEBUG]: FSX status true [2023-07-29 19:49:04.709 DEBUG]: atools::fs::sc::DataReaderThread::DataReaderThread(QObject*, bool) [2023-07-29 19:49:04.709 DEBUG]: void atools::fs::sc::DataReaderThread::setHandler(atools::fs::sc::ConnectHandler*) "SimConnect" [2023-07-29 19:49:04.709 DEBUG]: SimConnect available: false [2023-07-29 19:49:04.710 INFO ]: Connecting to FSX or Prepar3D using SimConnect. [2023-07-29 19:49:04.716 INFO ]: Starting server. This can take some time ... [2023-07-29 19:49:04.742 DEBUG]: Navserver starting [2023-07-29 19:49:04.742 DEBUG]: virtual void atools::fs::sc::DataReaderThread::run() update rate 500 [2023-07-29 19:49:04.756 DEBUG]: localHostName "SKSGAME5" localDomainName "" [2023-07-29 19:49:04.759 DEBUG]: Found IP "fe80::6828:5539:ad4f:9253%ethernet_32777" [2023-07-29 19:49:04.759 DEBUG]: Found valid IP "192.168.0.119" name "SKSGAME5" [2023-07-29 19:49:04.759 DEBUG]: Found IP "fe80::5c4d:19d9:2dc0:edc5%ethernet_32779" [2023-07-29 19:49:04.759 DEBUG]: Found valid IP "192.168.56.1" name "SKSGAME5" [2023-07-29 19:49:04.759 DEBUG]: Found IP "::1" [2023-07-29 19:49:04.759 DEBUG]: Found IP "127.0.0.1" [2023-07-29 19:49:04.759 DEBUG]: Found IP "fe80::9035:c514:410e:a4c3%ethernet_32774" [2023-07-29 19:49:04.760 DEBUG]: Found valid IP "172.20.80.1" name "SKSGAME5.mshome.net" [2023-07-29 19:49:04.760 DEBUG]: Server address IP QHostAddress("") [2023-07-29 19:49:04.763 CRIT ]: Unable to start the server: The address is protected. [2023-07-29 19:49:04.764 INFO ]: Server running. [2023-07-29 19:49:04.764 DEBUG]: MainWindow::mainWindowShown exit [2023-07-29 19:49:04.764 INFO ]: Not connected to the simulator. Waiting ...
July 29, 20232 yr Normally it should print "Server address IP QHostAddress("0.0.0.0")" in the log which means it listens on all available interfaces (like on Ethernet, WIFI, etc.). No idea why your host address is empty. Did you change the port number to a maybe too low value? Maybe a firewall is interfering? Alex Alex' Projects: Little Navmap
July 30, 20232 yr Author Hi Alex As always, a very quick answer! I did change the port number, but only when my problems began, and I changed it back when that didn't work. To tell you the thruth, I have absolutely no idea, what happened yesterday. On the 27th I did the mentioned update and my problems began. When I tried it on th 28th, it worked fine - but only once. Then the address was protected again and nothing worked. I tried all sorts of things, port change rollback to an earlier version of Little Navmap, but to no avail. Then I wrote to you... I came back today with the intention of getting to the bottom of this, but Lo! and Behold - everything is working again! And I haven't done anything today until that point. Now I have updated Little Navmap, and everything is still working fine. Im' confused, and hate when things like this happens. Fortunately it is rare... So let's close it for now, it must have been something in my setup, which is a bit special (Little Navmap running in a Hyper-V VM and accessed as a Remoteapp via RDP). If that doesn't mean anything to you, rest assured it usally works great! Thanks again, BRGDS Sven
July 30, 20232 yr 6 hours ago, svenks said: Now I have updated Little Navmap, and everything is still working fine. Glad it's working again but ... 6 hours ago, svenks said: Im' confused, and hate when things like this happens. ... so am I.🙂 No idea what can cause these hiccups. 6 hours ago, svenks said: If that doesn't mean anything to you, rest assured it usally works great! Sure it does. I have a whole zoo of VMs with all kind of OS for testing on my Linux box.🙂 Alex Alex' Projects: Little Navmap
Archived
This topic is now archived and is closed to further replies.