connecting to w2k domain

Hi,

I have been having serious issues with wireless and connecting my notebooks
to my W2K domain. The login scripts do not run, among other things.

I have figured this out, I think. I realise that the client application for
scanning for wireless routers is a client app, rather than a service, and
therefore doesn't load and attempt connection until I login and bring up the
desktop. This means I have to then logout and login again to get the scripts
to run. This is on all the notebooks I have used, except the IBM notebooks,
which are clever enough to search for wireless networks without having to
bring the desktop up. Some notebooks, such as the Acers are client
application based and require you bring up the desktop first to allow the
client application to scan for wireless routers and bind the connections to
the TCP/IP stack.

Does this make sense and is there any answer to getting logon scripts to run
first time?

Thanks,

This question has come up quite a few times. To my knowledge, no one has
found a solution for it. Your analysis is exactly right as to the cause.
--

"Paul" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Hi,
>
> I have been having serious issues with wireless and connecting my
> notebooks
> to my W2K domain. The login scripts do not run, among other things.
>
> I have figured this out, I think. I realise that the client application
> for
> scanning for wireless routers is a client app, rather than a service, and
> therefore doesn't load and attempt connection until I login and bring up
> the
> desktop. This means I have to then logout and login again to get the
> scripts
> to run. This is on all the notebooks I have used, except the IBM
> notebooks,
> which are clever enough to search for wireless networks without having to
> bring the desktop up. Some notebooks, such as the Acers are client
> application based and require you bring up the desktop first to allow the
> client application to scan for wireless routers and bind the connections
> to
> the TCP/IP stack.
>
> Does this make sense and is there any answer to getting logon scripts to
> run
> first time?
>
> Thanks,
>
>
>

Thanks GTS for the verfication. I have been trying other methods. Tried a
DLINK AirPlus PCMCIA wireless card and the drivers load up at boot time, so
that seems to work. My guess is that if the built-in wireless comes with its
own client based configuration and connection, then disable to internal
wireless adapter and use a DLINK AirPlus PCMCIA wireless card. A bit
asinine, but it works!



"GTS" <x> wrote in message news:(E-Mail Removed)...
> This question has come up quite a few times. To my knowledge, no one has
> found a solution for it. Your analysis is exactly right as to the cause.
> --
>
> "Paul" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
> > Hi,
> >
> > I have been having serious issues with wireless and connecting my
> > notebooks
> > to my W2K domain. The login scripts do not run, among other things.
> >
> > I have figured this out, I think. I realise that the client application
> > for
> > scanning for wireless routers is a client app, rather than a service,
and
> > therefore doesn't load and attempt connection until I login and bring up
> > the
> > desktop. This means I have to then logout and login again to get the
> > scripts
> > to run. This is on all the notebooks I have used, except the IBM
> > notebooks,
> > which are clever enough to search for wireless networks without having
to
> > bring the desktop up. Some notebooks, such as the Acers are client
> > application based and require you bring up the desktop first to allow
the
> > client application to scan for wireless routers and bind the connections
> > to
> > the TCP/IP stack.
> >
> > Does this make sense and is there any answer to getting logon scripts to
> > run
> > first time?
> >
> > Thanks,
> >
> >
> >
>
>