![egnyte desktop sync 127.0.0.1 waiting egnyte desktop sync 127.0.0.1 waiting](https://helpdesk.egnyte.com/hc/article_attachments/360057673112/mceclip1.png)
![egnyte desktop sync 127.0.0.1 waiting egnyte desktop sync 127.0.0.1 waiting](https://global-uploads.webflow.com/5f2a524f221895e85103ee82/5fb5a6c59183dca7da8a8010_mainbigsur.jpg)
I always like to dig a bit deeper when I run into a problem, so let’s look briefly at how vApp Options are applied to better understand this mechanism. The OVF vApp settings were injected into the appliance and applied at each reboot, overwriting my settings. Because the administrator didn’t know about my non-existent DNS servers, he used a default setting when he set the properties of the vApp while deploying the OVF. Think, dummy, think (absorb, beer, absorb)! Ah ha! I didn’t deploy the VCSA – it was deployed by the data center administrator to a separate management cluster before I had built an AD or DNS infrastructure on the hosts my VCSA was managing. I’m using a Static IP so DHCP isn’t handing out a DNS server. Either my incorrect DNS is getting set by DHCP or some other mechanism. If the problem is not coming from inside the appliance, it’s got to be coming from somewhere outside the appliance. I needed some help to figure this one out, so I visited my Universal Troubleshooting Accelerator Dispensing Machine, poured a pint of my Rye Porter homebrew and took a step back to think outside the box (or outside the VCSA as it were).
#Egnyte desktop sync 127.0.0.1 waiting update#
I even went so far as to manually update /etc/nf with the correct settings but after a reboot the DNS server settings were lost. I reviewed some logs on the appliance and poked around in /etc/sysconfig/network/config, but nothing jumped out at me as being wrong. Losing my DNS Server settings caused me all sorts of issues – my vCenter Server couldn’t find ESXi hosts by name, AD authentication failed, and general mayhem ensued. In one of my lab environments my vCenter Server Appliance ( VCVA VCSA*) kept reverting its DNS server settings after I changed them in the VCSA web interface ( After changing the Preferred DNS Server and Alternate DNS Server settings to use my Active Directory Domain Controller IPs and then rebooting the appliance, the DNS settings were removed and the Preferred DNS Server setting was reverted to the setting present before I updated it.