login from xp pro to win2000server is slow

[RobB]

I have a good working NT4 server domaincontroller.
I changed a second pc to be a domaincontroller with win2000 server.
I installed active directory and created some domainusers.
If I say to XP pro that hhas to connect to domain2 instead of domain1
(nt4), then it takes ages (10 minutes) for the boot, after I loggin.

What could I have done wrong?

RobB

 

[Chriss3]

(This is the most common possible reason) Make sure the DNS are correct
setup, (this means you should be available to ping the domain name by FQDN
ex: ping company.local from the client and from the server, one of your
Domain Controllers should responds)

--
Regards,

Christoffer Andersson
No email replies please - reply in the newsgroup
If the information was help full, you can let me know at:
http://www.itsystem.se/employers.asp?ID=1

 

[RobB]

(This is the most common possible reason) Make sure the DNS are correct
setup, (this means you should be available to ping the domain name by FQDN
ex: ping company.local from the client and from the server, one of your
Domain Controllers should responds)

Correct, if I ping the servers-name I get a ip-address that it is
pinging, even if I am logged in throught the other domain.

RobB

 

[Chriss3]

You should not only ping the server-name, you should ping the AD FQDN Domain
name.

--
Regards,

Christoffer Andersson
No email replies please - reply in the newsgroup
If the information was help full, you can let me know at:
http://www.itsystem.se/employers.asp?ID=1

 

[RobB]

You should not only ping the server-name, you should ping the AD FQDN Domain
name.

Euh,

How do I do that?
I am new at NT2000 server.
suppose the domainname is: mydomain and the ipadress is 10.0.0.12

I actived the WINS also in the Domain-settings and the loading
shortened to 3 minutes.

I made a rob.bat, for drive settings, like:
net use k: \\domainserver\sharename1

That seems not to function.

If I want to login through explorer on the server, for launching the
rob.bat in the sysvol directory, then it is asking for a userid.
Although my userid has adminrights, I must login with the
administrator uid and pw.

Afterwards, I can only enter the new drives through this
administrator.

Rob

 

[MJC]

he means to ping using the "FQDN (Fully Qualified Domain Name)" or:

server.mydomain.com

Make sure your DNS suffix on your machine matches the DNS suffix of your
domain. Chris is probably right, I had the exact same problem and DNS was
the cause of the problem. Sometimes when DHCP pushes a different DNS suffix
it will cause a problem.....

Active Directory uses DNS as its primary name resolution protocol...it won't
work correctly with out it. Make sure your forward lookup zone
(mydomain.com) and your SRV records were created correctly.

You should not only ping the server-name, you should ping the AD FQDN Domain
name.

Euh,

How do I do that?
I am new at NT2000 server.
suppose the domainname is: mydomain and the ipadress is 10.0.0.12

I actived the WINS also in the Domain-settings and the loading
shortened to 3 minutes.

I made a rob.bat, for drive settings, like:
net use k: \\domainserver\sharename1

That seems not to function.

If I want to login through explorer on the server, for launching the
rob.bat in the sysvol directory, then it is asking for a userid.
Although my userid has adminrights, I must login with the
administrator uid and pw.

Afterwards, I can only enter the new drives through this
administrator.

Rob

 

[Guest]

H

Do you set the DNS ip in XP workstation?

Calvin

 

[Copo]

Forget about WINS, at the moment. What you should focus on is that the DNS
server runs on the Windows2000 domain controller can resolve name for you.
Everything you need for loggin on an Active Directory resolve from the DNS
runs on your DC (in your case which have only 1 W2K DC, these informations
including which domain controller you are going to connect, as well as
kerberos, TGT, etc.). You seems not yet know the relationship between DNS
and AD, but the first thing you do is to configure your client (XP) to use
the IP of your Windows2000 DC as the DNS server and see if this can help.

Also, check if there is any hints from event viewer and post here if you
still get problem on loggin on.

 

[RobB]

Hi

Do you set the DNS ip in XP workstation?

Calvin

HAhahahohoohohohuhuhihihi,

No Calvin. I did not. I laughed because I did not think of it.
But thank you.
I could not ping compnam.domainname either, but I could ping compname.

I had no link in the DNS to the NT4-server, and that did function
pretty well.

Thank you all, as you all lead me to the sollution, one way or the
other.
Logging in is a matter of a few seconds now.

Robb