Tech, Gadgets, Photography, Social Media and Poor Spelling
I really do hope this helps someone. It’s just turned a potential nightmare Monday into a far better one.
you have an AD network on one subnet
and have another department on another subnet
there is communications between the two subnets, you can ping both ways, and from machines NOT on your AD network, you can connect over the router between the two machines no issues.
I’ve setup a DNS server on the 192.168.2.0 network which machines on that subnet use for domain requests.
However, when you try and connect between a machine on the second subnet, and a server on the first, you are asked to authenticate to the AD, which your PC is already a memeber of..
the answer is to add to the forward hosts file the following
_ldap._tcp.YOURDOMAIN.COM. SRV 0 0 389 YOURADSERVER.YOURDOMAIN.COM.
_kerberos._tcp.YOURDOMAIN.COM. SRV 0 0 88 YOURADSERVER.YOURDOMAIN.COM.
_ldap._tcp.dc._msdcs.YOURDOMAIN.COM. SRV 0 0 389 YOURADSERVER.YOURDOMAIN.COM.
_kerberos._tcp.dc._msdcs.YOURDOMAIN.COM. SRV 0 0 88 YOURADSERVER.YOURDOMAIN.COM.
(Obviously YOURDOMAIN.COM and YOURADSERVER.YOURDOMAIN.COM you need to change to reflect to your AD network)