Slow logon to domain...

[Van556]

Hello all,

Some of our workstations seems to have a long pause during
logon session. The pause seems to be after the
authentication process and during the execution of the
logon script file (eventhought I have verified that all
the script files are ok). In the Active Directory Users
And Computer mmc, under User property and in the Profiles
tab, I did not define the path for the Logon script file,
just the batch file name and extension. I was wonder if
this is where the problem locate. Do I have to define a
path to where the logon script files are located? I have
set up many new users and never have to point to where the
script files is and everyone was able to logon and execute
the correct batch file with no problem (it is just
annoyingly slow for some of them).

Since I am not at all firmiliar with Windows 2000 AD
works, I thought it would be better off seeking advise
from this board before I make any changes. Here is my
current network:

(2) Ms Windows 2000 server configure as domain controller
(1) Ms Exchange 2000 also configure as domain controller
(27) Ms Windows 2000 Professional

Thanks in advance to all response.

Sincerely,
Van

 

[Marina Roos]

Check ipconfig/all on the clients. Does everything point to the server-IP?
How many nics in the server?

 

[Marc Reynolds [MSFT]]

Make sure the XP client are configured to point to the DNS server that hosts
the domain SRV records and not to an ISP DNS server.

--

Thanks,
Marc Reynolds
Microsoft Technical Support

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Alice Spencer]

Why does the amount of Nics make a difference ?

Check ipconfig/all on the clients. Does everything point to the server-IP?
How many nics in the server?

 

[Marina Roos [SBS-MVP]]

If you have 2 nics, the bindingorder might be wrong. In network connections,
advanced, advanced, you should make sure the internal nic is on top.
Furthermore, the internal nic should have a blank gateway.
The external nic should be in a different IP-range than the internal nic.
DNS on both nics should *only* point to the server-IP.