Static IP changes to dynamic automatically

  • Thread starter Thread starter S N
  • Start date Start date
S

S N

I have a Windows 2000 server machine running IIS and hosting various
websites on my intranet.
All PCs in my network are running on DHCP except this server machine which
has been allotted a static IP. The DNS server is also on this network.
However, recently this server is behaving erratically. Its static IP
automatically changes to automatic IP using DHCP- as a result of which the
server becomes inaccessible because of unknown IP address.

Kindly advise on how to ensure that the assigned IP address remains on the
machine and does not change to automatic IP using DHCP.
 
Hi,

Normally, if you choose a static IP address, it should remain this
way.
Do you have an antivirus installed?

Giorgos
 
S N said:
I have a Windows 2000 server machine running IIS and hosting various
websites on my intranet.
All PCs in my network are running on DHCP except this server machine
which has been allotted a static IP. The DNS server is also on this
network. However, recently this server is behaving erratically. Its
static IP automatically changes to automatic IP using DHCP- as a
result of which the server becomes inaccessible because of unknown IP
address.
Kindly advise on how to ensure that the assigned IP address remains
on the machine and does not change to automatic IP using DHCP.
Click to expand...

Something is corrupt in the registry.

Uninstall the NIC but don't reboot
Go through HKLM\system\currentcontrolset\control\network
Find and delete all references to this NIC
Reboot
Let it redetect/reinstall the NIC

You should be fine from then on. This has happened to me a few times over
the years and I never figured out why.
 
"Lanwench [MVP - Exchange]"
Something is corrupt in the registry.

Uninstall the NIC but don't reboot
Go through HKLM\system\currentcontrolset\control\network
Find and delete all references to this NIC
Reboot
Let it redetect/reinstall the NIC

You should be fine from then on. This has happened to me a few times over
the years and I never figured out why.
Click to expand...


Just to add and clarify, I found a post in the following link, that the
poster got Microsoft PSS to assist in a similar issue. The reg entry you
quoted is correct, but there is one more spot under 'network.' which is
'config.' Not sure if that makes a difference or not, but

http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/2003_Server/Q_23453074.html

"[...] We finally got Microsoft to help and they tracked down the problem.
They found a corrupted registry entry in our TCP-IP configuration that
doesn't allow the GUI to successfully change the TCP-IP settings.
The reg entry is removed, and the computer restarted.
TCP-IP service finds the reg entry missing, and rebuilds it.
Voila - The GUI displays properly and will set/reset the TCP-IP setting
properly.
Unfortunately, I can't tell you what was the original cause of the corrupted
reg entry.

Deleting the following reg entry solved our problem:
My computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Network\Config"


--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCITP Windows 2008, MCTS Exchange 2007, MCSE & MCSA 2003 &
2000, MCSA Messaging 2003
Microsoft Certified Trainer

For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.
 
FPN, you can't be sure if and when ControlSet001 would be used again. Always
should be in CurrentControlSet


--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
 
Good point. And I'm not sure why PSS would have indicated using 001. I
should have edited that prior to posting. :-)

Thanks!

Ace
FPN, you can't be sure if and when ControlSet001 would be used again.
Always should be in CurrentControlSet


--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect


Ace Fekay said:
Just to add and clarify, I found a post in the following link, that the
poster got Microsoft PSS to assist in a similar issue. The reg entry you
quoted is correct, but there is one more spot under 'network.' which is
'config.' Not sure if that makes a difference or not, but

http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/2003_Server/Q_23453074.html

"[...] We finally got Microsoft to help and they tracked down the
problem.
They found a corrupted registry entry in our TCP-IP configuration that
doesn't allow the GUI to successfully change the TCP-IP settings.
The reg entry is removed, and the computer restarted.
TCP-IP service finds the reg entry missing, and rebuilds it.
Voila - The GUI displays properly and will set/reset the TCP-IP setting
properly.
Unfortunately, I can't tell you what was the original cause of the
corrupted reg entry.

Deleting the following reg entry solved our problem:
My
computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Network\Config"


--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit
among responding engineers, and to help others benefit from your
resolution.

Ace Fekay, MCT, MCITP Windows 2008, MCTS Exchange 2007, MCSE & MCSA 2003
& 2000, MCSA Messaging 2003
Microsoft Certified Trainer

For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.
Click to expand...
Click to expand...
 
This is the problem faced by me.

Ace Fekay said:
"Lanwench [MVP - Exchange]"
Something is corrupt in the registry.

Uninstall the NIC but don't reboot
Go through HKLM\system\currentcontrolset\control\network
Find and delete all references to this NIC
Reboot
Let it redetect/reinstall the NIC

You should be fine from then on. This has happened to me a few times over
the years and I never figured out why.
Click to expand...


Just to add and clarify, I found a post in the following link, that the
poster got Microsoft PSS to assist in a similar issue. The reg entry you
quoted is correct, but there is one more spot under 'network.' which is
'config.' Not sure if that makes a difference or not, but

http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/2003_Server/Q_23453074.html

"[...] We finally got Microsoft to help and they tracked down the problem.
They found a corrupted registry entry in our TCP-IP configuration that
doesn't allow the GUI to successfully change the TCP-IP settings.
The reg entry is removed, and the computer restarted.
TCP-IP service finds the reg entry missing, and rebuilds it.
Voila - The GUI displays properly and will set/reset the TCP-IP setting
properly.
Unfortunately, I can't tell you what was the original cause of the
corrupted reg entry.

Deleting the following reg entry solved our problem:
My
computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Network\Config"


--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit
among responding engineers, and to help others benefit from your
resolution.

Ace Fekay, MCT, MCITP Windows 2008, MCTS Exchange 2007, MCSE & MCSA 2003 &
2000, MCSA Messaging 2003
Microsoft Certified Trainer

For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.
Click to expand...
 
Back
Top