So, we're wiping clean all PCs at our office and migrating them to a new server cluster and a new domain. Last night I tested on PC and it mostly worked except it refuses to join to the domain.
Now, our domain is named like
EXAMPLE.COM. When I just type
EXAMPLE the PC can't find the domain controller, even though I can ping it find. If I type
EXAMPLE.COM it seems to work. How can I get it to work with just
EXAMPLE? That's how I got all the new servers int he cluster to work (about 20 of them) and I haven't had any issues...
The only difference between the Windows 7 PC(s) and the servers is that the clients will be on a 10.0.3.X network where as the servers are on a 10.0.1.X network.
Oh, the domain controller and all the other servers are Windows Server 2008 R2.
Suggestions will be highly appreciated!
UPDATE per @joeqwerty's request:
The servers network is 10.0.1.X/23. The clients network is 10.0.3.X/24. Both networks are running over their own VPNs on the switches (3x Dell 6224).
The clients are configured to use the DNS of the new domain controller. It also happens to be the one handing out their IPs through DHCP.
The client is complaining that the SRV record for _ldap._tcp.dc._msdcs.EXAMPLE was not found. Looking at the DNS I can see there is an _ldap._tcp.dc._msdcs.EXAMPLE.COM under _msdcs.example.com forward lookup zone, which is probably the one it's finding.
What do I need to do on the DNS to make it find the non .COM version? Or is that even possible? It should be possible, right?