Fred Marshall,
I'm sorry you're experiencing trouble. From a previous post by my coworker
Karl, this could well be an issue with your router. Differences in the
networking
stack between XP and Vista have exposed a lot of router bugs which were
hitherto hidden.
Vista uses UPnP much more heavily than XP ever did, and we've found that a
lot of routers have suboptimal UPnP implementations, causing them to crash.
1. Does this happen on both a wired connection to the router AND a wireless
connection?
2. when Vista "loses" connection, does it come back automatically, or do you
have to reboot your router? Do the other xp machines also lose
connectivity?
3. If ONLY the vista machine loses connectivity, then there is an issue with
your vista machine. Make sure your drivers are all up to date. If
wireless, make sure you have the latest drivers for your card. Go to
linksys' website and verifiy that what you've got is the latest.
4. While you're there, make sure you have the latest firmware for your
router. We found a lot of bugs in router firmware during development, and
the vendors posted a lot of firmware updates.
5. Then, try running the router tool at
http://www.microsoft.com/windows/using/tools/igd/default.mspx, and see if it
passes the tests.
If we can narrow the issue down to your router, that is, that when Vista
loses connectivity ALL the machines (xp too) lose connectivity, then there
are some things worth trying:
A possible solution worth trying is to turn of UPnP. This can be done on
the router (you would have to log onto the routers config page, find out
where it has the UPnP on/off switch, and turn it off) or from the machine
itself.
You can also try disabling window scaling.
So, please try these out:
1. Go to the webtool, and when the test is finished, click on the "view
detailed report" link, and copy that data off & save it.
2. turn off UPnP, either on the router or on the vista machine:
from an elevated command prompt,type the following:
a. sc config SSDPSRV start= disabled
b. net stop ssdpsrv <or> reboot the system
3. Try your test again. If it still fails after some perioed of time, turn
off Window Scaling:
From an elevated command prompt, type the following:
a. netsh in tcp set gl auto=di
<no reboot required>
