Xenserver PV network card getting 169 IP



  • Ok, so I had an issue with an SBS 2011 server and ended up bouncing it quite hard as it was locked at 100% and Xen could not shut it down. Hard powered the host in order to get it back and running.

    But now I have a very odd problem, the Xen PV network adapter is set to have a static IP of 192.168.0.254, but when it comes up it is trying to use its "Preferred" ip of 169.whatever.

    According to some google searches this can happen when the there is a duplicate IP on the network, which there is not. I cannot ping in or out from this server.

    So a while back I did some updates on Xen and had to re-install the Xen Tools which did not go so well, once issue was it never installed the PV network stuff, and there was a Realtek nic installed, which I configured, but then realized this was wrong and re-installed the Xen Tools, which worked the second time and everything was happy. So I am wondering if the "conflict" is actually between the Xen nic and the now hidden Realtek nic? If so, how in the hell do I get to that hidden nic to change it's config? Or am I barking up the wrong tree here?

    I have tried rebooting the server again, hoping that maybe a clean re-boot would fix it, to no avail.

    Not sure where to go from here...



  • Does this VM think it's connected to a public network?



  • @DustinB3403

    No it does not.



  • Confirm the firewall is set appropriately. I've had this occur myself and it's always been either the vm thinks it's on a public network, or the firewall is on / miconfigured



  • @DustinB3403

    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?



  • @DustinB3403

    DNS yes, DHCP no.



  • @jrc said in Xenserver PV network card getting 169 IP:

    @DustinB3403

    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.
    0_1491498295312_upload-6b6501d7-ab3f-40c5-a43c-e84ef43fec92

    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.



  • @DustinB3403

    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).



  • @momurda

    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



  • @DustinB3403

    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.



  • @BRRABill

    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:

    @BRRABill

    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".



  • @BRRABill

    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:

    @BRRABill

    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.


Log in to reply
 

Looks like your connection to MangoLassi was lost, please wait while we try to reconnect.