|
Question : Windows 2000 native WEP
|
|
My current setup:
A number of computers running W2k SP4, netgear wireless access point, Zyxel G-300 PCI WLAN Adapter. The WLAN is WEP 128 bit protected.
Once I'm logged in and the Zxyel software is started, I cann connect to the network and map network drives. However, when I configure the machine with AdminAutoLogon and execute a script from the startup folder, the drives cannot get mapped. (The WLAN connection is not up at that point). I can get another script that delays until the network connection is up, but I wonder if there is a solution where I can initiate the WLAN/WEP connection before I logon. E.g. WEP support by W2k instead by the tool from zyxel.
I'm not sure if it will work if I disable WEP, however, I need WEP enabled to protect the network.
Thanks for your help.
|
Answer : Windows 2000 native WEP
|
|
<< but I wonder if there is a solution where I can initiate the WLAN/WEP connection before I logon. >>
This is a very common problem. Basically you already have the right strategy, you MUST delay the attempt to connect until ALL the windows event managers and protocols are loaded. There is no way around this, because all networking and login procedures must be loaded before it will work. What if the login was from someone not authorized to access the resources? How can you justify letting an unauthorized person in, for a 20 second delay?
The only way I can think of right now to automate this is, if your own personal computer, set it to automatically login with your user name and password (dangerous on a laptop), then having used task scheduler to setup a task --
AT 1.00 minutes after login, run connect-script
Then you encapsulate that in a .CMD script (like DOS batch) and dump THAT in the startup folder -- that will work when the delay parameters are correct for the boot timing. It is not much more efficient than you sitting there and waiting for everything to load, but it does automate the procedure.
Bottom line, all service FOR the user and user permissions must be loaded to do this, else it violates windows protection mode of all services and features being user login-access dependant.
|
|
|
|