Xenserver PV network card getting 169 IP
-
Firewall is off I believe (but I will check) and this is the DC for the domain, and it was working just fine until I had to hard reset it after a failed attempt to reboot it (this all started due to the need to reboot it, it locked up at "Shutting down Computer").
-
This is the DC, is it also dhcp and dns?
-
DNS yes, DHCP no.
-
@jrc said in Xenserver PV network card getting 169 IP:
DNS yes, DHCP no.
Where is your dhcp server, what does it have for a ip record, can it see this system?
-
Does the correct ip address show for the vm properties in Xencenter? this can be an indicator of problems. if it shows unknown.
To remove the now non existant realtek nic you need to enable device manager to see disabled devices. You can then remove it.
http://www.activeservers.com/Remove-Non-Existing-Network-Adapters.aspx -
If this is the only dc in your network you may need to restart your dhcp server.
-
The DHCP is on the router they have (a Netgear something or the other, business class though). The server's IP is well outside of the range it is authed to give (192.168.0.100-199).
-
Xen shows the 169 IP. And I did follow those instructions, removing a few old ghost network cards and rebooted again, no change after this.
-
I've had dhcp servers start up before domain controller and had similar behavior. Restarting dhcp corrected the issue after a reboot and then an IPconfig flush and renew
-
Sounds good, expect this server was set to have a static IP that was well outside of the DHCP Range and the DHCP server is also the main router/firewall and gateway to the internet.
There is very little chance that the DHCP server is the culprit here. I would just bounce it if I were on site, but I'm not and I do not want to loose my remote connection.
-
If I change the address to 192.168.0.253 the PV adapter takes it and can connect to the rest of the network and the internet. But as soon as I change it back to .254 it jumps to the 169 IP.
There is some sort of internal IP that it is conflicting with, but I cannot find out what that could be.
-
I ran the windows repair tool, it detected an issue with the nic, set it to DHCP. Not very helpful, however, when I then set it back to static of 192.168.0.254 it worked. I am guessing that the tool cleaned up some registry stuff that it did not tell me about or something.
But it seems ok now. I'll need to watch it to make sure though.
-
Ah, computers.
-
Yeah, people laugh at me when I say that I hate computers. Not sure why, I genuinely do hate the f-ing things...
-
@jrc said in Xenserver PV network card getting 169 IP:
Yeah, people laugh at me when I say that I hate computers. Not sure why, I genuinely do hate the f-ing things...
The thing that I find more of is that people just refuse to believe the advice of "just try rebooting it" ... then when that fixes it, they get pissed and say "boy I wish I went to school for 4 years for that".
-
O, those are my favorite, but I never that the last bit, mine always go:
"Have you tried rebooting it"
"Yes, I think so..."
"When was that"
"Last week sometime.."
"Yeah, go ahead and restart and call me back if the problem persists"The call back rate is about 1 in 10.
-
@jrc said in Xenserver PV network card getting 169 IP:
O, those are my favorite, but I never that the last bit, mine always go:
"Have you tried rebooting it"
"Yes, I think so..."
"When was that"
"Last week sometime.."
"Yeah, go ahead and restart and call me back if the problem persists"The call back rate is about 1 in 10.
It's funny that it's not just computers. Anything that plugs in.
Shoot, I replug in a toaster if it isn't working.
