Windows xp takes 7 tries to login to server 2000

I have windows 2000 server with about 30 users. Everyone has xp on their
workstation.
Some users login within a second and some has to try about 6 to 8 times
before they login.

Each fail login tells the user that Domain is not available etc.

I

Did you check the DNS settings for these stations?

Mehbs wrote:
> I have windows 2000 server with about 30 users. Everyone has xp on their
> workstation.
> Some users login within a second and some has to try about 6 to 8 times
> before they login.
>
> Each fail login tells the user that Domain is not available etc.
>
> I
>
>

I removed obtain automaticall ip address and have hard coded ip address and
DNS so there should be no problem. But still have to login about 7 times and
it happens in certain work station and not all of them.


"Theo Verweij" <(E-Mail Removed)> wrote in message
news:4665981e$0$338$(E-Mail Removed)...
> Did you check the DNS settings for these stations?
>
> Mehbs wrote:
>> I have windows 2000 server with about 30 users. Everyone has xp on their
>> workstation.
>> Some users login within a second and some has to try about 6 to 8 times
>> before they login.
>>
>> Each fail login tells the user that Domain is not available etc.
>>
>> I

There are so many ways to narrow this down.....mostly networking.

Your "hard coded" DNS has the Domain Controller as the "Primary" correct?

Once the troubled workstations do log on, can you see domain workstations
and servers in your "Network Places?" Can you browse shares ?

Can you PING or do an NSLOOKUP for the server via NetBIOS name and get a
response that is correct? If not, flush the cache and try again. Type
IPCONFIG /flushdns and hit enter

What is in the event log of the XP workstations? There must be errors
reported?

Turn off or disable any firewall temporarily, reboot and attempt logon.

Do you have more than one Domain Controller? Type SET L and hit enter on the
problem machines at a command prompt to see who they are using as a logon
server. Make sure that machine is available and ping or nslookup resolves the
name correctly.

Look on the server for event log errors about Active Directory
failures/issues of any kind. Depending on how you have DNS set up, your AD
setup may be throwing errors like crazy if it's not registered in DNS
correctly. One solution would be to add support tools from the Server 2000
CD and run NETDIAG /fix on the domain controller to see if it passes all the
tests correctly.

I'd go to the event logs first, then test networking on both ends including
NS lookups, dig through the network setup to look for non-standard settings,
make sure your AD/DNS server setup is correct with NETDIAG, then remove any
offending firewall/security software if there is...then possibly remove them
from the domain, reboot twice, delete the computer account in AD and then
re-join the machine to see if that resolves it.





"Mehbs" wrote:

> I removed obtain automaticall ip address and have hard coded ip address and
> DNS so there should be no problem. But still have to login about 7 times and
> it happens in certain work station and not all of them.
>
>
> "Theo Verweij" <(E-Mail Removed)> wrote in message
> news:4665981e$0$338$(E-Mail Removed)...
> > Did you check the DNS settings for these stations?
> >
> > Mehbs wrote:
> >> I have windows 2000 server with about 30 users. Everyone has xp on their
> >> workstation.
> >> Some users login within a second and some has to try about 6 to 8 times
> >> before they login.
> >>
> >> Each fail login tells the user that Domain is not available etc.
> >>
> >> I
>
>
>