Back Ground info- XP Pro w/ DHCP network w/ Domain. File and Print sharing -
on. Simple file sharing - off.
I can setup a shared folder, but can not share it with a domain user. I
click on the Permission tab, click on ADD button, click on the Location
button, but only the local machine is there. The Domain does not show so I
can not change to the Domain to add domain users to this share. This also
happens in Security tab too.
The Network is working fine, I can see the other computers and
servers(Domain/Logon server is W2K). I can get email, can get on the
internet. as well as printer to a network printer.
Where do I go now?

"Aron" <(E-Mail Removed)> wrote in message
news:2F6D64A3-E7F5-4F8D-B4FD-(E-Mail Removed)...
> Back Ground info- XP Pro w/ DHCP network w/ Domain. File and Print
> sharing -
> on. Simple file sharing - off.
> I can setup a shared folder, but can not share it with a domain user. I
> click on the Permission tab, click on ADD button, click on the Location
> button, but only the local machine is there. The Domain does not show so I
> can not change to the Domain to add domain users to this share. This also
> happens in Security tab too.
> The Network is working fine, I can see the other computers and
> servers(Domain/Logon server is W2K). I can get email, can get on the
> internet. as well as printer to a network printer.
> Where do I go now?


If the domain is missing from there, this indicates a
problem with the machine's domain membership.

Usually, it's a DNS problem.
Is logging on to a doman user account slow, too?

Here's my usual lecture on DNS configuration.
You must make sure this is set up correctly before going any further:

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...b;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:

HOWTO: Remove the Root Zone (Dot Zone)
http://support.microsoft.com/default.aspx?kbid=298148

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...b;en-us;237675
HOW TO: Configure DNS for Internet Access in Windows 2000
http://support.microsoft.com/default...b;en-us;300202


--
Best Regards,
Ron Lowe
MS-MVP Windows Networking