Can't see all computers on XP home network

I havent read all these posts in full but . . . .

1. I wouldn't use Vista ever - at work when we buy any Pcs or Laptops we insist on a roll-back disk to set up as Windows XP Pro - suggest you get a licensed copy of XP Pro - save data and over-install

2. If you put SP3 on an XP pro computer >> you can't see the other PCs on the same wirless subnet

3. Solution remove XP SP3 >>> install XP SP2 and - it works - you can see printers PCs etc

you are a god - thanks so much for posting this answer.

Thank you for your answer this fixed all my network problems!

The issue is most likey caused by the mode that Netbios is running in. There are 4 node types: peer-peer, broadcast, mixed and hybrid.

Open a command window and type ipconfig/all the hit enter.
About the third line down you will see node type and I would bet it is most like set to peer-peer.

peer-peer does not check local broadcast for resolution, it only checks the cache and then looks for a wins server.

changing it to any of the other 3 modes should fix your problem.

To change it open Regedit and find the navaget to the following:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetBt\Parameters

Look at the DhcpNodeType key.
If you have a Nodetype key change it as well. (the DhcpNodeType key overrides the NodeType)

It is most likely set to 2.

1 = Broadcast (checks cache then local broadcast)
2 = Peer-Peer (checks cache then wins)
4 = Mixed (checks cache then local broadcast then wins)
8 = Hybrid (checks cache then wins then local broadcast )


Double click it and set it to 1 (home or small network no server) 8 if you are on a network with a wins server.

Reboot the machine and you should be good to go.

This is what I have been looking for for about a year.

Thanks

Best answer which helped me out!! You're professional!!!!!

Maxcat - the REGEDIT32 fix WORKS GREAT! I didn't even have to reboot my XP laptop, I put it to sleep when the battery was low and when I woke it up it knew where are the other computers were and the shared folders on them that I had connected to. Still not quite sure why it "forgot" them after a routine Windows update although I could ping them via their IP addresses, etc. but that is one of the mysteries of Windows.

It's Norton. I can't tell you how I did it, but I had to go into my Norton 360 firewall and 'allow' the Vista to see the XP machine. The firewall treats it as a malicious attempt & blocks it, but doesn't tell you that's what it's doing!

The Norton 360 came on my machine. as soon as the trial expired I removed it and installed AVG.

I had this problem and I renamed my workgroup to ThePig (not really just an example) ON ALL the computers 2-XPs and 1-Windows 7.
Then the folders on windows 7 you want to share you right click on them and click (Properties - Sharing - Share) where it says (Add) you click on the (drop down arrow) and select (Everyone) click add and you should be good to go.

yes the firewall is properly cofigured

Hey, just another post to read but someone might pick up something.

I have made a home network with xp as main, vista on wireless laptop and an older machine starting out with 98 and then upgraded to xp. I was able to install the LLTD protocol that each machine needed. I can see each machine from each machine on my network page. I am trying now to network a vista and xp pro sp3 by wired router. Both can access the internet. The vista sort of sees the xp, but cannot connect to it yet even though file sharing is turned on the xp and the vista. I tried to install the LLTD to the xp sp3 machine but it said I 'did not need it'. it did not give an explanation why. The xp machine does not see any kind of network.

any thoughts?

i dont see the network from vista
idont see the win vista from server 2003

SuperDave,

This was it. The McAfee on the Vista machine has been blocking the IP address.

Thanks a bunch.

It's nearly a year since this was posted, but this reply solved my problem!!!! Only by going into the McAfee Internet Logs and allowing my laptop's IP was I FINALLY able to see my XP desktop on my Windows 7 laptop. Permissions, LLTP, Home or Work workgroup made no difference, it was that final layer buried in McAfee that was the stumbling block to home networking. A million thanks!!!!!!!

SuperDave,

This worked like a charm! I couldn't for the life of me figure out why after setting up file sharing on both my desktop and laptop, both of which are Vista, I could only get my desktop to see my laptop but not the reverse.

Thanks a million!

SuperDave,
Your suggestion was spot on. Thanks for helping me solve my issues.

Etexan

Superdave you are indeed SUPER!! I was going crazy trying to figure out why none of the remote computers would print...I followed the steps you outlined and we're back up and running! Thanks!

Go to control panel/admin tools/services/server. Make sure it isn't disabled, if it is set it on automatic and then hit "start" and then you should see that computer on the network. As soon as I did that my problem was solved. I have a boost program that turns it off, so I just start it up again and no problems.
Kelley

It's all bullcrap when it comes to Mic.soft.. I have an exact oposite of the problem described here by a few people. My XP machine sees Vista, but Vista won't see the XP.
Needless to say, THIS USED TO WORK! Then one day, Windows Vista, being such a "smart" and "advanced" OS, simply refused to access the XP machine.
I'm guessing, since I'm switching LAN's quite often for my work, Win Vista got some garbage stuck in it's cache somewhere, and now it's creating problems. I've seen it cache DNS's, gateways, etc, and then using the cached information on different networks.. I mean, what the heck is that!? Who came up with that sh*t?!

One other proof of this is my work LAN, where some people can access other people's computers, but others can't, and there is no rule! XP sees Vista, Linux/UNIX see it, but some Vista machines don't see other Vistas, yet some others do!

If someone knows how to clear this cache, please post it here.. I'm sure that in most cases this is what creates network problems...

Cheers,
S