Long wait for domain to be available

I have a Windows 2000 adv server network with mixed
clients. One client, running Win98-SE, must wait 3 to 5
minutes after the log-on screen appears to successfully
log on to the domain. If he logs on immediately he gets
the "No Domain server" message. I've removed and
reinstalled the NIC (3Com 10/100), removed all protocols
and reinstalled TCP/IP only. This phenomenom occurs
every time his computer is restarted or powered on -- and
is the only client with this problem. Once logged on,
everything runs fine.
Thx in advance for any clues!
Al Neely
Microsoft Certified Partner

I am having the exact same problem, anyone else have a
clue why this is happening.
>-----Original Message-----
>I have a Windows 2000 adv server network with mixed
>clients. One client, running Win98-SE, must wait 3 to 5
>minutes after the log-on screen appears to successfully
>log on to the domain. If he logs on immediately he gets
>the "No Domain server" message. I've removed and
>reinstalled the NIC (3Com 10/100), removed all protocols
>and reinstalled TCP/IP only. This phenomenom occurs
>every time his computer is restarted or powered on --
and
>is the only client with this problem. Once logged on,
>everything runs fine.
>Thx in advance for any clues!
>Al Neely
>Microsoft Certified Partner
>.
>

I went into msconfig and removed suspect items from
startup, but that didn't help. Next week I'm going to
try to find something else starting from the registry
which might cause a delay in binding the TCP/IP
protocol?????????????
Al
>-----Original Message-----
>I am having the exact same problem, anyone else have a
>clue why this is happening.
>>-----Original Message-----
>>I have a Windows 2000 adv server network with mixed
>>clients. One client, running Win98-SE, must wait 3 to
5
>>minutes after the log-on screen appears to successfully
>>log on to the domain. If he logs on immediately he
gets
>>the "No Domain server" message. I've removed and
>>reinstalled the NIC (3Com 10/100), removed all
protocols
>>and reinstalled TCP/IP only. This phenomenom occurs
>>every time his computer is restarted or powered on --
>and
>>is the only client with this problem. Once logged on,
>>everything runs fine.
>>Thx in advance for any clues!
>>Al Neely
>>Microsoft Certified Partner
>>.
>>
>.
>

This issue hasn't gone away! I have tried stopping all
startup - sys.ini, win.ini, startup, added protocols --
anything to cause win98se to load over existing -- no
help! This is just an annoyance, and don't want to
scratch reload. Help will be appreciated.
Al

>-----Original Message-----
>I have a Windows 2000 adv server network with mixed
>clients. One client, running Win98-SE, must wait 3 to 5
>minutes after the log-on screen appears to successfully
>log on to the domain. If he logs on immediately he gets
>the "No Domain server" message. I've removed and
>reinstalled the NIC (3Com 10/100), removed all protocols
>and reinstalled TCP/IP only. This phenomenom occurs
>every time his computer is restarted or powered on --
and
>is the only client with this problem. Once logged on,
>everything runs fine.
>Thx in advance for any clues!
>Al Neely
>Microsoft Certified Partner
>.
>