I have a network of three locations and they are connected via VPN and everything works fine between location 1 & 2. location 3 was just joined to the VPN and it seems to be working. I can RDP into location 3 from either 1 or 2. the problem is that location 3 is not part of the Domain like location 1 & 2 are, and it is at a point where we need to redirect printers to location 3 which I can't do because they are not part of the domain.
Not 100% sure the VPN is correct based on when I try to join a computer at location 3 to the Domain I get an error message about an A/D controller could not be found.
I need to join 5 workstations to the existing Domain.
Exactly at which particular time the following error appear on your screen? Were you asked to enter credential? To put it simply, in my point of view since both locations 1 and 2 have no problems with authentication to the AD, you may need to revise the VPN configuration for location 3.
Although you did not provide information about how your VPN is configured, make sure that DNS and other required protocols are allowed through your VPN connection. In addition take a look at the access rules of your gateway and VPN servers and verify the configuration.
I get the error after entering the domain name to join then clicking ok, it never gets to the point where it asks for credentials.
I was kind of thinking the same thing that there is something not correct with the VPN setup for location 3. I will look at that tomorrow. if you have any other suggestions please let me know.
Based on your description, it seems that the client computers are not able to reach a DC. Please make sure that your client computers are pointing to correct internal DNS servers for DNS resolution.
You need also to make sure that needed ports for AD authentication are opened and not filtered: http://technet.microsoft.com/en-us/library/dd857231.aspx
Same for DNS traffic on port . To make sure that DNS resolution is properly, please use nslookup.
PortQryUI should be helpful for checks.
Please also make sure that the VPN setup is fine as previously suggested. A network sniffer like Wireshark should be helpful to understand what is wrong with the traffic.
This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.Get Active Directory User Last Logon Create an Active Directory test domain similar to the production one Management of test accounts in an Active Directory production domain - Part I Management of test accounts in an Active Directory production domain - Part II Management of test accounts in an Active Directory production domain - Part III Reset Active Directory user password
- Proposed as answer by Alex LvMicrosoft contingent staff, Moderator Monday, June 24, 2013 3:17 AM
Hello Mr. X,
I will be checking all of these points today and will post what I find here.
One thing I see that I did not mention, there is no server in location 3 we only need the workstations
to join the Domain over the VPN. if this make any difference?
it turns out that the computers in location just needed the WINS server address. after putting in the WINS address I would receive the request for credentials from the AD / DC.
the VPN is setup correct and working.
I have not joined any computers yet as we discovered that by doing so will cause another problem with the POS program so we have to wait for advisement from the POS vendor.
is there a way to redirect a printer from location 3, which is a single workgroup but able to access the VPN, when I try to connect to the workgroup from the domain it never finds the printer.
nslookup did help me find the answer.
- Edited by Danny at DCS Monday, June 24, 2013 9:14 PM added