marceloNYC
asked on
a domain controller for the domain cannot be contacted
Dear Experts, I am in our new office trying to make the PCs part of the domain. We are over a VPN trying to make the PCs part of the domain and we are getting "a domain controller for the domain cannot be contacted". The only interesting thing I can tell you is that we are over a L2L tunnel to the domain controller.
I try entering the local DNS from the remote site. I got the same message.
Is there a particular port that I might need to open in the firewall.
If I do a tracert from the actual PC I get this result to the domain controller:
C:\Users\me>tracert 172.16.100.10
Tracing route to is-doamincontroller.is.ad [172.16.100.10]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 172.16.19.2
2 121 ms 36 ms 29 ms 10.255.255.17
3 55 ms 29 ms 118 ms domaincontroller.is.ad [172.16.100.10]
I don't know why it will not work....
I try entering the local DNS from the remote site. I got the same message.
Is there a particular port that I might need to open in the firewall.
If I do a tracert from the actual PC I get this result to the domain controller:
C:\Users\me>tracert 172.16.100.10
Tracing route to is-doamincontroller.is.ad [172.16.100.10]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 172.16.19.2
2 121 ms 36 ms 29 ms 10.255.255.17
3 55 ms 29 ms 118 ms domaincontroller.is.ad [172.16.100.10]
I don't know why it will not work....
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.