connection between 2000 & XP

[michael]

hi,

I have installed a windows 2000(sp4) as domain controller; then add one xp
box into this domain. I found something interesting though,
first of all, XP machine logon to domain takes about 3 minutes, and I tried
other 2000 box only takes few seconds;
Secondly, I cannot access any shared folder in 2000 box, even I logon as
domain adminitrator; XP keep telling me that the server is not configured
transsactional; This happens even after I have added domain administrator
into XP's local administrators group;
Thirdly I cannot access anything from 2000 to XP; 2000 keep telling me the
user is not authenticated.

I added microsoft file and printer share in both machines; I can ping each
other through network; I installed Microsoft network clinet in both
computers;
I just totally get lost!! Did I missed anything?

Can somebody help???

I appreciated!

Michael

 

[Richard G. Harper]

What you probably missed is proper DNS configuration. Your AD domain
controller must be running DNS for the domain to function properly. This
DNS server should be set up to resolve all requests for addresses,
forwarding requests for name resolution outside your domain to an outside
DNS server. The client PCs in the domain must be set up to look only at the
AD DNS server for name resolution.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

 

[michael]

Thanks Richard;
Do you mean I can only have one DNS servere setting in my client computer?
What if I need some outside DNS server to resolve name?
My server is in the internal network. I don't think my server can work as
internet DNS server.

What you probably missed is proper DNS configuration. Your AD domain
controller must be running DNS for the domain to function properly. This
DNS server should be set up to resolve all requests for addresses,
forwarding requests for name resolution outside your domain to an outside
DNS server. The client PCs in the domain must be set up to look only at the
AD DNS server for name resolution.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

hi,

I have installed a windows 2000(sp4) as domain controller; then add one xp
box into this domain. I found something interesting though,
first of all, XP machine logon to domain takes about 3 minutes, and I
tried
other 2000 box only takes few seconds;
Secondly, I cannot access any shared folder in 2000 box, even I logon as
domain adminitrator; XP keep telling me that the server is not configured
transsactional; This happens even after I have added domain administrator
into XP's local administrators group;
Thirdly I cannot access anything from 2000 to XP; 2000 keep telling me the
user is not authenticated.

I added microsoft file and printer share in both machines; I can ping each
other through network; I installed Microsoft network clinet in both
computers;
I just totally get lost!! Did I missed anything?

Can somebody help???

I appreciated!

Michael

 

[Richard G. Harper]

Sounds like you need to do some further reading on configuring DNS in an AD
domain. Start here:

http://www.microsoft.com/resources/...00/server/reskit/en-us/cnet/cncf_imp_ZZUI.asp

There are several topics below this heading that discuss how to implement
DNS properly.

And yes, you MUST configure the clients to use only the AD DNS server to
resolve addresses, all outside addresses must be resolved by forwarding the
request from the DNS server to your ISP's DNS server. Details will be found
above.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

Thanks Richard;
Do you mean I can only have one DNS servere setting in my client computer?
What if I need some outside DNS server to resolve name?
My server is in the internal network. I don't think my server can work as
internet DNS server.

What you probably missed is proper DNS configuration. Your AD domain
controller must be running DNS for the domain to function properly. This
DNS server should be set up to resolve all requests for addresses,
forwarding requests for name resolution outside your domain to an outside
DNS server. The client PCs in the domain must be set up to look only at the
AD DNS server for name resolution.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

hi,

I have installed a windows 2000(sp4) as domain controller; then add one xp
box into this domain. I found something interesting though,
first of all, XP machine logon to domain takes about 3 minutes, and I
tried
other 2000 box only takes few seconds;
Secondly, I cannot access any shared folder in 2000 box, even I logon
as
domain adminitrator; XP keep telling me that the server is not configured
transsactional; This happens even after I have added domain administrator
into XP's local administrators group;
Thirdly I cannot access anything from 2000 to XP; 2000 keep telling me the
user is not authenticated.

I added microsoft file and printer share in both machines; I can ping each
other through network; I installed Microsoft network clinet in both
computers;
I just totally get lost!! Did I missed anything?

Can somebody help???

I appreciated!

Michael