Delta Virtual Airlines Water Cooler | PC Support |
WideFS failure |
DVA6497
Captain, B747-400
Joined on January 15 2006
Everett 250 Club
Triple Century Club
DVA Ten-Year Anniversary
"RLTW" Kerkrade, Limburg NL
366 legs, 574.8 hours
14 legs,
20.0 hours online 365 legs,
568.9 hours ACARS
|
Posted onPost created on
June 18 2009 15:31 ET by Ken Tucker
|
I had recently reloaded my windoze box from a known good image and now I'm having a problem where WideFS simply quit connecting about a week after the reload. As far as I can tell, there have been no significant network or OS changes to cause this since the reload. The client and FS side can ping each other, they see shares on each other, there are no AV restrictions (none installed for testing/validation purposes) and both connect to the 'Net as before. For kicks and giggles, I even added the .exe to my wife's computer (don't tell her!) and it, too, was unable to connect to the FS box. I "reinstalled" the widefs components on both sides, without effect. Naturally, both FSUIPC and WideFS are registered. I've posted this on Pete Dowson's support forum, however, he's on holiday until the end of the month. Thanks for the help.
Cheers!!
Ken TuckerCaptain, B747-400
|
|
AFV153
Senior Captain, A320
Joined on January 12 2009
Double Century Club
"Brace yourselves this might be bumpy" Sandwell GB
207 legs, 362.1 hours
207 legs,
362.1 hours ACARS
|
Posted onPost created on
June 18 2009 16:25 ET by Dave Gandolfo
|
Hi ken
I have just reinstalled my PC after a disaster with Windoze 7, I too was having problems with WideFS taking literally 5 minutes to connect.
I ended up setting the servername in the wideclient.ini file and setting up an lmhosts file in windows on the wideclient PC so the windows networking resolution is instantaneous rather that dragging its feet and trying various methods which all fail until 5 minutes later it eventually decides it can see the FS machin and connects.
Are you using static IP addresses or are you using DHCP from you router (I assume you have a router)?
Do you know what an lmhosts file is? (if you do it makes life a lot easier :D)
Dave GandolfoSenior Captain, A320
|
|
DVA6497
Captain, B747-400
Joined on January 15 2006
Everett 250 Club
Triple Century Club
DVA Ten-Year Anniversary
"RLTW" Kerkrade, Limburg NL
366 legs, 574.8 hours
14 legs,
20.0 hours online 365 legs,
568.9 hours ACARS
|
Posted onPost created on
June 19 2009 01:44 ET by Ken Tucker
|
Dave,
Thanks for the reply! My Cisco 1751 provides DHCP for the wireless stuff but these particular boxes are static. I'd not thought of the lmhost as WideFS had worked before but am trying that now. I'll let ya'll know how that works.
Cheers!!
Ken TuckerCaptain, B747-400
|
|
AFV153
Senior Captain, A320
Joined on January 12 2009
Double Century Club
"Brace yourselves this might be bumpy" Sandwell GB
207 legs, 362.1 hours
207 legs,
362.1 hours ACARS
|
Posted onPost created on
June 19 2009 02:58 ET by Dave Gandolfo
|
Ken,
I forgot to say, I also added the protocol line to the wideclient.ini file so it doesnt waste time trying TCP, UDP and IPX ( I would imagine it wouldnt realy try unless you have IPX installed).
ServerName=netbios name of your fs machine
Protocol=TCP
Yeah, my wideFS worked perfectly before I decided to give Win7 a try then reverted back to XP. It came as a bit of a shock when it wouldnt work and I ventured over to the FSUIPC forum to find like you that Pete Dowson was on holiday.
I dont know why it used to work ok and now it will only work if I add those 2 lines to the ini file.
I guess it is using windows networking somehow rather than pure IP; drive mapping between my wideserver and wideclient seem to lag out a little when initially connecting which it never used to do either.
I seem to recall that there was a registry tweak to change the windows networking mode: something about changing to/from broadcast mode to hybrid mode (or vice versa). That may have been the difference, either that or a hotfix from MS has changed something at OS level.
I use my Cisco for DHCP but I have set individual DHCP pools for each device on my network and tied them to the MAC addresses, so it is kind of static but via DHCP.
As a final note, i bet if you had a WINS server you wouldnt have the WideFS problem.
Dave GandolfoSenior Captain, A320
|
|
DVA6497
Captain, B747-400
Joined on January 15 2006
Everett 250 Club
Triple Century Club
DVA Ten-Year Anniversary
"RLTW" Kerkrade, Limburg NL
366 legs, 574.8 hours
14 legs,
20.0 hours online 365 legs,
568.9 hours ACARS
|
Posted onPost created on
June 19 2009 04:03 ET by Ken Tucker
|
Dave,
I ended up adding IPX and the config mods to get everything to work. After this flight, I'll remove the IPX to see if that was the trick or just the ServerIPAddr entry. I hate having to RTFM...
Cheers!!
Ken TuckerCaptain, B747-400
|
|
AFV153
Senior Captain, A320
Joined on January 12 2009
Double Century Club
"Brace yourselves this might be bumpy" Sandwell GB
207 legs, 362.1 hours
207 legs,
362.1 hours ACARS
|
Posted onPost created on
June 19 2009 04:31 ET by Dave Gandolfo
|
I had better results when using the servername rather than ip address. I know itshould be the other way around, but on my network they were my findings.
I suppost the main thing is "as long as it works"
There is a distict difference between reading the manual and scanning it for information.
Dave GandolfoSenior Captain, A320
|
|
DVA6497
Captain, B747-400
Joined on January 15 2006
Everett 250 Club
Triple Century Club
DVA Ten-Year Anniversary
"RLTW" Kerkrade, Limburg NL
366 legs, 574.8 hours
14 legs,
20.0 hours online 365 legs,
568.9 hours ACARS
|
Posted onPost created on
June 19 2009 08:18 ET by Ken Tucker
|
After getting one good flight in (-145 feet/minute, 1.0300G, 1,518 feet FFTH), I've been gouging around with the guts of this and figured out that ServerIPAddr was the key. Adding the IPX protocol didn't work nor did adding ServerNode to the .ini file. Like you said, Dave, as long as it works. I'm intrigued as to why it failed and how it was working before. Hmmm...
Cheers!!
Ken TuckerCaptain, B747-400
|
|
AFV153
Senior Captain, A320
Joined on January 12 2009
Double Century Club
"Brace yourselves this might be bumpy" Sandwell GB
207 legs, 362.1 hours
207 legs,
362.1 hours ACARS
|
Posted onPost created on
June 19 2009 13:31 ET by Dave Gandolfo
|
Nice landing....
I don't think there is a servernode parameter, I used servername rather than serveripaddr as it (when coupled with the lmhost file) gave instant connection to the widefs server.
Anyway, it's working now so dont mess with it anymore...remember the addorage "if it 'aint broke, don't fix it!"
Dave GandolfoSenior Captain, A320
|
|
DVA6497
Captain, B747-400
Joined on January 15 2006
Everett 250 Club
Triple Century Club
DVA Ten-Year Anniversary
"RLTW" Kerkrade, Limburg NL
366 legs, 574.8 hours
14 legs,
20.0 hours online 365 legs,
568.9 hours ACARS
|
Posted onPost created on
June 19 2009 15:03 ET by Ken Tucker
|
Roger!
Cheers!!
Ken TuckerCaptain, B747-400
|
|