I deployed a Thin client for a new site on a network 172.x.x.x on the main site, it was added to AD and worked fine.
new building’s network is behind the company’s firewall.
New DC,DNS,DHCP were just created. Few virtual servers with static addresses work fine. The guy who organized the above told me that I can connect to the Thin.
When I ping the Thin that is currently connected on the network 10.x.x.x (DC is on 10.x.x.x. sure) I receive reply 172.20.33.56.
When do nslookup for 172.20.33.56 it resolves the name of the computer that exits on network 172.x.x.x. with right name of computer (not my THIN).
What is the mistery? Something was hit wrong on DNS probably… but what?