Jump to content
The simFlight Network Forums

no connection


Recommended Posts

Hello Mr. Dobson it has been awhile that i have used widefs , and im having problems connecting.

first here is my log .

this is what im reading from the main computer log

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

Blocksize guide = 4096 (double allowed)

Date (dmy): 09/02/09, Time 09:55:29.281: Server name is THERMALTAKE

85562 Initialising TCP/IP server

85578 Initialising IPX/SPX server

85578 IPX/SPX socket() failed [Error=10044] Socket type not supported

85578 Failed to start IPX/SPX Server

85578 Initialising UDP/IP server

86234 Broadcasting service every 1000 mSecs

96922 Restarting service due to total lack of use

96922 Failed to start IPX/SPX Server

418969 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

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

this is the log from the client computer.

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

Date (dmy): 09/02/09, Time 09:55:01.930: Client name is ROBERTCAMPBELL

203 Attempting to connect now

1201 Trying to locate server: Need details from Server Broadcast

1201 Failed to connect: waiting to try again

3214 Attempting to connect now

4742 New Client Application: "AS2004" (Id=3512)

67751 Trying to locate server: Need details from Server Broadcast

what do you think i need to do to get it up.

im runnig fs9 on the main com , and i have radar contact and active sky on my second computer.

what am i doing wrong......Thanks..........Robert

Link to comment
Share on other sites

Hello Mr. Dobson

It's Dowson, actually, but most call me Pete.

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

Date (dmy): 09/02/09, Time 09:55:01.930: Client name is ROBERTCAMPBELL

203 Attempting to connect now

1201 Trying to locate server: Need details from Server Broadcast

Your client isn't receiving broadcasts from your Server. That could be because they are in different Workgroups -- that's the usual reason. If you don't want to make the workgroup names the same you must use the ServerName= and Protocol= parameters in the WideClient.INI file to tell WideClient where to connect. Please see the documentation supplied.

Regards

Pete

Link to comment
Share on other sites

Thanks for the reply and sorry for the error in your name .

im still must be doing somthing wrong .

im not for sure on work group names so i went in and set them up.

as far a work group names i name then the same on both computers. (camtech).

hers is the log on the client com.

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

Date (dmy): 09/02/09, Time 13:25:26.080: Client name is CAMTECH

172 Attempting to connect now

172 Trying TCP/IP host "camtech" port 8002 ...

172Okay, IP Address = 192.168.2.3

1186 Error on client pre-Connection Select() [Error=10061] Connection refused

1217 Ready to try connection again

2247 Attempting to connect now

13182 New Client Application: "AS2004" (Id=2364)

61933 Trying TCP/IP host "camtech" port 8002 ...

61933Okay, IP Address = 192.168.2.3

here is the log on the main com.

'

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

Blocksize guide = 4096 (double allowed)

Date (dmy): 09/02/09, Time 13:18:03.750: Server name is CAMTECH

86906 Initialising TCP/IP server

86922 Initialising IPX/SPX server

86922 IPX/SPX socket() failed [Error=10044] Socket type not supported

86922 Failed to start IPX/SPX Server

86922 Initialising UDP/IP server

88469 Broadcasting service every 1000 mSecs

98062 Restarting service due to total lack of use

98062 Failed to start IPX/SPX Server

655797 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

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

so at this moment im confused on where to go or what to do.

i did as your instructions said to do.

servername = camtech

protocol=TCP

that did not work so i tried the ips address.

the problem with that is im not for sure where to get that from.

Thanks again.....Robert

Link to comment
Share on other sites

im not for sure on work group names so i went in and set them up.

as far a work group names i name then the same on both computers. (camtech).

hers is the log on the client com.

Well, you have named both the Server PC and the Client PC "camtech"!!!

Each PC must have a unique NAME! How else can they be identified?

You've now told WideClient to connect to a WideServer on the same PC as itself:

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

Date (dmy): 09/02/09, Time 13:25:26.080: Client name is CAMTECH

172 Attempting to connect now

172 Trying TCP/IP host "camtech" port 8002 ...

172Okay, IP Address = 192.168.2.3

All PCs you want to work together should normally be in the same workgroup. But EVERY PC needs a unique name! Looks again at where you set the name. There's a workgroup name too. See it? Change that to be the same, change your PC names to be unique!

Pete

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 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.