HELP: Win 7 64 bit networking issues

[JBaymore]

I am having a networking problem since the upgrade of the main flight sim machine.  I have this lovely brand new i7-960 quad core kick butt machine which is running fs2004 (there are reasons it is not fsx) like a jackrabbit. It is running Win 7 64 bit and fs2004 runs just fine on it. Now I am trying to hook up the pit again.

I have the existing simpit wired up on a 10/100 Mbit LAN using an 8 port switch. It used to work just fine with the old XP main sim machine. The existing network is a combination of a few machines running XP and one still on Win 98 (yeah....98 !). All is hardwired. No network cable issues. Switch is fine.

The other machines can see the internet via the routing thru the network switch connected directly to the DSL modem. I don't run those machines to the net "through" the main machine. They currently work fine connecting to the net.

I am suddenly experiencing problems with SOME stand alone gauges on the networked machines that I NEVER had before. So I am suspecting some sort of network issue is at the root of this.

The whole "homegroup" business in Win 7 as opposed to "workgroup" seems to not be all that "backward compatible"...at least easily for a non-IT type person. Mucking about in this new version is difficult for me.

I can't get the Win 7 machine to add the computers to the "map". I can see the other computers when I click on "network" in Win 7.... but they are placed at the bottom of the screen in the Network center under a line that says it could not add them to the map. (Don't know exactly what that message implies?) I see the main Win 7 machine and the DSL modem and the internet icon at the top of the "map" all hooked together nicely.

I can "reach" two XP machines shared folders and copy files TO them. The Win 98 machine I can see the machine icon in Win 7, but if I try to access the shared folder there .... it does not accept requests.

If I try to see the shared folders back on the Win 7 machine from the XP or Win 98 machines..... I cannot see it from them. It says the Win 7 machine does not accept requests.

I have installed the very latest version of FSUIPC and WideFS (paid versions). I've been using FSUIPC/WideFS for YEARS and have had it working just fine. I am ASSUMING it is working fine now too. WideClient on both the XP machines and the Win 98 machines has the "connected" message in the top info bar.

But here is the kick.

With WideClinet showing connected, ONE stand alone gauge is connected to the sim and is displaying data correctly on an XP machine. Running right next to that gauge is another gauge that is connected....... but shows no data at all. If I turn off WideClient with the non displaying gauge still running.... it then shows the normal "INOP" display that is designed to indicate that it is not receiving data.
Same scenario on the Win 98 machine.

This situation is happening with two separate stand alone gauges from the same supplier (a PFD and an EICAS). (I am expecting the ND will possibly do the same....... haven't had time to test it yet.)

I am guessing this is happening because the network is only partially working correctly. Something is not getting sent...... and that "technicality" is what the second non-displaying gauges are depending upon for data.

Any thoughts / help would be GREATLY appreciated.

best,

.....................john

[NickN]

The problem is homegroup John.. you need to get off the exclusive W7 homegroup system and go back to normal networking, then the XP system should connect fine.

Homegroup is for all systems being W7

http://www.help2go.com/blogs/arraknid/1 ... twork.html

more:
http://www.ciscopress.com/articles/arti ... ?p=1405566


http://windows.microsoft.com/en-US/wind ... of-Windows

[JBaymore]

Hi Nick!

[NickN]

John

I only logged in here because it was you


Let me say something flat out... Microsuck doesnt want you on WindowsXP network or otherwise. I read the thread with Pete and yes it is possible it could be an issue with the gauges and they should look into it, but I do know that MS is playing games at the network level when it comes to connections other than W7, something you wont hear from anyone who is scared shitless of MS and their wrath. I'm older and have more insurance

In this case there can be several reasons for your problem and even if the XP system is not listed IN the map, it should be listed at the bottom as "The following discovered device(s) can not be placed in the map"

The deal is there are several different possible problems from the LLTD Responder not being enabled on the XP system to the right settings in W7 being out of sorts.. it is also possible everything is correct but the gauge people need to get their act together

What I can say is this may be something you should get into direct contact with MS support about on the phone. I know those f'kers are playing games with networking setup and trying to make things as frustrating as possible so people just say 'uckit I will buy another copy of W7" but in this case even though I can point you 4 different directions I think you should call them directly and tell them the situation that the XP system is not showing on the map and you are having problems with certain network software

[JBaymore]

In this case there can be several reasons for your problem and even if the XP system is not listed IN the map, it should be listed at the bottom as "The following discovered device(s) can not be placed in the map"

They other systems DO show down there......but that is not where I would have expected them..... I thought I should have seen them up on the "Map".

Hummmmmmm......... looks like this is going to be "fun".

Thanks for the thought.  Guess maybe I'll take two valium and call Microsoft when I can work up the gumption. 

Crap!

Thanks, Nick.

best,

.....................john

[NickN]

As I said, I can point you to a few different writeups about this, but there does not seem to be a 'specific' fix and not having my network on W7 but instead XPx64 with one W7 machine, I dont deal with this.

I will see if I can come up with anything, but its possible this may be a gauge problem too.. let them look at it and if I come up with something that looks like it may work I will post it. The new networking system in W7 is made for W7 which is why I thought a phone call to MS may help, but dont hold your breath

[NickN]

The #1 reason for the network map problem is the failure of MS in XPsp3 to install the service

===================================

Using the network map
The network map in Network and Sharing Center is a graphical view of the computers and devices on your network, showing how they're connected and including any problem areas. This can be helpful for troubleshooting. Before a computer running Windows XP can be detected and appear on the network map, you might need to install the Link-Layer Topology Discovery (LLTD) protocol on that computer. For more information, go to Network Map Does Not Display Computers Running Windows XP on the Microsoft website.

If the LLTD protocol is installed but computers running Windows XP still don't appear on the network map, firewall settings could be preventing Windows from detecting them. Check the firewall settings and make sure that file and printer sharing is enabled. To learn how to do this, if you're using Windows Firewall, open Help and Support and search for "Enable file and printer sharing." Open the Help topic, and then scroll to the end. If you're using another firewall, check the information that came with your firewall.
==================================


Here is the workaround

http://homecommunity.cisco.com/t5/Wired ... m-p/200830

[JBaymore]

Hi Nick.

I'll give the workaround a look see and let you know what happens.

THANKS!

I'm gonna guess that the Win 98 machine is a hopeless cause even though it shows on the lower part?  The interesting thing is that an older very eatly beta (alpha maybe) version of the one gauge in question DOES run on that Win 98 PC correctly. 

best,

................john

[NickN]

I am reading in a few places that W7 may not show the systems in the damn map no matter what you do but you DO need to make sure the responder service IS installed into XP and it shows in the properties of the network connection, and, you must make sure the responder is enabled on the W7 system under the network properties

As for the 98 system..   well,     I think that one is a MS question  LOL

I would disable both firewalls at first to see what happens too. Take all the firewalls out of the loop temp and check things

and by the way, if yuu are using a 3PD firewall on the XP system, I would get rid of that completely and just use the Windows firewall

[NickN]

one other thing too..   W7 uses 128bit encrpt, some older devices may not work with that.. you could try dropping that to the 40-56bit encryption setting in the CHANGE ADVANCED SHARING section under the HOME/WORK profile

[NickN]

[quote]

one other thing too..

[JBaymore]

[quote]

one other thing too..

[JBaymore]

I would disable both firewalls at first to see what happens too. Take all the firewalls out of the loop temp and check things

and by the way, if yuu are using a 3PD firewall on the XP system, I would get rid of that completely and just use the Windows firewall

Already tried disableing the firewalls a while back..... no joy.

Will double chack that though to make sure that I tried BOTH off at the same time.

No thrid party firewall.

best,

.............john

[JBaymore]

[quote]also John

[JBaymore]

OK...verified that there is NO LLTD installed on at least one XP SP3 machine. (Thanks Microsoft!  )

Will install XP hotfix per instructions.  Might get delayed a bit.... have an errand to run.

best,

....................john