I ran into the same problem. I think I solved it by simply removing the server from the domain and then re-joining. I think it has something to do with the whole Public/Private/Domain network location stuff.
Cameron Shaw wrote:
Server 2008 losing IP Configuration
22-Sep-09
I have got a rather strange issue right now which I am hoping someone coul
advise on. Now I did not do the work myself so I do not know exactly wha
changes were made, but I am the one who is fixing the issue
A IP Resveration is and the information is entered into server statically
The problem is if you restart the server, the server will not respond t
ping, rdp etc
This is how the problem was reported to me, when I logged in locally I foun
that ipconfig reported the ip to be 169.254.x.x when I went to the stati
settings I found the information I entered was there except for the defaul
gateway which appeared to remove itself
I re-entered the gateway clicked ok and closed the window. Upon runnin
ipconfig again I got the same 169.254.x.x number but this time the gateway
entered is now displayed. If I change the settings to DHCP and run ipconfi
the correct information is displayed and remote connection begin working.
can return the settings to Static and they still work, but as soon as
restart ther server the settings are lost and the 169.254.x.x number i
assigned
The problem here i
1)Why is it losing it is settings when they are static
2)Why is it trying to contact a dhcp server
3)Why is this failing when restarting the computer
The server config is Window Server 2008 Standard Edition X64 SP2 run on
Virtual Machine hosted on a Server 2008 Enterprise X64 box
Thanks,
Previous Posts In This Thread:
On Tuesday, September 22, 2009 12:27 PM
Cameron Shaw wrote:
Server 2008 losing IP Configuration
I have got a rather strange issue right now which I am hoping someone coul
advise on. Now I did not do the work myself so I do not know exactly wha
changes were made, but I am the one who is fixing the issue
A IP Resveration is and the information is entered into server statically
The problem is if you restart the server, the server will not respond t
ping, rdp etc
This is how the problem was reported to me, when I logged in locally I foun
that ipconfig reported the ip to be 169.254.x.x when I went to the stati
settings I found the information I entered was there except for the defaul
gateway which appeared to remove itself
I re-entered the gateway clicked ok and closed the window. Upon runnin
ipconfig again I got the same 169.254.x.x number but this time the gateway
entered is now displayed. If I change the settings to DHCP and run ipconfi
the correct information is displayed and remote connection begin working.
can return the settings to Static and they still work, but as soon as
restart ther server the settings are lost and the 169.254.x.x number i
assigned
The problem here i
1)Why is it losing it is settings when they are static
2)Why is it trying to contact a dhcp server
3)Why is this failing when restarting the computer
The server config is Window Server 2008 Standard Edition X64 SP2 run on
Virtual Machine hosted on a Server 2008 Enterprise X64 box
Thanks,
On Thursday, October 22, 2009 12:22 PM
Cameron Shaw wrote:
Yep on both, but the issue appears to have stopped no idea why.
Yep on both, but the issue appears to have stopped no idea why.
On Monday, October 26, 2009 9:55 PM
Meinolf Weber [MVP-DS] wrote:
Hello Cameron,Did you make sure the latest NIC drivers are installed from the
Hello Cameron
Did you make sure the latest NIC drivers are installed from the hardwar
vendor on the hosting machine? Also make sure to have the integration service
installed on the guest system, assuming that you talk about Hyper-V
Best regard
Meinolf Webe
Disclaimer: This posting is provided "AS IS" with no warranties, and confer
no rights
** Please do NOT email, only reply to Newsgroup
** HELP us help YOU!!!
http://www.blakjak.demon.co.uk/mul_crss.htm
On Monday, October 26, 2009 9:55 PM
tjcee wrote:
I am having the very same problem and I have done some troubleshootingwith
I am having the very same problem and I have done some troubleshooting
with weird results. On a server I set NIC1 with a static IP address
and it talked fine on the NW until a reboot. My IP was something like
192.168.3.158/24. After the reboot I had the auto address of
169.254.xxx.xxx/24 and of course, no NW connection. Nothing I did at
that point would allow me to set the NIC back to 192.168.3.158/24. If
I went into the properties of the NIC I still see 192.168.2.158/24 as
the static address. If I edited it right there on that screen and
changed it to 192.168.3.157, once I close the properties window, the
NIC would come alive and start using the new .157 address. Another
very odd behavior was, now I am talking on 192.168.3.157 but if I open
the properties window of NIC1, it still said 192.168.3.158 as the
static address. I needed to click on Advanced and there I could see it
added .157 as a second IP on the NIC. If I reboot the server now, it
would revert to trying to use .158 and lose the fact that .157 was
added at all. It would once again, after a reboot, be set back to
169.254.xxx.xxx/24. So.. I can replicate that behavior over and
over....
Another try...instead of changing the static IP from .158 to .157, I
changed the subnet mask on .158 from /24 to /16, the server would
start using the new static IP w/the 255.255.0.0 subnet. I would make
the subnet change right on the properities window for IPV4 on NIC1.
Another curiosity.. after the change of subnet mask and subsequent
closure of all properties windows, the server started using
192.168.3.158/16 but if I open the NIC1 properties window again, it
showed a static setting of 192.168.3.158/24. Now after a reboot. I am
using 192.168.3.158/16 and the NIC properties shows a static setting
of 192.168.3.158/16... So... I figure I would try to change it to
192.168.3.158/24. I change this in properties and it works fine. Now I
am using 192.168.3.158/24 and my NIC properties shows
192.168.3.158/24 ... all is well... Until a reboot... I go back to
169.254.xxx.xxx/16 this time??? The NIC properties shows
192.168.3.158/24 but now my auto address went to 169.254.xxx.xxx and
is using the subnet I set on my other static set up of 255.255.0.0.
It seems something somewhere is holding the NW setting and reverting
them.. but why and where?? does anyone have any ideas.. this is
driving my crazy..
Thanks
TJ
wrote:
vices
ers
On Monday, October 26, 2009 9:55 PM
tjcee wrote:
Update:Also, on a side note, all of this started happening after I used
Update:
Also, on a side note, all of this started happening after I used HP's
Altiris Remote Deployment Pack's deployment server to create an image
of the Win 2008 server. I am not sure if that broke my tcp/ip or not
but this fix from Microsoft, run first thing after re-deploying the
image, seems to have fixed the problem.
Use a manual method to reset TCP/IP
The reset command is available in the IP context of the NetShell
utility.
Follow these steps to use the reset command to reset TCP/IP manually:
To open a command prompt, click Start and then click Run. Copy and
paste (or type) the following command in the Open box and then press
ENTER:
cmd
At the command prompt, copy and paste (or type) the following command
and then press ENTER:
netsh int ip reset c:\resetlog.txt
Note If you do not want to specify a directory path for the log file,
use the following command:
netsh int ip reset resetlog.txt
Reboot the computer.
e
ervices
nfers
Submitted via EggHeadCafe - Software Developer Portal of Choice
Adding WCF Service References
http://www.eggheadcafe.com/tutorials...ce-refere.aspx
Similar Threads
Linear Mode
