unusual (weird) network behavior

  • Thread starter Thread starter dave
  • Start date Start date
D

dave

I have a PC that was once on a network. It had a fixed IP address.
The PC has a new home and a new network. The network has now been
configured for DHCP. I should also mention there was an issues
getting rid of Norton AV and installing Symanted Corporate. The
machine would not boot. Selecting "last good configuration" as a boot
option got it up and running. Once up and running the network was
reconfigured for DHCP. Once that was done it got an IP address and
was able to browse the network.

But, subsequently when the PC is started it always gives itself the
old, fixed IP address. A temporary workaround is to open a cmd
prompt and do an ipconfig /release followed by and ipconfig /renew.
Once that is done all is well.....until the next cold start. How can
I make it forget the old address and use dhcp at boot up?

Thanks.
 
I have a PC that was once on a network. It had a fixed IP address.
The PC has a new home and a new network. The network has now been
configured for DHCP. I should also mention there was an issues
getting rid of Norton AV and installing Symanted Corporate. The
machine would not boot. Selecting "last good configuration" as a boot
option got it up and running. Once up and running the network was
reconfigured for DHCP. Once that was done it got an IP address and
was able to browse the network.

But, subsequently when the PC is started it always gives itself the
old, fixed IP address. A temporary workaround is to open a cmd
prompt and do an ipconfig /release followed by and ipconfig /renew.
Once that is done all is well.....until the next cold start. How can
I make it forget the old address and use dhcp at boot up?

Thanks.

Will this a bad TCP/IP stack, try to uninstall the Internet Protocol
(TCP/IP) and Reinstall and configure this machine to get or assigned Auto IP
Address.

Try this:
Open the Run command and type in:
ipconfig /flushdns click [OK]
ipconfig /renew click [OK]
netsh winsock reset click [OK]

Run disk Clean up on this machine and Reboot and see if after restarting
again will hold its IP Address.
HTH.
nass
 
I wonder if a startup script (set by the network administrator earlier) is changing the IP addressing to Static from DHCP at every startup.

--
Regards,

Ramesh Srinivasan, Microsoft MVP [Windows Shell/User]
Windows® Troubleshooting http://www.winhelponline.com


I have a PC that was once on a network. It had a fixed IP address.
The PC has a new home and a new network. The network has now been
configured for DHCP. I should also mention there was an issues
getting rid of Norton AV and installing Symanted Corporate. The
machine would not boot. Selecting "last good configuration" as a boot
option got it up and running. Once up and running the network was
reconfigured for DHCP. Once that was done it got an IP address and
was able to browse the network.

But, subsequently when the PC is started it always gives itself the
old, fixed IP address. A temporary workaround is to open a cmd
prompt and do an ipconfig /release followed by and ipconfig /renew.
Once that is done all is well.....until the next cold start. How can
I make it forget the old address and use dhcp at boot up?

Thanks.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top