Big news! The community will be moving to a new platform April 21. Read more.
Big news! The community will be moving to a new platform April 21. Read more.
Cadet 2nd Class Cadet 2nd Class
Cadet 2nd Class
1578 views

Wirelss Driver not working until after login

Hello everyone,

I have another weird problem.

We have a number of workstations which use wireless NICs. These NICs are setup to connect to the preferred wireless network on boot - giving the user a "wired experience"

And 9 out of 10 times this works perfectly, however every once in a while, the network card will not connect until after login. This is obviously a problem as firstly the user is unable to login without a connection to the network. Second, there are microsoft login/boot scripts that should run before the user even logs in.

We have tried many solutions to the problem, and have found that the most reliable way of fixing the problem is to uninstall the Novell Client, Reboot, Re-install the Novell Client.

It should be noted that we do have two different wireless networks.
A WPA2 Passphrase network which our wireless workstations use with a long complicated passphrase.
A WPA2 Enterprise network which our laptops use which authenticates through a RADIUS server.

The problem we are having are with the workstations connected to the WPA2 Passphrase network. However a "work around" has been to check the "login using 802.1X" checkbox, this will of course fail after the set timeout, but this action seems to kick the network card forcing it to connect to the wireless network, by that time the 802.1X timeout kicks in and the client is able to authenticate normally. But this is not a fix!

Does anyone have any idea how/why this happens?

Thanks
Bob Brandt
Labels (1)
0 Likes
2 Replies
Absent Member.
Absent Member.

Personally I think this is a wireless network
noise/distortion/congestion problem. I have the experience that you can
never be sure, that the wireless network comes up in a certain amount
of time. And this does happen on PCs without Novell Client, too. So
just sometimes your PC is quicker than the network in booting up.

And there is a group policy setting "Always wait for the network at
computer startup and logon", which may help.
--
W. Prindl


robert w brandt wrote:

>
>Hello everyone,
>
>I have another weird problem.
>
>We have a number of workstations which use wireless NICs. These NICs
>are setup to connect to the preferred wireless network on boot -
>giving the user a "wired experience"
>
>And 9 out of 10 times this works perfectly, however every once in a
>while, the network card will not connect until after login. This is
>obviously a problem as firstly the user is unable to login without a
>connection to the network. Second, there are microsoft login/boot
>scripts that should run before the user even logs in.
>
>We have tried many solutions to the problem, and have found that the
>most reliable way of fixing the problem is to uninstall the Novell
>Client, Reboot, Re-install the Novell Client.
>
>It should be noted that we do have two different wireless networks.
>A WPA2 Passphrase network which our wireless workstations use with a
>long complicated passphrase.
>A WPA2 Enterprise network which our laptops use which authenticates
>through a RADIUS server.
>
>The problem we are having are with the workstations connected to the
>WPA2 Passphrase network. However a "work around" has been to check
>the "login using 802.1X" checkbox, this will of course fail after the
>set timeout, but this action seems to kick the network card forcing
>it to connect to the wireless network, by that time the 802.1X
>timeout kicks in and the client is able to authenticate normally. But
>this is not a fix!
>
>Does anyone have any idea how/why this happens?
>
>Thanks
>Bob Brandt


W. Prindl
0 Likes
Cadet 2nd Class Cadet 2nd Class
Cadet 2nd Class

Thanks, but unfortunately I already ruled that out. I have proven that the network does not come up until after the user logs in. I have had workstations sit idle for hours (i.e. over lunch or even overnight) and still they do not connect. My theory is that the wireless network drivers themselves are running as a user program rather than a deamon (or service), but the right troubleshooting tools and options in windows are few and far between.

I will look into this "Always wait for the network at computer startup and logon" option though, Thanks.
Bob

W_Prindl;2120827 wrote:
Personally I think this is a wireless network
noise/distortion/congestion problem. I have the experience that you can
never be sure, that the wireless network comes up in a certain amount
of time. And this does happen on PCs without Novell Client, too. So
just sometimes your PC is quicker than the network in booting up.

And there is a group policy setting "Always wait for the network at
computer startup and logon", which may help.
--
W. Prindl

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.