RE: [ActiveDir] Joining a domain from offsite

[Mark Parris]

I have seen this error message if the WINS 1Ch records are incorrect.   Mark   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Mike Williams Sent: 14 September 2005 19:55 To: ActiveDir@mail.activedir.org Subject: RE: [ActiveDir] Joining a domain from offsite   It will ping by name or IP number. Ping times are about 100 ms.. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Brian Desmond Sent: Wednesday, September 14, 2005 1:23 PM To: ActiveDir@mail.activedir.org Subject: RE: [ActiveDir] Joining a domain from offsite Are WINS and DNS working over the VPN? Try specifying the FQDN or shortname of the domain instead of what you’re specifying now to join it … this certainly smells like nonworking DNS though.   Thanks, Brian Desmond [EMAIL PROTECTED]   c - 312.731.3132     From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Mike Williams Sent: Wednesday, September 14, 2005 2:03 PM To: ActiveDir@mail.activedir.org Subject: [ActiveDir] Joining a domain from offsite   Hi all:   We are setting up a server off-site using a PIX 525 and a PIX 501 to establish the VPN connection. If I join the domain locally and then take the server offsite I can login to the domain without any problems. If I disjoin the server and then try to rejoin the domain from offsite I get errors that no domain controller is available. In the error message it lists the domain controllers.   any ideas?   Thanks   Mike   The domain name (XXXXXXXX) might be a NetBIOS domain name.  If this is the case, verify that the domain name is properly registered with WINS.   If you are certain that the name is not a NetBIOS domain name, then the following information can help you troubleshoot your DNS configuration.   DNS was successfully queried for the service location (SRV) resource record used to locate a domain controller for domain cvl:   The query was for the SRV record for _ldap._tcp.dc._msdcs.cvl   The following domain controllers were identified by the query:   dc-001.corp dc-002.corp   Common causes of this error include:   - Host (A) records that map the name of the domain controller to its IP addresses are missing or contain incorrect addresses.   - Domain controllers registered in DNS are not connected to the network or are not running.   For information about correcting this problem, click Help.