R
robert.waters
My XP Pro SP2 laptop travels between several similar wireless networks
during the course of a day (from job to job), and I prefer to hibernate
rather than shut down between them (due to long boot time). I find
that the supposedly DHCP-set DNS server is being actually remembered
from the previous network after emerging from hibernation.
Example:
Network 1 192.168.1.0/24, DNS server is 192.168.1.16 (windows domain
controller). When I get to network 2 192.168.1.0/24, DNS server is
192.168.1.1 (SOHO router); however, 192.168.1.16 is remembered as the
DNS server, and I need to disable and then enable (or use Windows'
repair option) in order to get the settings right (just renewing the
adapter doesn't work).
My question is, is there any scripting method that will allow me to
perform this repair? Netsh only works for Windows 2003 server. I am
open to anything, vbscript, whatever. This is really a pain.
Thank you.
Robert
during the course of a day (from job to job), and I prefer to hibernate
rather than shut down between them (due to long boot time). I find
that the supposedly DHCP-set DNS server is being actually remembered
from the previous network after emerging from hibernation.
Example:
Network 1 192.168.1.0/24, DNS server is 192.168.1.16 (windows domain
controller). When I get to network 2 192.168.1.0/24, DNS server is
192.168.1.1 (SOHO router); however, 192.168.1.16 is remembered as the
DNS server, and I need to disable and then enable (or use Windows'
repair option) in order to get the settings right (just renewing the
adapter doesn't work).
My question is, is there any scripting method that will allow me to
perform this repair? Netsh only works for Windows 2003 server. I am
open to anything, vbscript, whatever. This is really a pain.
Thank you.
Robert