Dean B

Pete, Will you be releasing an updated FSUIPC shortly? Right now the installer gives us - INSTALLATION FOR Prepar3D: AppPath="D:\Prepar3D\" Checking version of Prepar3D.EXE: ... Version 1.2.3253.0 (Need at least 1.0.677.0) !! WARNING !! This version of ESP is later than any known by this FSUIPC4. There may be problems. Please check for a later version of FSUIPC4! -Dean

Actually I found an option in the Routers config, to assign an ip to one machine, so i've done it that way. Thanks. --Dean

Yes I am with Virgin, but I still don't understand why it should now find that ip when I've always used the ServerName= FS-Rig option which has worked fine for years. My machines are given their own internal ip addresses assigned by DHCP from the D-LINK DIR-655 Router. IP's 192.168.0.2 up to 0.255. So I can give each machine its own one of these ip's and it will remain fixed? I didn't think that was possible. --Dean

Pete, In reply to your email - =================================================================== Hi Dean, >> What I've also noticed is that when the main FSX window opens, in windowed mode, the title bar only displays 'MS FSX'. It's only after a few seconds that it displays 'MS FSX with wideserver:waiting for clients'. Maybe it's been that way since a previous FSUIPC upgrade. I only noticed since i switched to window mode when setting up Edzok cameras. << No, it has ALWAYS waited until FS is fully ready to fly before enabling. It always delayed a few seconds to let things settle. This is as it has been for 12 years. 151 Trying TCP/IP host "Fs-Rig" port 8002 ... 151Okay, IP Address = 81.200.64.50 Is that REALLY the IP address of your "Fs-Rig"? Usually they are 192.168.xxx.yyy. That looks more like an Internet or Router external IP address. Have you explicitly given Wideclient that IPaddress, or it that what it gets automaticaly? If so, you have a router problem. Try giving the IP address explicitly. ================================================================= The FS-Rigs IP addy is currently 192.168.0.195. If I explicitly state this then connecting is not an issue. If I state 'FS-Rig' as I always have done, I get that error. No idea where that IP is being called from as my IP address right now begins 86.25.**.** It means I now have to check the IP everytime I start the FS-Rig as the network gets shut down every night and three, sometimes four machines aren't always started in the same order. Whatever has changed on the client or the server, is fairly recent. Maybe a new piece of software or an update. --Dean