Do you see anything? Indeed, nothing was traced over SSL (port 443). Minimize Wireshark window. The question is then, where is the traffic going? verify that DNS is working successfully on the XM Device Manager server. Let’s Open Command Prompt from the Address field and type (no quotes). “cmd” Press Enter. Type the command: nslookup ac.training.lab Press Enter. The expected result is: Name: ac.training.lab Address: 192.168.10.23 The nslookup results are successful. This confirms that the DNS server has the correct value for XM App Controller. However, this does not confirm any local DNS cache entries from the XM Device Manager. From Command Prompt, type the command: ipconfig /displaydns Press Enter. Do you see anything strange for ac.training.lab? Indeed! this record does not match with the DNS server record returned from NSLOOKUP. Next step is to check the hosts file from Windows.
Do you see anything? Indeed, nothing was traced over SSL (port 443). Minimize Wireshark window. The question is then, where is the traffic going? Let’s verify that DNS is working successfully on the XM Device Manager server. Open Command Prompt from the Address field and type “cmd” (no quotes). Press Enter. Type the command: nslookup ac.training.lab Press Enter. The expected result is: Name: ac.training.lab Address: 192.168.10.23 The nslookup results are successful. This confirms that the DNS server has the correct value for XM App Controller. However, this does not confirm any local DNS cache entries from the XM Device Manager. From Command Prompt, type the command: ipconfig /displaydns Press Enter. Do you see anything strange for ac.training.lab? Indeed! this record does not match with the DNS server record returned from NSLOOKUP. Next step is to check the hosts file from Windows.
Syn2014_616.docx