Robert_W_Brandt Absent Member.
Absent Member.

Re: Network Card becoming disabled

Rodion;2122000 wrote:
I have got problem like you when I was testing 802.1x authentication.
I solved it by uninstalling and reinstalling Novell Client 4.91 SP5 IR1
with last patches..


Thanks, but unfortunately I have found that the Novell Client, either the version installed or un/re-installing it, doesn't work 100% of the time.

Bob
0 Likes
kpmonson Absent Member.
Absent Member.

Re: Network Card becoming disabled

Well a small fruitless update. This last round of MS updates brought us 42 new security patches not including updates to Win Media Player, an odd hotfix, etc. I made 3 VM clones and uninstalled 14 different updates from each. Thus far they have all been working... I'm still doing some testing with them but so far it feels like another dead end. Are you imaging your worktations? If so did you happen to build it in VMware? I'm in the process of getting these images put on an actual workstation as there has been some disparity between testing between the two environments, but I'm just about ready to forget about the updates as I don't have much more time to spend to sort this out, particularly if I have to re-image (AGAIN!!) 400+ machines before school starts, and hope the other 800 don't decide to defecate the bed...
0 Likes
Highlighted
kpmonson Absent Member.
Absent Member.

Re: Network Card becoming disabled

I uninstalled the VMware NIC driver in the image before sysprepping the image. Originally I had left it in there because we don't use Microsoft Networking and had uninstalled it prior to sysprep thinking it was the only way to do so short of doing it manually each and every time. This seems to have stabilized the image for us, although I still don't have anything solid to suggest why it was a problem to begin with. If this works then I'll abandon trying to root out the cause (lack of time, otherwise I'd love to know) and begin reimaging, again...
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Network Card becoming disabled

robert w brandt <robert_w_brandt@no-mx.forums.novell.com> wrote:

> What is happening is that the Network Card becomes disabled by itself.


There is a known issue with the Novell Client's NOVEAP.DLL on both the
Novell Client for Windows 7 and the Novell Client for Windows XP/2003
in which the wired network interface can potentially be "abandoned" in
a disabled state during shutdown of the machine.

Currently this issue can occur even if 802.1x authentication is only
being performed on wireless network interfaces, and even if the Wired
AutoConfig (DOT3) service is disabled.

This issue is currently open with Novell as Bug 701413. It will not
be addressed in the upcoming Novell Client 2 SP1 (IR8), but as soon as
there is a post-IR8 release for Novell Client for Windows 7 and/or a
post-Novell Client 4.91 SP5 (IR1) release of NOVEAP.DLL citing Bug
701413 as fixed, this issue should be addressed.

Unfortunately there isn't any workaround other than disabling NOVEAP
at the moment, because there aren't any optional conditions which can
avoid the interface disable-reenable cycle that gets interrupted on
shutdown and potentially leaves the interface abandoned in the
disabled state.

If anyone is seeing this issue and DOESN'T have NOVEAP enabled
(meaning a visual inspection of the
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\RasMan\PPP\EAP\26]
confirms definitively that Microsoft's RASCHAP.DLL is still registered
as the MSCHAPv2 provider instead of Novell's NOVEAP.DLL), then that
would not fit the parameters of the currently known issue.

Alan Adams
Novell Client CPR Group
alan.adams@novell.com

Novell
Making IT Work As One
www.novell.com

Upgrade to OES Community
http://www.novell.com/communities/coolsolutions/upgradetooes/
0 Likes
kpmonson Absent Member.
Absent Member.

Re: Network Card becoming disabled

Thank you thank you thank you! Unregistering the noveap.dll seems to be working for us. This will save me loads of time.


Alan Adams;2124646 wrote:
robert w brandt <robert_w_brandt@no-mx.forums.novell.com> wrote:

> What is happening is that the Network Card becomes disabled by itself.


There is a known issue with the Novell Client's NOVEAP.DLL on both the
Novell Client for Windows 7 and the Novell Client for Windows XP/2003
in which the wired network interface can potentially be "abandoned" in
a disabled state during shutdown of the machine.

Currently this issue can occur even if 802.1x authentication is only
being performed on wireless network interfaces, and even if the Wired
AutoConfig (DOT3) service is disabled.

This issue is currently open with Novell as Bug 701413. It will not
be addressed in the upcoming Novell Client 2 SP1 (IR8), but as soon as
there is a post-IR8 release for Novell Client for Windows 7 and/or a
post-Novell Client 4.91 SP5 (IR1) release of NOVEAP.DLL citing Bug
701413 as fixed, this issue should be addressed.

Unfortunately there isn't any workaround other than disabling NOVEAP
at the moment, because there aren't any optional conditions which can
avoid the interface disable-reenable cycle that gets interrupted on
shutdown and potentially leaves the interface abandoned in the
disabled state.

If anyone is seeing this issue and DOESN'T have NOVEAP enabled
(meaning a visual inspection of the
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\RasMan\PPP\EAP\26]
confirms definitively that Microsoft's RASCHAP.DLL is still registered
as the MSCHAPv2 provider instead of Novell's NOVEAP.DLL), then that
would not fit the parameters of the currently known issue.

Alan Adams
Novell Client CPR Group
alan.adams@novell.com

Novell
Making IT Work As One
NOVELL Worldwide

Upgrade to OES Community
Upgrade to Open Enterprise Server | Novell User Communities
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Network Card becoming disabled

kpmonson <kpmonson@no-mx.forums.novell.com> wrote:

> Unregistering the noveap.dll seems to be working for us.


Good, hope that permits you to work around the issue until it is
finally resolved.

Note that setting "802.1x Authentication" to "Off" in the "Advanced
Login" tab of the Novell Client Properties is what's expected to
disable and de-register NOVEAP.DLL. Running REGSVR32.EXE /U against
NOVEAP.DLL directly will also work, but is the action performed by the
Novell Client Properties item, too.

Just wanted to clarify that I had mentioned the registry location
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\RasMan\PPP\EAP\26]
only as the most definitive place to check for whether NOVEAP.DLL was
currently registered. And not because you're expected to somehow
manually de-register NOVEAP.DLL or change the registry setting
directly.

Alan Adams
Novell Client CPR Group
alan.adams@novell.com

Novell
Making IT Work As One
www.novell.com

Upgrade to OES Community
http://www.novell.com/communities/coolsolutions/upgradetooes/
0 Likes
Robert_W_Brandt Absent Member.
Absent Member.

Re: Network Card becoming disabled

Sorry for the late response but I just haven't had an opportunity to test this.

But we finally found a workstation here that had the problem and I too can report that this does fix the problem. I won't call it a fix rather than a workaround and it could cause some problems in the future since we do have many workstations that do use 802.1x.

However I guess we will just have to wait for the next updated client.

Thanks
Bob
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.