waiting for clients

[FLYPAST]

Hello all

Wide client won't connect to the main FS9 PC. I have read the other threads regarding this and I have tried all the suggestions but still no joy.

Everything in the LAN and internet settings all indicate a connection.

Any ideas would be welcome.

Thank you

Alan W

[Pete Dowson]

You posted into the FAQ subforum, which is the permanent repository for ANSWERS to Frequently Asked Questions. It is NOT the Support forum, so I moved your question here. Please use the Support Forum in future.

Wide client won't connect to the main FS9 PC. I have read the other threads regarding this and I have tried all the suggestions but still no joy.

There's no way I can help with no information. When reading all those other threads didn't you notice that things like version numbers and Logs are needed?

Please always state the version numbers of the FSUIPC, WideServer and WideClient you are using. Close FS and WideClient down. Then find the log files: FSUIPC.LOG and WideServer.Log in the FS9 modules folder, and WideClient.log in the same folder as your Wideclient.exe on the client PC. Paste them into a message in this thread.

Everything in the LAN and internet settings all indicate a connection.

Internet connection is irrelevant.

Regards

Pete

[FLYPAST]

Thank you Peter

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

Date (dmy): 03/04/11, Time 10:37:17.687: Client name is AW-PC03

813 Attempting to connect now

1813 Trying to locate server: Need details from Server Broadcast

1813 Failed to connect: waiting to try again

3813 Attempting to connect now

33282 ****** End of session performance summary ******

33282 Total time connected = 0 seconds

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

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

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

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

****** FSUIPC, Version 3.989w by Pete Dowson *********

Running on Windows Version 5.1 Build 2600 Service Pack 3

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="Alan Watson"

User Addr="aoh63@blueyonder.co.uk"

FSUIPC Key is provided

WideFS Key is provided

Module base=61000000

WeatherReadInterval=4

LogOptions=00000001

DebugStatus=255

57531 System time = 03/04/2011 10:05:21

57547 \\AW-01\Flight Simulator 9\

57547 System time = 03/04/2011 10:05:22, FS2004 time = 12:00:00 (00:00Z)

77422 \\AW-01\My Documents\Flight Simulator Files\EGKK Gate 58 default flight.flt

77578 AIRCRAFT\PMDG737-800\B737-800.air

78984 Aircraft="B737-800 British Airways"

91687 ERROR: Can't change message filter: functions not available

102437 \\AW-01\My Documents\Flight Simulator Files\EGKK Gate 58 default flight.flt

103625 Clear All Weather requested: external weather discarded

106187 Advanced Weather Interface Enabled

3789515 WeatherOptions set, now 0000B0A7 (timer=0)

4752562 System time = 03/04/2011 11:23:37, FS2004 time = 17:22:56 (17:22Z)

4752562 *** FSUIPC log file being closed

Memory managed: 50 Allocs, 55470 Freed

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

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

Blocksize guide = 4096 (double allowed)

Date (dmy): 03/04/11, Time 10:05:27.328: Server name is AW-01

152438 Initialising TCP/IP server

152469 Initialising IPX/SPX server

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

152469 Failed to start IPX/SPX Server

152469 Initialising UDP/IP server

152469 Broadcasting service every 1000 mSecs

163734 Restarting service due to total lack of use

163781 Failed to start IPX/SPX Server

4692109 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 *********

Regards,Alan

[Pete Dowson]

1813 Trying to locate server: Need details from Server Broadcast

1813 Failed to connect: waiting to try again

I thought you said you'd checked other threads? This is the most common symptom, often mentioned and resolved, where the Server is sending broadcasts which the client never sees. It is because the server and client PCs are in different workgroups. This has occurred innumerable times since Microsoft released Vista and Win 7, because those two systems set a different Workgroup name to WinXP.

Did you think to check the supplied documentation? Please read the part where there's a RED notice asking you to at least read some of it. It isn't very far down, in the User guide. It tells you how you can override the automatic connection, if you don't want to name your workgroups the same.

Pete

[FLYPAST]

Hello Peter

I've looked and can't find the part in 'red' you mention. Can you help?

Thank you

Alan W

[Pete Dowson]

I've looked and can't find the part in 'red' you mention. Can you help?

Only the banner asking you to read what follows is in red. it is so highlighted so you cannot miss it! So how on Earth do you manage to do just that? The document is obscurely named, perhaps, "WideFS User Guide"? The part so headed is in a section called "configuring your network" which is part of the Installation section, and occurs on the 4th page. How could it be in such an appropriately named place in an appropriately named document and still have escaped your attention so completely? :-(

Pete

[FLYPAST]

For some unknown reason I have 2 wideFS user guides and one has no highlighted 'in red' printed in it. However I have found a copy that does but this does not help me because I don't understand it.

I would like to say at this point following your last reply I am 48 years old not 8 yet you choose to answer with sarcasm which is not only rude but unnecessary.

I have come to you for help.It is not my fault I don't possess as much knowledge as some with regard to computing. If I could resolve this issue I would. It is spoiling my enjoyment of my hobby so I would very much appreciate it if you could perhaps give me step by step instructions.

I am not stupid and I respond well to instructions.

That said thank you for your support so far.

Regards

Alan W

[Pete Dowson]

For some unknown reason I have 2 wideFS user guides and one has no highlighted 'in red' printed in it.

Sounds like you've got some pretty old stuff there. The current and correct user guide is actually supplied inside the very same Zip file as the versions of WideFS you are using, so how could you have got some really old ones mixed up?

However I have found a copy that does but this does not help me because I don't understand it.

It tells you what parameters to add to the INI file in Wideclient if you need to tell it to link to the Server explicitly. Please tell me what there is to not understand. I really wouldn't know any way to desdcribe it clearer, that's why it is written there.

I am not stupid and I respond well to instructions.

Please explain, then, what it is you do not understand. The instructions are there in black and white (below the red bit). Look, here is the EXACT information extracted from that section:

However, if you find the connection is still 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

I cannot actually edit your INI file, you need to do that! If you don't know the name of your Server PC you can see it in the Server log you posted:

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

Blocksize guide = 4096 (double allowed)

Date (dmy): 03/04/11, Time 10:05:27.328: Server name is AW-01

How much more explicit can it be? And how is it you never saw any such suggestions in all the other threads you said you viewed?

:-(

Pete

[FLYPAST]

Hellp Peter

I've now added the lines but still no response.

Any other suggestions would be welcome-thank you

Alan W

[Pete Dowson]

I've now added the lines but still no response.

Please show me the WideClient log file. It will no longer be waiting for a Broadcast from the Server, so there will be another reason your Server is not seen. Possibly a firewall?

Pete

[FLYPAST]

Thank you

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

Date (dmy): 03/04/11, Time 17:43:18.828: Client name is AW-PC03

891 Attempting to connect now

1891 Trying to locate server: Need details from Server Broadcast

1891 Failed to connect: waiting to try again

3891 Attempting to connect now

67891 Trying to locate server: Need details from Server Broadcast

277141 ****** End of session performance summary ******

277141 Total time connected = 0 seconds

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

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

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

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

[Pete Dowson]

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

Date (dmy): 03/04/11, Time 17:43:18.828: Client name is AW-PC03

891 Attempting to connect now

1891 Trying to locate server: Need details from Server Broadcast

1891 Failed to connect: waiting to try again

Oh dear. As you can see (did you look at all?) it is still doing the same thing. Seems you didn't actually edit the WideClient INI file as instructed! Please go back and check it.

If you really think you've edited it correctly, please show me that file so i can see.

BTW did you not bother to see if you could put both your PCs in the same workgroup, so you wouldn't need to edit any file in the first place?

Pete

[FLYPAST]

I can't actually find the ini file on the clieny machine. I thought I had but clearly not.I have looked but not finding it. Any help on this one?

Thank you

Regards

Alan

[Pete Dowson]

I can't actually find the ini file on the clieny machine. I thought I had but clearly not.I have looked but not finding it. Any help on this one?

You posted exactly the same question in the same thread twice. Why? Please don't. It only makes extra work to no avail.

If there is no WideClient.INI file in the folder on the Client PC where you placed WideClient.EXE, then

1. You could never have run WideClient, because it always makes an INI file as well as a LOG file.

AND

2. You could not possibly have added the two parameters as instructed to the file because it doesn't exist! So why say you did?

Now this really seems very unlikely because you actually showed me a Log from WideClient -- the INI file would be right next to it, in the same folder. So, all I can think is that you are not looking in the right place. Maybe you've forgotten where you put wideClient? If so, check the properties of the short-cut I assume you are using to start it.

I can see this is going to take a long time. It's getting late here now so it'll be sometime tomorrow now ....

Pete

[FLYPAST]

You posted exactly the same question in the same thread twice. Why? Apologies.

I have a wide client folder on the desktop and in this folder is cfg settings, widefs0log and widefs log. The shortcut is on the desktop. There is nothing to suggest a .ini file.

I've searched high and low and I'm sorry this is happening but I'm trying my best here. Sure you will agree it is difficult resolving issues in this manner?

Regards

Alan

[Pete Dowson]

I have a wide client folder on the desktop and in this folder is cfg settings, widefs0log and widefs log. The shortcut is on the desktop. There is nothing to suggest a .ini file.

You have Windows set to hide known file types from you. The filetype "INI" is short for "INITIALISATION SETTINGS", which is another term for configuration settings, so Windows reference to 'cfg settings' should certainly suggest such! That IS the "wideclient.ini" file!

Please tell me, how did you manage, as you confirmed, to add those parameter lines as instructed to a file you couldn't find? Something isn't making any sense here!

If you want to see filenames correctly, and I recommend you do, please open the Folder Options in Windows Explorer and uncheck the option to hide known filetypes from you.

Pete

[FLYPAST]

Hello Peter

Ok I have had a look around and these are my findings.

On my main PC the one that FS9 is installed,in network places there is 1394 connection connected Firewalled 1394 Net adaptor properties of which are

192.168.1.1

255.255.255.0

192.168.1.1

preferred DNS server 192.168.1.1

Under the LAN TCP/IP properties is 'obtain IP address automatically

---------------------------------------------------------------------------

In the PC with Wide Client installed I found the following

Local area connection connected Braodband NetXtreme Gigabit E....

IP/TCP properties

192.168.1.7

255.255.255.0

192.168.1.7

Preferred DNS server 192.168.1.7

------------------------------------------------------

In wide client CFG I have added Protocol TCP and server PC which is the main FS PC? - AW-01, and saved the settings.

As a point of interest I said I couldn't find the .ini file on the client machine, yet on a remote PC (named AW-PC-04) I can see the wide client .ini file?!!

I also have the show hidden files checked.

Anyway that is where I am at the moment?

If you can shed some light on this I would be grateful

Regards

Alan

[Pete Dowson]

Ok I have had a look around and these are my findings.

Sorry, but really none of that is really of any relevance. I don't need and didn't ask for that information.

In wide client CFG I have added Protocol TCP and server PC which is the main FS PC? - AW-01, and saved the settings.

What is "wideclient CFG"? The only configuration file for Wideclient is Wideclient.INI.

As a point of interest I said I couldn't find the .ini file on the client machine, yet on a remote PC (named AW-PC-04) I can see the wide client .ini file?!!

Sorry, I have no idea what you are talking about there.

If you cannot find Wideclient.INI how on Earth are you adding any parameters to it?

I also have the show hidden files checked.

That's completely irrelevant. None of the files any of my programs use are hidden.

Sorry, but you are losing me, going off at a tangent?

As I said right at the beginning of this ever-lengthening thread, the problem you really have is simple. The two PCs are not in the same workgroup. Fixing that might be a lot quicker than adding two lines to a file you don't seem to be able to even find. did you ever even check the workgroup names on each PC?

If you've no idea how, it is like this:

On XP, right click on "My Computer", select Properties, then Computer Name. There you will see your computer name AND your workgroup name. And you can change either using the Change button.

On Vista and Win7 you right click "Computer" and select properties, and the details are shown where it says "computer name ...", and you can change them by using the Change Settings button.

Regards

Pete

[FLYPAST]

Good morning to you Peter

Thank you for your latest response. I'm sure you are very busy and I appreciate your time and effort to help me resolve the issue I have experienced which is in fact now resolved.

I hope you have a nice day and once again thank you for your continued support.

Kind regards

Alan W