Network connectivity at startup

Windows XP SP2 connecting to a Doamin; Windows 2003 and 2000 domain
controllers. When the workstation is started and user starts to logon as
soon as the logon screen appears, the logon script, group policy and other
domain/network associated functions fail. But if the users lets the machine
run for a few minutes after the logon screen appears and then logs on, then
all is well. It seems like some services (must be network related services)
are not started when the logon screen appears.

Any suggestions as to how to make the logon prompt appear only after all
services are started. Or any other suggestions to resolve this issue will be
greatly appreciated.

Thanks in advance

I think this link should help you out.
http://support.microsoft.com/default...&Product=winxp

"dc" wrote:

> Windows XP SP2 connecting to a Doamin; Windows 2003 and 2000 domain
> controllers. When the workstation is started and user starts to logon as
> soon as the logon screen appears, the logon script, group policy and other
> domain/network associated functions fail. But if the users lets the machine
> run for a few minutes after the logon screen appears and then logs on, then
> all is well. It seems like some services (must be network related services)
> are not started when the logon screen appears.
>
> Any suggestions as to how to make the logon prompt appear only after all
> services are started. Or any other suggestions to resolve this issue will be
> greatly appreciated.
>
> Thanks in advance
>
>
>

yes...thats the article that helped me out.

Thanks


"PJ" <PJ@discussions.microsoft.com> wrote in message
news:0E4DFBE8-CB4E-40F1-9B23-1DFD07BE89DE@microsoft.com...
>I think this link should help you out.
> http://support.microsoft.com/default...&Product=winxp
>
> "dc" wrote:
>
>> Windows XP SP2 connecting to a Doamin; Windows 2003 and 2000 domain
>> controllers. When the workstation is started and user starts to logon as
>> soon as the logon screen appears, the logon script, group policy and
>> other
>> domain/network associated functions fail. But if the users lets the
>> machine
>> run for a few minutes after the logon screen appears and then logs on,
>> then
>> all is well. It seems like some services (must be network related
>> services)
>> are not started when the logon screen appears.
>>
>> Any suggestions as to how to make the logon prompt appear only after all
>> services are started. Or any other suggestions to resolve this issue will
>> be
>> greatly appreciated.
>>
>> Thanks in advance
>>
>>
>>