Connecting to new network without rebooting

[Guest]

I'm having a problem connecting to networks without re-booting.

Simply: I work at home on a wireless network, put my computer to sleep,
drive to work, and plug in to the work Ethernet cable. I wake my computer,
and it finds the work network. However, I have no connectivity. Doing a
"route print" shows 169.* (autoconfigure, worthless) routing. I unplug the
Ethernet cable (and maybe even disable and re-enable the Ethernet adapter)
and "route print" is back to very simple (4-entry) routing that looks right
(just local loopback adapter). I re-connect, and I'm back to the same crazy
routing with no real connectivity.

It doesn't matter if I completely disable and turn off my wireless
connectivity -- the problem still exists. It's not due to an attempt to
connect to some local wireless network.

Re-booting the computer completely fixes the problem.

My IT person swears that all is fine on our network and our DHCP server. He
says it's a glitch in Vista networking. Can anyone reproduce this problem?
Can anyone point me to any knowledgebase articles about this? Are there any
workarounds?

I'd prefer not to have to re-boot every time I switch to my work network.

Thanks!

 

[Robert L [MVP - Networking]]

Try to re-set power management or use static IP instead of DHCP. This search result may help,

Vista: Wireless connectivity issuePost Posted: Wed Mar 14, 2007 4:26 am Post subject: Vista: Wireless connectivity issue ... The wireless connection may drop when you use battery power. ...
http://www.chicagotech.net/netforums/viewtopic.php?p=794&sid=420bb1ae71484a0e9f600ea966f27698


Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
I'm having a problem connecting to networks without re-booting.

Simply: I work at home on a wireless network, put my computer to sleep,
drive to work, and plug in to the work Ethernet cable. I wake my computer,
and it finds the work network. However, I have no connectivity. Doing a
"route print" shows 169.* (autoconfigure, worthless) routing. I unplug the
Ethernet cable (and maybe even disable and re-enable the Ethernet adapter)
and "route print" is back to very simple (4-entry) routing that looks right
(just local loopback adapter). I re-connect, and I'm back to the same crazy
routing with no real connectivity.

It doesn't matter if I completely disable and turn off my wireless
connectivity -- the problem still exists. It's not due to an attempt to
connect to some local wireless network.

Re-booting the computer completely fixes the problem.

My IT person swears that all is fine on our network and our DHCP server. He
says it's a glitch in Vista networking. Can anyone reproduce this problem?
Can anyone point me to any knowledgebase articles about this? Are there any
workarounds?

I'd prefer not to have to re-boot every time I switch to my work network.

Thanks!

 

[Guest]

Thanks.

Didn't work for me.

My work network -- the trouble one -- is not wireless. The problem presents
when just plugging in Ethernet.

I've re-set power management and am working at the high-performance power
setting, plugged in.