gavinseabrook
Posts: 316 +1
Hello All
Ive been having this trouble. I have a client whose 2000 server died, and we transfered all their data to a new server. Setup DHCP on server, WINS, and DNS with Active Directory. Now all the clients that are in the same IP range of the main office have NO PROBLEMS connecting to the domain. Yet all the clients connecting over a hardware VPN cant. Here is a small diagram
MAIN OFFICE (192.9.200.- scheme)>Router>Internet>Router>Other office (192.9.203.-) scheme.
Everytime we try to join the domain, we get an error saying it cant be contacted. Yet we can ping the IP of the domain server, and NSLOOKUP sees that the default server is the proper domain (w11243-1.w11243dom.com).
I have tried everything I could think of, but have no luck what so ever. Anyone able to come up with some suggestions?
Ive been having this trouble. I have a client whose 2000 server died, and we transfered all their data to a new server. Setup DHCP on server, WINS, and DNS with Active Directory. Now all the clients that are in the same IP range of the main office have NO PROBLEMS connecting to the domain. Yet all the clients connecting over a hardware VPN cant. Here is a small diagram
MAIN OFFICE (192.9.200.- scheme)>Router>Internet>Router>Other office (192.9.203.-) scheme.
Everytime we try to join the domain, we get an error saying it cant be contacted. Yet we can ping the IP of the domain server, and NSLOOKUP sees that the default server is the proper domain (w11243-1.w11243dom.com).
I have tried everything I could think of, but have no luck what so ever. Anyone able to come up with some suggestions?