"preparing network connections"

  • Thread starter Thread starter Brandon Goodman
  • Start date Start date
B

Brandon Goodman

Anyone know which service(s) is/are running when Win2000 displays this
status before logon?

My scenario is this: I have a win2000 pro machine that connects to a
win2000 AD domain via WiFi. The WiFi network requires WPA with TKIP.
The network card needs to connect to the network *before* the user is
allowed to login. In order to do this, Srvany was used to create a
service that starts the WiFi driver utility. This solution works to a
certain extent. Windows does not seem to start the srvany-wifi service
until after the "press ctrl-alt-del" logon dialog is available to the
user. If the user does not wait for 30 seconds or so to login, the
WiFi card will not yet be connected. If tried forcing various system
services such as netlogon & Workstation to be dependent on the
srvany-wifi service. But that doesnt seem to be causing the Wifi
Drivers to start any sooner. I thought maybe if I knew what services
were starting during the "preparing network connections" phase of the
bootup, maybe I could set some dependencies there.

Any ideas out there to priortize service startups or even just force a
30 second delay before allowing login?
 
Know about what? I don't have an previous messages,..I only see this one.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
http://www.microsoft.com/isaserver/techinfo/Guidance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
 
my previous message was as follows:

Perparing Network Connections

Anyone know which service(s) is/are running when Win2000 displays this
status before logon?

My scenario is this: I have a win2000 pro machine that connects to a
win2000 AD domain via WiFi. The WiFi network requires WPA with TKIP.
The network card needs to connect to the network *before* the user is
allowed to login. In order to do this, Srvany was used to create a
service that starts the WiFi driver utility. This solution works to a
certain extent. Windows does not seem to start the srvany-wifi service
until after the "press ctrl-alt-del" logon dialog is available to the
user. If the user does not wait for 30 seconds or so to login, the
WiFi card will not yet be connected. If tried forcing various system
services such as netlogon & Workstation to be dependent on the
srvany-wifi service. But that doesnt seem to be causing the Wifi
Drivers to start any sooner. I thought maybe if I knew what services
were starting during the "preparing network connections" phase of the
bootup, maybe I could set some dependencies there.

Any ideas out there to priortize service startups or even just force a
30 second delay before allowing login?
 
I don't think that will work,...I think you will get the exact results you
are getting. In my own experience with WiFi there was two options:

1. Buy a WiFi Nic that functions without the user being logged into the
desktop. I have no idea what brands or models do that,...but hopefully there
are some out there somewhere.

2. If you can not do #1. Then hook the machine up to the network with a
wired Nic first. Join the machine to the Domain if it is not already, then
have each user that will use the machine login to it as least once to create
the cached account. Then when you use the WiFi Nic the user will log into
via the cached account (because it can't see the DC yet), then once the
desktop is up and the WiFi Nic activates it will then see the DC and
everything will be fine. Make sure you disable any Nics that are not being
used so that Windows does not try to use them and end up "hanging" or having
long delay during startup.

Maybe someone else will have other ideas, but that has been how my
experience with them has been.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
http://www.microsoft.com/isaserver/techinfo/Guidance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
 
Back
Top