Jump to content

Cannot connect to Client Pc to Server PC using FSUIPC/WideFs


Recommended Posts

I'm trying to connect "FS Commander" (registered ver.7.7 patches 1, 2 and 3, also FSUIPC is registered) installed on the client computer "DUKE6", it appears that the Commander sw loads on OK, however, when clicking on the GPS icon the message "cannot connect" appears.

Also I'm listing a the pertinent files that may hep you desifer my predicament.

All other side SW's instaled on several Client PCs that work with info provided from FS9 located the server (DUKE1) , seams to work flawlesly.

Please Help.

Thanks, Emil

********* WideServer.DLL Log [version 6.72] *********

Blocksize guide = 4096 (double allowed)

Date (dmy): 08/06/07, Time 21:56:17.765: Server name is DUKE1

40719 Initialising TCP/IP server

40719 Initialising IPX/SPX server

40734 ServerNode=0.0.3072.44529.19169

40734 Initialising UDP/IP server

42156 Broadcasting service every 1000 mSecs

52375 Restarting service due to total lack of use

1348531 Closing down now

Memory managed: Offset records: 0 alloc, 0 free

Read buffer usage: 0 alloc, 0 free, max in session: 0

Write buffer usage: 0 alloc, 0 free, max in session: 0

Throughput maximum achieved: 0 frames/sec, 0 bytes/sec

Throughput average achieved for complete session: 0 frames/sec, 0 bytes/sec

Server PC named "DUKE1" FSUIPC log file

; PLEASE SEE the documentation for parameter details

; ==================================================

[Config]

Port=8002

AdvertiseService=1

AutoRestart=0

AutoUpdateTime=13

MaximumBlock=4096

NoStoppedRestarts=Yes

Port2=9002

RestartTime=10

SendTimeout=15

TCPcoalesce=No

; -----------------------------------------------

[user]

Log=Errors+

; ===============================================

********* FSUIPC, Version 3.74 by Pete Dowson *********

Running on Windows Version 5.0 Build 2195 Service Pack 4

Verifying Certificate for "C:\Program Files\Microsoft Games\Flight Simulator 9\MODULES\FSUIPC.dll" now

SUCCESS! Signature verifies okay!

Running inside FS2004 (FS9.1 CONTROLS.DLL, FS9.1 WEATHER.DLL)

User Name="Emil Horvath"

User Addr="emilh09@ca.rr.com"

FSUIPC Key is provided

WideFS Key is provided

Module base=61000000

ClassOptions: UIPCMAIN=FF7F, FS98MAIN=FF7F, FS2KMAIN=FF5E

WeatherOptions(Orig)=40003605[40003605]

InitDelay: 0 seconds

WeatherReadInterval=4

LogOptions=00000001

DebugStatus=255

3687 System time = 22:15:14

3687 \\DUKE1\Flight Simulator 9\

3687 System time = 22:15:14, FS2004 time = 12:00:00 (00:00Z)

6015 FLIGHTS\OTHER\FLTSIM.flt

6031 AIRCRAFT\c172\Cessna172SP.air

6250 Aircraft="Cessna Skyhawk 172SP"

9109 Advanced Weather Interface Enabled

163171 C:\Documents and Settings\Administrator.DUKE1\My Documents\Flight Simulator Files\UI generated flight.flt

163359 Clear All Weather requested: external weather discarded

177093 Traffic File #16 = "scenery\world\scenery\traffic030528"

[Log closed by user request, and continued in new file]

268000 System time = 22:19:39, FS2004 time = 22:15:23 (05:15Z)

268000 *** FSUIPC log file being closed

Memory managed: 0 Allocs, 354 Freed

********* FSUIPC Log file closed ***********

Server PC FsWide log file;

********* WideClient Log [version 6.72] Class=FS98MAIN *********

Date (dmy): 08/06/07, Time 21:45:30.187: Client name is DUKE1

218 Attempting to connect now

1218 Trying to locate server: Need details from Server Broadcast

1218 Failed to connect: waiting to try again

3218 Attempting to connect now

67218 Trying to locate server: Need details from Server Broadcast

620531 ****** End of session performance summary ******

620531 Total time connected = 0 seconds

620531 Reception maximum: 0 frames/sec, 0 bytes/sec

620531 Transmission maximum: 0 frames/sec, 0 bytes/sec

620531 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0

620531 ********* Log file closed (Buffers: MaxUsed 0, Alloc 0 Freed 0 Refused 0) *********

Client PC named "DUKE6" config file;

; PLEASE SEE WideFS documentation for parameter details

; =====================================================

[Config]

Port=8002

Window=599,394,672,290

Visible=Yes

ButtonScanInterval=20

ClassInstance=0

NetworkTiming=5,1

MailslotTiming=2000,1000

PollInterval=2000

Port2=9002

ResponseTime=18

ApplicationDelay=0

TCPcoalesce=No

WaitForNewData=500

MaxSendQ=100

OnMaxSendQ=Log

NewSendScanTime=50

Priority=3,1,2

; -----------------------------------------------

[user]

Log=Errors+

; ===============================================

This log file is on the "client" PC named "DUKE6" which is correct.

1st try to connect;

********* WideClient Log [version 6.75] Class=FS98MAIN *********

Date (dmy): 08/06/07, Time 22:05:21.171: Client name is DUKE6

172 Attempting to connect now

1172 Trying to locate server: Need details from Server Broadcast

1172 Failed to connect: waiting to try again

3172 Attempting to connect now

17187 New Client Application: "FSC" (Id=296)

67406 Trying to locate server: Need details from Server Broadcast

361562 ****** End of session performance summary ******

361562 Total time connected = 0 seconds

361562 Reception maximum: 0 frames/sec, 0 bytes/sec

361562 Transmission maximum: 0 frames/sec, 0 bytes/sec

361562 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0

361562 **************** Individual client application activity ****************

361562 Client 296 requests: 15 (Ave 15/sec), Data: 810 bytes (810/sec), Average 54 bytes/Process

361562 ********* Log file closed (Buffers: MaxUsed 1, Alloc 15 Freed 15 Refused 0) *********

2nd try to connect;

********* WideClient Log [version 6.75] Class=FS98MAIN *********

Date (dmy): 08/06/07, Time 22:12:38.375: Client name is DUKE6

109 Attempting to connect now

1109 Trying to locate server: Need details from Server Broadcast

1109 Failed to connect: waiting to try again

3109 Attempting to connect now

22390 ****** End of session performance summary ******

22390 Total time connected = 0 seconds

22390 Reception maximum: 0 frames/sec, 0 bytes/sec

22390 Transmission maximum: 0 frames/sec, 0 bytes/sec

22390 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0

22390 ********* Log file closed (Buffers: MaxUsed 0, Alloc 0 Freed 0 Refused 0) *********

Link to comment
Share on other sites

I'm trying to connect "FS Commander" (registered ver.7.7 patches 1, 2 and 3, also FSUIPC is registered) installed on the client computer "DUKE6", it appears that the Commander sw loads on OK, however, when clicking on the GPS icon the message "cannot connect" appears.

You don't say what versions of Windows you are using, but possibly the Client isn't Windows XP or later? Either that or they aren't both in the same Workgroup.

You should add the ServerName= and Protocol= parameters to the WideClient.INI file, as described in the documentation, because the client evidently cannot see the broadcasts from the Server. All that stuff is only possible automatically on later Windows operating systems with all PCs in the same workgroup.

Really you should have found this out by reading just a few pages of the WideFS User guide. In the section "Configure your Network" you will see this quite clearly stated:

To use TCP/IP in a client you shouldn’t need to do anything to either Server or Client configurations providing both are running Windows XP, 2000, or Vista. However, if you find the connection is not happening, or you have more than one Server and it is connecting to the wrong one, then you will need to add these lines to the [Config] section of the WideClient.ini file (add the [Config] section too if your ini file hasn’t even got one!):

ServerName=NameOfServer

Protocol=TCP

Incidentally the current, supported, version of FSUIPC3 is 3.75, not 3.74. There's also a version 6.75 of WideFS out. Neither will make any difference here, but you should really keep up to date as far as possible and certainly before asking for help, just in case.

Regards

Pete

Link to comment
Share on other sites

Thank you for your prompt reply.

The Server OPSystem is Win2000 and the Clients OPsys are WinXPs.

Yes, the instructions you refered to I have read, but to one that only knows enough about computers to be dangerous, is somewhat eluding.

I will try your suggestion, thanks again!

Best regards, Emil :oops: :oops: :oops:

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.