Posted here as this covers different networking systems.For well over a year, I have been running FS9 and FSX {on 2 separate partitions} networked to a second computer via an ethernet connection as an FS Support system with Wide FS to run programmes such as Squawkbox, FlightSim Commander etc etc. During the last month I flew FS9 exclusively but today tried FSX. It ran correctly except that Wide FS would not connect. Fsx showed Wide Server waiting for clients AND wide Client waiting for a connection. A copy of the wide client log is as follows:Date (dmy): 13/01/11, Time 17:40:06.640: Client name is JER 94 Attempting to connect now 110 Trying TCP/IP host "JER1" port 8002 ... 110 ... Okay, IP Address = 169.254.208.49 21172 Error on client pre-Connection Select() [Error=10060] Connection timed out 21172 Ready to try connection againRepeated until I close dowmSo far I have checked the installation on both computers against the Wide FS manual, ensured all firewalls etc are turned off, reinstalled my windows network, and checked that all necessary files are shared and can be seen and opened in Network Places.All to no avail. But Wide FS/FS9 still works perfectly. On the other hand, I have also lost the FSX Simconnect connection between the two computers!either Wide FS or SimConnect So it seems to be something blocking the client computer seeing FSX - with either Wide FS or SimConnect - but nothing else!Not sure where to look next so v grateful for any suggestionsJohn R

Posted here as this covers different networking systems.For well over a year, I have been running FS9 and FSX {on 2 separate partitions} networked to a second computer via an ethernet connection as an FS Support system with Wide FS to run programmes such as Squawkbox, FlightSim Commander etc etc. During the last month I flew FS9 exclusively but today tried FSX. It ran correctly except that Wide FS would not connect. Fsx showed Wide Server waiting for clients AND wide Client waiting for a connection. A copy of the wide client log is as follows:Date (dmy): 13/01/11, Time 17:40:06.640: Client name is JER 94 Attempting to connect now 110 Trying TCP/IP host "JER1" port 8002 ... 110 ... Okay, IP Address = 169.254.208.49 21172 Error on client pre-Connection Select() [Error=10060] Connection timed out 21172 Ready to try connection againRepeated until I close dowmSo far I have checked the installation on both computers against the Wide FS manual, ensured all firewalls etc are turned off, reinstalled my windows network, and checked that all necessary files are shared and can be seen and opened in Network Places.All to no avail. But Wide FS/FS9 still works perfectly. On the other hand, I have also lost the FSX Simconnect connection between the two computers!either Wide FS or SimConnect So it seems to be something blocking the client computer seeing FSX - with either Wide FS or SimConnect - but nothing else!Not sure where to look next so v grateful for any suggestionsJohn R

Go here John http://forum.simflight.com/forum/30-fsuipc-support-pete-dowson-modules/

Thanks.I posted here first as this is not just a FSUIPC problem. However, I'll post over on SimFlight in case Pete D can think of anything.John R

I have had the same thing happen in the past and each occurrence was due to my server or client being assigned a different IP address than is in the FSUIPC init. or simConnect.xml file . I apologize is this is obvious, but verifity each computers current IP and make sure the server and client IP's are correct in the various init and xml files. I hope that helps.Bob.. :)

Bob, Many thanks. Checked my Port and IP settings v carefully - no change. Re-installed both Wide FS and SDK/Simconnect - again no change. So looked at the last few weeks - I un-installed an ACARS programme I had tried. I then un-installed MSE from both systems (which I had swopped for AVG Free as the latter seemed to be growing with every update) - no change. I then re-installed MSE to search on line for solutions but carefully made sure that both firewalls were off. The first option I tried after this - "voila" Wide FS connected immediately and after a couple of tweaks simconnect was also back on line. In the end, I suspect that somehow a firewall had been active on one of the systems - although I don't understand why it only affected FSX and not FS9?An interesting 24 hours but we got there.RegardsJohn R