cannot connect to domain.

[Ng Wai Mun]

I'm running on windows XP pro. When I try to join domain,
it gives me this error message as stated below. I can log
into my computer but I cannot access my mapped drive on
server or connect to network printer.

Thanks

__________________________________________________________
The domain name mypah 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.

The following error occurred when DNS was queried for the
service location (SRV) resource record used to locate a
domain controller for domain mypah:

The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)

The query was for the SRV record for
_ldap._tcp.dc._msdcs.mypah

Common causes of this error include the following:

- The DNS SRV record is not registered in DNS.

- One or more of the following zones do not include
delegation to its child zone:

mypah
.. (the root zone)

For information about correcting this problem, click Help.

 

[Ron Lowe]

I'm running on windows XP pro. When I try to join domain,
it gives me this error message as stated below. I can log
into my computer but I cannot access my mapped drive on
server or connect to network printer.

Thanks

__________________________________________________________
The domain name mypah 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.

The following error occurred when DNS was queried for the
service location (SRV) resource record used to locate a
domain controller for domain mypah:

The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)

The query was for the SRV record for
_ldap._tcp.dc._msdcs.mypah

Common causes of this error include the following:

- The DNS SRV record is not registered in DNS.

- One or more of the following zones do not include
delegation to its child zone:

mypah
. (the root zone)

For information about correcting this problem, click Help.

This is a name resolution issue.

Now, whay *kind* of name resolution issue depends on the type of domain.

An old NT4 domain uses NetBIOS name resolution.
A win2k domain uses DNS name resolution.

Your single-lable domain name does not make it clear what your domain is.

Taking a leap in the dark that you have a win2k domain, then you have a DNS
issue.
Here's my usual lecture on DNS...

XP differs from previous versions of windows in that it uses
DNS as it's primary name resolution method for finding domain
controllers:

How Domain Controllers Are Located in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;314861

If DNS is misconfigured, XP will spend a lot of time waiting for it to
timeout before it tries using legacy NT4 sytle NetBIOS.
( Which may or may not work. )

1) Ensure that the XP clients are all configured to point to the local
DNS server which hosts the AD domain. That will probably be the
win2k server itself.
They should NOT be pointing an an ISP's DNS server.
An 'ipconfig /all' on the XP box should reveal ONLY the domain's
DNS server.

( you should use the DHCP server to push out the local DNS server
address. )

2) Ensure DNS server on win2k is configured to permit dynamic updates.

3) Ensure the win2k server points to itself as a DNS server.

4) For external ( internet ) name resolution, specify your ISP's DNS server
not on the clients, but in the 'forwarders' tab of the local win2k DNS
server.

On the DNS server, if you cannot access the 'Forwarders' and 'Root Hints'
tabs because they are greyed out, that is because there is a root zone (".")
present on the DNS server. You MUST delete this root zone to permit the
server to forward unresolved queries to yout ISP or the root servers.
Accept any nags etc, and let it delete any corresponding reverse lookuop
zones if it asks.


The following articles may assist you in setting up DNS correctly:

Setting Up the Domain Name System for Active Directory
http://support.microsoft.com/default.aspx?scid=kb;en-us;237675
HOW TO: Configure DNS for Internet Access in Windows 2000
http://support.microsoft.com/default.aspx?scid=kb;en-us;300202