WideFS not seeing FS2004

[kdundon]

Peter,

I have been using WideFs for years now and have done so without any big problems. Yesterday I moved my computers and whatnot to a new location in the house and now Wideclient does not connect to FS2004 I have attached my Wideclient Ini and Log and WideServer ini and log. I have tried putting the latest versions in (the 3.507 ver) and nothing happens. I go to network connections and I can see the computer, the FS directory and everything else as before but for some reason it wont connect. Hopefully you can see what the problem is in my ini files or the log files. Ken

WideFS Problem.zip

[Pete Dowson]

... I moved my computers and whatnot to a new location in the house and now Wideclient does not connect to FS2004 I have attached my Wideclient Ini and Log and WideServer ini and log. I have tried putting the latest versions in (the 3.507 ver) and nothing happens. I go to network connections and I can see the computer, the FS directory and everything else as before but for some reason it wont connect.

What are you thinking of, putting this parameter in the WideClient INI file:

ServerName=192.168.0.101

?

That isn't a name! It's an IP address. Please check the WideFS documentation.

Although, somehow (I don't know how), Windows does seem to recognise something with that "name" as something with the same IP address, it is a very odd way to misuse the WideClient parameters. As far as I can see it probably isn't even the correct IP address. Why not use the actual Name to save having to worry about such obscure things? Your ServerName is apparently "DADS" (see the WideServer LOG). It's a whole lot easier. You seem to want to make it difficult? ;-)

In any case, if you are using Windows XP on both PCs you don't need to give either the ServerName or ServerIPaddr. Clients will find the Server automatically. It's one of the new facilities since 6.50. Again please see the documentation.

Pete

[kdundon]

For the last 12 hours I have read the instructions, installed and tested the program at least 40 times. I have tried the new version that does not need the Servername and have put the name in as you said to no avail. I know I am not a computer programming expert like you and some of the other posters here but I had a legitimate problem I thought you could help me with. It is obvious however that since I am not as good with computer programming as the rest I am not worthy of your help. I will figure this problem out on my own as you have suggested. Sorry to have bothered you. Have a nice day. Ken

[Pete Dowson]

For the last 12 hours I have read the instructions, installed and tested the program at least 40 times. I have tried the new version that does not need the Servername and have put the name in as you said to no avail.

So, even with the correct parameters (which you did not show me), it still does not see the Server? There is no error reported in the logs you sent, merely a timeout at both ends though lack of any connection.

Can you show me files relating to your attempts with the correct parameters? Maybe there are then more clues?

I know I am not a computer programming expert like you and some of the other posters here but I had a legitimate problem I thought you could help me with.

Yes, the problem in the files you sent were that the parameters were incorrect. You put the IP address in the Server name parameter. I suggested trying both using the ServerName ("DADS"), and even, if you have Windows XP installed in both, leaving both Server parameters out.

Neither of these steps require you to be a computer programmer, surely? I don't know where you get that idea from. I did say that all these things are mentioned in the documentation. I assumed you had not bothered to look, otherwise you woyuld have surely realised that the word "ServerName" is not same as "ServerIPaddr"? The WideServer log even explicitly tells you the Server name (DADS) in case you don't know how to find it!

Now that you have tried the suggestions I made, without success, perhaps you could show me the results so that we can move on?

It is obvious however that since I am not as good with computer programming as the rest I am not worthy of your help. I will figure this problem out on my own as you have suggested. Sorry to have bothered you. Have a nice day. Ken

That is the weirdest response and attitude I have come across in a very long time! Where are you coming from on this? You say you have a problem, and send me files. I study them and make at least two suggestions as to why it may not be working and things you should try, and you react so crazily?

If you don't want any more help, that's fine, but I don't understand why you should bring in all this irrelevant stuff about programming and "not being worthy" (?) as an excuse. I help as much as I can with the information I am given and at the same time try to encourage folks to find ways to help themselves. If you are doing the latter now, that's fine. If not, let me know..

Pete

[kdundon]

Peter, excuse my last note as I was tire and had been at it all day with not joy on the connection. I attached another set of files showing Wideclient with and without the ServerName=Dads in it. I also included the WideServer log. I did not start any program other than Flight Sim and Wideclient. One thing I noted last night was that when I had Quickmap build 130 running it would say Not connected then it would put a FS 0/0 in the center of the map and the Not connected would go away like it was connected but it never moved to the airport I was at. I don't know if this is any help but it was a bit odd. I am going to try some other things to see if it is related to virus scanning software or my firewall. I did disable the fire wall (zonealarm) but it made no difference. Ken

[kdundon]

Peter, sorry forgot to attach the files. Ken

WideFS Problem.zip

[Pete Dowson]

Peter, sorry forgot to attach the files. Ken

Okay. The log named "WideClientWithServerName.Log" shows:

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

Date (dmy): 28/11/05, Time 07:33:11.294: Client name is KENS

1122 Attempting to connect now

1152 Trying TCP/IP host "dads" port 8002 ...

1152Okay, IP Address = 192.168.1.101

or, on the other hand, the other Log (just named "WideClient.Log") shows:

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

Date (dmy): 28/11/05, Time 07:30:59.545: Client name is KENS

1112 Attempting to connect now

1712 Server = DADS

1732 Trying TCP/IP host "DADS" port 8002 ...

1732Okay, IP Address = 192.168.1.101

So both methods work in the sense that the Server PC is identified correctly. So you can leave both the Server Name and IPAddr parameters out.

However, please look at the IP address:

192.168.1.101

In your previous set of files you were actively setting the IP address as

192.168.0.101

If the so-called "subnet mask" is set to its usual default, 255.255.255.0, then the difference between that 1 and that 0 could be absolutely crucial! I think that BOTH PCs MUST BE ON THE SAME "SUBNET". In fact all PCs you want to work with each other should be on the same subnet. Check the IP address of the Client PC -- if that is not 192.168.1.??? (??? is anything), then you either need to change it, or change the Subnet Mask so that the 0 and 1 difference does not matter (e.g. change it to 0).

I don't know how you managed to get the Network into this sort of mess. Are you setting IP addresses explicitly, or letting them be assigned by a Router or something? Maybe you are assigning one explicitly and the other automatically? You need to be consistent.

This is really all in the realms of Networks which I know little about, by the way. It is nothing to do with programming. I had to figure out how to get my Networks configured by reading Windows Help and using trial and error. I know it isn't easy and I'm sorry if I'm not good at explaining things I know little about. But let me know if you cannot find where all this stuff is set or examined. I can help you there.

Pete

[kdundon]

Thanks, I figured it would be the network but not sure what step to take first. I guess it is time to get some money back from my investment of my sons education. He is a network guru. Like you I have trouble with the network end of things. I will try the subnet part and see if it makes any difference. Ken

[kdundon]

Ok, not sure what exactly I did but I went into MSCONFIG and started up a few services I had stopped and now everything is working as advertised. It definately was the network like you said. I used the new test versions and they are working great. Thanks for your suggestions Peter. They definetly led me to a solution even though I am not sure what caused it. I am tempted to disable services one at a time to see which one it was but now that its working I am going to leave well enough alone. Ken

[Pete Dowson]

Ok, not sure what exactly I did but I went into MSCONFIG and started up a few services I had stopped and now everything is working as advertised.

Ah, yes. When stopping Windows services you need to be pretty careful. I only ever did it one at a time, eventually settling on a set of disabled ones after weeks.

Thanks for letting us know.

Pete