No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


FusionAccess-logging failed due to DNS configuration in VM's is wrong

Publication Date:  2017-08-10 Views:  178 Downloads:  0

Issue Description

The user login VM failed because  the DNS configuration in the VM is changed.

Alarm Information

no alarm existing in the FusionAccess portal.

Handling Process

1-the VM registered normal

2-login the VM,and try to ping  the domain name,but it failed.

3-Using the command "ipconfig /all" and find that the DNS configuration is not correct

Root Cause

User changed the DNS configuration on the VM because he need to access the internet 


1-First we need to check the DNS configuration on this VM ,we need to be sure that the customer is putting the same IP of the DNS server.

2- Usually Vms  get the DNS configuration automatically  from the DHCP server so we need to mark on the obtain DNS address automatically

3-Login the DNS server and configure Forwarder DNS configuration to let the VM's access the internet like google DNS :