simbro

Hi Urs, Thanks for the suggestion but I have in fact managed to trace the problem to a firewall setting on the DisplayUnit machine. Due to the LAN connection being on a different subnet I had to set different authentication rules and had forgotten to do so on this machine. Problem is solved and I'm happily using EFB via the LAN connection! Regards Simon

After many years of problem-free usage I have now changed my network configuration and am having problems connecting the DisplayUnit to the DataProvider over the network as I would like to have it. Both machines (DataProvider & DisplayUnit) have TWO network cards - 1xLAN & 1xWiFi - and the DisplayUnit->DataProvider connection is confusing me! DataProvider machine IPs: LAN=192.168.1.220, WiFi=10.0.0.145 DisplayUnit machine IPs: LAN=192.168.1.245, WiFi=10.0.0.160 The DataProvider starts up and displays 'This computer name is FS-TOWER, IP-address is: 192.168.1.220' followed by 'TcpConnector started' then 'Provider is ready and running'... When I enter either 'FS-TOWER' or '192.168.1.220' into the DisplayUnit no connection takes place! However, if I enter '10.0.0.145' as parameter the connection succeeds and the DataProvider displays 'New connection from 10.0.0.160 accepted.' I would like to make the connection via LAN rather than WiFi - as suggested by the DataProvider message... but despite the DataProvider saying that it is 'ready' on the LAN network it will only accept the DisplayUnit on the WiFi network! I have other software communicating between these two machines without problems on both the LAN and WiFi networks. Anybody got any clues as to what I'm doing wrong or missing in the network setup? Kind regards Simon

Something else I've just noticed: At the bottom of the DisplayUnit there is a statusbar which displays a green light & 'loading...' during the initialisation phase. On my remote client this line then changes to 'Connected to DataProvider' and all is well... However, on my local client there flashes up a yellow light and something to do with 'Socket Error beim Versuch.....' which is almost immediately replaced with a yellow light & 'Disconnected from DataProvider'. Unfortunately, I don't have time to read the whole message before it disappears! Is the output to this statusbar logged somewhere? Maybe there is a further hint as to what is going on here... Kind regards Simon

Hi Urs I don't think this will be the case as I have been running my Class A network for at least 8 years now connecting machines with all sorts of different OS's ranging from XP to Linux via Win7, Server2003/8 & MacOS... (at the last count I had 15 machines connected) Never been a problem sofar and I don't fancy reconfiguring my DHCP server to a Class C network considering that I also have a pool of fixed IPs that I would have to change as well! Also, the local DisplayUnit is using a local internal IP (127.0.0.1) to communicate with the DataProvider so I don't think the network class comes into play in this situation. I suspect that the Apple drivers inside the BootCamp installation might have something to do with it because I previously had FSX & EFB on a 'non-Mac' machine in Win7-Home (Class-A network!) and didn't have any problems with the local DisplayUnit. Anyway, not to worry! I'm quite happy at the moment seeing that I can use the remote DisplayUnit for the time being. As I mentioned previously, I'm getting some new hardware soon (both Mac & 'non-Mac') and will try various combinations of FSX/EFB on it to see what I can come up with. I'll keep you posted on any discoveries I might make.. ie. 'don't install EFB on a BootCamp partition' (or whatever!) BTW, just out of curiosity, is there a maximum number of remote DisplayUnits that one DataProvider can handle? I've got a small Citrix Terminalserver here and was thinking of trying to run a number of DisplayUnits on it just for fun... Kind regards Simon

Hi Urs sorry for the delay in getting back to you - I was away for the weekend. I've attached the complete error message that appears - (the contents of the scrollable message box in the .NET error window) I've also tried 'repairing' the .NET v4.51 installation via the 'Systemsteuerung/Programme' but after rebooting I still get the same error. FYI, in case it might be relevant, I'm running Win7 Home-Premium with SP1 via BootCamp... (ie. on iMac hardware!) Sofar I have never had any problems with this setup so I personally don't think it's of any relevance. I'm in no great hurry to have this problem sorted seeing that I can run the Displayclient without any problems from a remote machine for the moment. However, I'm going to be doing a complete new installation on some new Mac-hardware (via BootCamp) when it arrives and I would like to have the possibilty of running the DisplayClient on it at that point. I'm still using the Demo-License for the time being (expires 28.02) and hope to have the new setup installed by then at which time I will be using my 'proper' license again. Thanks for your support and a marvellous piece of software engineering! Kind regards Simon DisplayClient_ErrorMsg.txt

Further investigation found the cause of the problem - at least in my case! On the menu there is a button labelled 'TRFC' which needs to be enabled to show the ai traffic.... Pressing the button did just that!! Regards Simon

This would interest me also... Having seen this thread I checked my setup (remote) and also see no AI traffic. The monitor is showing traffic but it doesn't appear on the any maps. regards Simon

After many years of problem free usage of EFB I have just installed v1.5 on a new computer (Win7) and am having a strange problem: The Dataprovider and Client appear to have installed correctly (no error messages) and I can run the Dataprovider without any problems. However, when I start the DisplayClient I get an error immediately after it connects to the DataProvider - and then disconnects again! The error message: Aivla_EFB-DataProvider-Msg.JPG[/attachment] The strange thing is that I installed the EFB DisplayClient on a separate (remote) Notebook and it works perfectly! I'm only having a problem with the 'local' copy of the DisplayClient... I've de- & reinstalled everything on the server machine (EFB, .NET, etc...) but the problem remains the same. (Remote=no problem, Local=no go) The logfiles for both Dataprovider and DisplayClient are attached just in case they might be of use. Help would be appreciated as I'm starting to miss EFB... Regards Simon DataProvider_log.txt DisplayUnit_log.txt