As far as the vista machine not being able to find the other xp machines. There is an update for xp called LLTD (linked layer typology discovery) which is what vista uses to see the other machines. May not help locating your printers, but will put the xp machines in their proper places. See
Network Map in Windows Vista does not display computers that are running Windows XP for description and download.
Regarding the limited connectivity. I have had the same problem with a presario dv9000 runing vista ultimate with an N wireless and a linksys 350N router set up to run mixed mode. The problem for me appears to show up when I move the Vista machine to the other end of the house, when it not only crashes the connection to the machine, but brings down the entire wireless network. One of my xp machine complains of an IP address conflict, and the vistas give the local access only and occasionally fail to recognize the wireless router as a known network.
I have a sneaking suspicion that there may be issues with switching between the narrow and wide bands as I move or with the CTS protection mode.
Does any of this ring a bell with your situations?
Quote:
Originally Posted by Unregistered  I have a home network with a desktop running XP hard wired to a wireless router, a laptop running XP and using a pen type wireless connector, and a laptop running Vista with built in wireless connector.
The hard wired desktop shares files and connects to the internet, all as one would expect.
The XP laptop similarly shares files, connectes to the internet and uses the printer attached to the desktop.
The Vista laptop connects to the internet until its been standing idle for a while, and then nothing will persuade it to reconnect. The only way to reconnect to the internet is to reboot.
Sometimes the Vista laptop will see the other computers on the network, and on special once in a blue moon occasionas, lets you use the printer on the desktop, but more often than not seems to think its all alone in the world.
Vista's network diagnostic tool just returns 'unable to diagnose fault'
Don't want to hard wire this too, as it defeats the object of having a laptop, but I see no other option, unless someone comes up with a solution to stop this. |