Jump to content
Welcome to our new Citrix community!
  • 0

VMs from machine catalog lose IP address


Tomas Ferianc

Question

Hello

 

I've got standard XenDesktop Citrix structure, AD VM, Citrix VM and machine catalog with VM.

Time to time, IP address of those VMs which are in catalog is lost, AD and Citrix VMs are always fine.

In that case, XenCenter shows something like 169.254.196.126 instead of 192.168.x.x.

Therefore, clients connected via Virtual Apps & Desktops lose connection too and nothing works.

 

Any ideas why this is happening? Thank you.

Link to comment

4 answers to this question

Recommended Posts

  • 0

Hello, thanks, here are 2 errors which I've found in event log just when IP loss happened.

I've replaced addresses and names by general description... <text>

-----------------------------------------------------------------------------------------------------------
The system failed to update and remove host (A or AAAA) resource records (RRs) for network adapter
with settings:

           Adapter Name : {624766B4-2808-4F0C-A536-FC7A74F311F2}
           Host Name : <our host name>
           Primary Domain Suffix : <our domain>
           DNS server list :
                 <ip address of our AD server>
           Sent update to server : <?>
           IP Address(es) :
             <ip address of failing VM>

         The system could not remove these host (A or AAAA) RRs because the update request timed out while awaiting a response from the DNS server. This is probably because the DNS server authoritative for the zone where these RRs need to be updated is either not currently running or reachable on the network.

---------------------------------------------------------
NtpClient was unable to set a domain peer to use as a time source because of DNS resolution error on '<host name of AD server>'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9).

Link to comment
  • 0

The error you're listing here is not likely related to the problem (but may be a symptom since you're not acquiring an IP address, you're not able to talk to AD/DNS/NTP.).  You need to focus on the DHCP failure rather than DNS.  Check logs on the DHCP server and client to see if there are errors logged that will give you an indication of the problem.  Run a packet trace to observe what is happening with the DHCP request/offer/ACK/ etc.  Are you certain  you're not simply out of addresses?

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...