Msg # 14 unable to connect, need help! please

[RFenner]

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

Date (dmy): 18/02/08, Time 16:04:34.189: Client name is ROB3GIGDELL

921 Attempting to connect now

1922 Trying to locate server: Need details from Server Broadcast

1922 Failed to connect: waiting to try again

3925 Attempting to connect now

68208 Trying to locate server: Need details from Server Broadcast

69109 New Client Application: "FSC82" (Id=568)

194760 Trying to locate server: Need details from Server Broadcast

1032394 ****** End of session performance summary ******

1032394 Total time connected = 0 seconds

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

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

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

1032394 **************** Individual client application activity ****************

1032394 Client 568 requests: 30 (Ave 30/sec), Data: 1620 bytes (1620/sec), Average 54 bytes/Process

1032394 ********* Log file closed (Buffers: MaxUsed 1, Alloc 30 Freed 30 Refused 0) *********

[Pete Dowson]

What's "Msg #14"?

1922 Trying to locate server: Need details from Server Broadcast

1922 Failed to connect: waiting to try again

3925 Attempting to connect now

68208 Trying to locate server: Need details from Server Broadcast

...

194760 Trying to locate server: Need details from Server Broadcast

I would have thought it would be only polite to actually enter some text in your message, not just baldly shove a log file under my nose and expect miracles! After all, don't you want to provide any other information at all to explain why you don't know what the problem is? After all the log does actually tell you what is wrong, if you look at it -- see above!

It "needs details from Server Broadcast" because it hasn't been told where to connect to. If it isn't receiving broadcasts then either the Server or the Client is running an older operating system which didn't support them, or they are in different Windows workgroups. Since you don't tell me anything about either PC, nor even what version of FS you are trying to use, I can't say much more about why it isn't seeing them.

Read the section in the WideFS User Guide entitle "Configure your network", and especially note paragraph 3 in that section.

Next time you ask for help please bring rather more useful data with you, please, and maybe a few words of explanation.

Pete

[RFenner]

Pete, sorry, the whole message didnt get put on the forum.

Im running FScommander 8.2.2 on my laptop, have the newest versions of Wide and fsuipc on the main computer and am running FSX with acceleration.

I followed the instructions in the network config and FS commander sees the install of FSX for its parts.

I put the wide client.dll and ini in the fs commander folder as per directions.

I started wide as directed, then fs commander, when i try the connect to FS option i get the msg #14 error.

im not real literate with these programs so please forgive my lack of details

Repectfully,

Robert

[Pete Dowson]

Im running FScommander 8.2.2 on my laptop, have the newest versions of Wide and fsuipc on the main computer and am running FSX with acceleration.

Right. So the Server must be running WinXP or Vista. But what is the Laptop running? If not XP or Vista you would need to add the parameters as described in the paragrpah I pointed you too.

Are both PCs in the same WorkGroup? If not the same applies, as Broadcasts only go to Workgroup members.

Where's the WideServer log file, please? That too is relevant you know.

I followed the instructions in the network config

What instructions? You've obviously not added the ServerName and Protocol parameters, for instance.

I started wide as directed, then fs commander, when i try the connect to FS option i get the msg #14 error.

I'm sorry, I've no idea still what "Msg #14" means.

Regards

Pete

[RFenner]

Pete,

Both computers are runiing Win XP with latest patches.

I included the wide server log file below.

As stated im kinda illiterate with this and not sure what should go into these ini files.

I added SeverName= and included the name shown in the wide server file. I have no idea what protocols are, so I havent done anything with that one.

Could you show me what a correct ini file would look like?

I really appreciate your time and understand your labor of love with FS, as I'm sure that there are others like me that cause you to pull out your hair.

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

Blocksize guide = 4096 (double allowed)

Date (dmy): 18/02/08, Time 20:20:10.936: Server name is HOME-728FF1256D

15203 Initialising TCP/IP server

15203 Initialising IPX/SPX server

15203 IPX/SPX socket() failed [Error=10047] Address family not supported by protocol family

15203 Failed to start IPX/SPX Server

15203 Initialising UDP/IP server

16015 Broadcasting service every 1000 mSecs

[Pete Dowson]

Both computers are runiing Win XP with latest patches.

I included the wide server log file below.

In that case the broadcasting should certainly work fine. It sounds like your PCs are not in the same workgroup. Check that (My Computer Properties, Computer Name dialogue) and change one to match the other.

As stated im kinda illiterate with this and not sure what should go into these ini files.

I added SeverName= and included the name shown in the wide server file.

Looks like you need to use cut and paste, because it won't work with "SeverName" as the parameter, it needs "ServerName", as it says.

I have no idea what protocols are, so I havent done anything with that one.

Why on Earth not simply copy what it tells you then? Why do you think I give such explicit examples? I pointed you to the exact paragraph. It gave you the two lines to insert. What more could you ask for? You used the ServerName line but not the Protocol line? Why? :roll:

Regards

Pete

[RFenner]

Pete,

Thanks for the help. I still had problems even after I had added those lines correctly. I did spell it right in the .ini by the way, and had added both lines. I hadnt added it at first because the documentation said it wasnt necessary since XP was supposed to sort it out.

The problem in the end was the fact that the client was resolving the ip to a different number than my router was telling me, and the fact that netbios and some other odd options in the network card were off.

I have it sorted out now I think and its working fine!

Regards,

Robert

[Pete Dowson]

Thanks for the help. I still had problems even after I had added those lines correctly. I did spell it right in the .ini by the way, and had added both lines. I hadnt added it at first because the documentation said it wasnt necessary since XP was supposed to sort it out.

Yes, it is.

The problem in the end was the fact that the client was resolving the ip to a different number than my router was telling me, and the fact that netbios and some other odd options in the network card were off.

Oh, right. I never understood all that stuff. Sorry.

I have it sorted out now I think and its working fine!

Goodyou are obviously nowhere near as "illiterate" as you made out! ;-)

Regards

Pete