Hi,lately I bought widefs so that I can run rc on a second pc. I think i followed the instructions to the letter but somehting is not right because when I run radar contact on my second machine I get this error:"Maybe running on wideclient, but fs not running on server, or wrong FSUIPC".Any help appreciated,Vic Nucera

Vic,I run RC4 on a second PC but I'm not at home at the moment so all this is from memory.Firstly, does WideClient say "Connected" in the title bar on your Client PC? If it doesn't then it's not 'speaking' to FS on the server PC.You do have FS running on the server PC don't you? Sorry to ask silly questions. That means at an airport and not just the Select a Flight menu visible. :( Finally, please advise which version of FSUIPC you're running. 'The latest' is not an acceptable reponse. :(

>Firstly, does WideClient say "Connected" in the title bar on your Client PC? If it doesn't then it's not 'speaking' to FS on the server PC.Nope it says waiting for a connection.>You do have FS running on the server PC don't you? Sorry to ask silly questions. That means at an airport and not just the Select a Flight menu visible. :( Lol. sure fsx is running sitting at an airport..>Finally, please advise which version of FSUIPC you're running. 'The latest' is not an acceptable reponse. :wink:vs 4.60ThanksVic

>Firstly, does WideClient say "Connected" in the title bar on your Client PC? If it doesn't then it's not 'speaking' to FS on the server PC.Nope it says waiting for a connection.

Check the IP address for the server PC in wideclient.ini. It sounds like it's not correct. Again, this is from memory.

>You do have FS running on the server PC don't you? Sorry to ask silly questions. That means at an airport and not just the Select a Flight menu visible. :( Lol. sure fsx is running sitting at an airport..

Okay, I had to ask. :(

>Finally, please advise which version of FSUIPC you're running. 'The latest' is not an acceptable reponse. :wink:vs 4.60

That's the current version - good.

Check the IP address for the server PC in wideclient.ini. It sounds like it's not correct. Again, this is from memory.Okay, I had to ask. :( That's the current version - good.

Ok I fixed the ip in the wideclient.ini.Now on top of the fsx window it says " fsx with wideserver:1 connected" and then it changes to "fsx with wideserver:waiting for clients" on my client pc it changes intermittently between connected to waiting for connection.Now when I launch radar contact I get the same error as before " maybe running on wideclient but fs not running on server or wrong fsuipc".what should I do now ?thanksVic

Ok I fixed the ip in the wideclient.ini.Now on top of the fsx window it says " fsx with wideserver:1 connected" and then it changes to "fsx with wideserver:waiting for clients" on my client pc it changes intermittently between connected to waiting for connection.Now when I launch radar contact I get the same error as before " maybe running on wideclient but fs not running on server or wrong fsuipc".what should I do now ?thanksVic

It sounds like the server PC is disconnecting the link or possibly, a firewall program like ZoneAlarm. Can you refer to page 4 of the WideFS User Guide please. This gives specific directions on how to configure your setup. Bear in mind I know nothing about your setup and there is more than one way of configuring things. I would go with how Pete suggests you do it.In my setup my WideServer.ini has a section :-[ClientNames]1=NONFLYING2=LAPTOPThose are the names of the other PCs in my setup. Do you have that in your wideserver.ini?If the above doesn't solve things you may be better posting on Pete Dowson's site as this is a WideFS problem, not a RC one. Pete's forum is here. http://forums.simfli...wforum.php?f=54You could post your wideclient.log and wideserver.log files here in case I can spot something.

Vic,It may help if I show you the logs from a successful connection of WideFS.Here is my WideServer.log********* WideServer.DLL Log [version 7.588] *********Blocksize guide = 4096 (double allowed)Date (dmy): 07/10/10, Time 19:03:07.984: Server name is FLYING 15312 Initialising TCP/IP server 15375 Initialising IPX/SPX server 15375 IPX/SPX socket() failed [Error=10047] Address family not supported by protocol family 15375 Failed to start IPX/SPX Server 15375 Initialising UDP/IP server 16109 Broadcasting service every 1000 mSecs 17750 Incoming connection Accepted ok (skt=9740) TCP 17812 Connected to computer "NONFLYING" running WideClient version 6.780 (skt=9740) TCP 109516 Error 10054: client socket disconnected at Client: removing (skt=9740) TCP 115687 Incoming connection Accepted ok (skt=9740) TCP 115906 Connected to computer "NONFLYING" running WideClient version 6.780 (skt=9740) TCP 147484 Error 10053: client socket disconnected at Client: removing (skt=9740) TCP 174250 Close signalled to clients 175359 Closing down now ...Memory managed: Offset records: 75 alloc, 74 freeRead buffer usage: 57 alloc, 57 free, max in session: 1Write buffer usage: 2292 alloc, 2292 free, max in session: 1Throughput maximum achieved: 32 frames/sec, 804 bytes/secThroughput average achieved for complete session: 6 frames/sec, 158 bytes/secAverage receive rate from "NONFLYING": 0 frames/sec, 9 bytes/sec********* Log file closed *********And here is my WideClient.log********* WideClient Log [version 6.78] Class=FS98MAIN *********Date (dmy): 07/10/10, Time 19:05:01.796: Client name is NONFLYING 313 Attempting to connect now 656 Server = FLYING 672 Trying TCP/IP host "FLYING" port 8002 ... 672 ... Okay, IP Address = 192.168.0.3 672 Connection made okay! 32438 ****** End of session performance summary ****** 32438 Total time connected = 30 seconds 32438 Reception maximum: 32 frames/sec, 776 bytes/sec 32438 Reception average whilst connected: 31 frames/sec, 773 bytes/sec 32438 Transmission maximum: 0 frames/sec, 19 bytes/sec 32438 Transmission average whilst connected: 0 frames/sec, 25 bytes/sec 32438 Max receive buffer = 348, Max send depth = 1, Send frames lost = 0 32438 ********* Log file closed (Buffers: MaxUsed 2, Alloc 1002 Freed 1002 Refused 0) *********The Server PC is named FLYING and the client is named NONFLYING. I manually configure the IP address of each PC rather than going with the automatic setting.I'm running XP but things should be the same for W7. Hope that helps but if not, Pete will get you sorted once you supply the two log files.LATER: You also need entries in FSUIPC4.INI. Here are mine..[WideServer]WideFSenabled=YesAdvertiseService=1Port=8002Port2=9002[ClientNames]1=LAPTOP2=NONFLYING

Hi Vic,this may seem like a silly question, but does your FS PC have a dual network adapter ?I had similar connection problems on my setup sometime ago, it turned out that with the dual adapter that there was a conflict. The solution was to configure them as a single highspeed adapter.Regards,................Adrian19

Ok I fixed the ip in the wideclient.ini.Now on top of the fsx window it says " fsx with wideserver:1 connected" and then it changes to "fsx with wideserver:waiting for clients" on my client pc it changes intermittently between connected to waiting for connection.Now when I launch radar contact I get the same error as before " maybe running on wideclient but fs not running on server or wrong fsuipc".what should I do now ?thanksVic

you've read the section in the rc manual on setting up rc on widefs, right?jd