Anonymous_User Absent Member.
Absent Member.
1765 views

4.91 SP4 client/802.1x and wireless


Hello all...

I know the SP4 client is a recent appearance,
but just interested in anyone else is testing it.

We have the following:

- laptop with 4.91 SP4 installed
- one wireless network defined that is set
to use 802.1x (WPA/TKIP, PEAP and Novell EAP chosen)

The user we are testing has no local account,
but we assumed this process would create one following authentication.

Trying this, we fail to login at the GINA, but then after
getting to the desktop, the EAP plugin tries to authenticate
the user we have logged in with locally.

Additionally we also see authentication requests for
'yadayadauser' which we guess is probably a debug feature?

I'd be grateful to hear from anyone else
that has been testing this.

Peter Bates,
Systems Support Officer,
IT Services,
London School of Hygiene & Tropical Medicine, London, UK.

Labels (1)
0 Likes
3 Replies
Anonymous_User Absent Member.
Absent Member.

Re: 4.91 SP4 client/802.1x and wireless

Same problem's here. Cannot login until you login one time with a wired
connection. After that login sometimes works with 802.1x, not always. We
also see yadayadauser flashing by. Especially when you logout.

Logout will also get you that the roaming profile could not be uploaded
to the server error. I cannot translate this message into English.

Feature request: It also would be nice to see which SSID you're
connected to in the Novell Client. Or better search for an active
Wireless network. This way you could see or connect to a Wireless Network.

If you've figured out something can you share you're info with me
please? Maybe together we can make something working.

Regards.

M. Duran
mduran(at)aoc-oost.nl









Peter Bates schreef:
> Hello all...
>
> I know the SP4 client is a recent appearance,
> but just interested in anyone else is testing it.
>
> We have the following:
>
> - laptop with 4.91 SP4 installed
> - one wireless network defined that is set
> to use 802.1x (WPA/TKIP, PEAP and Novell EAP chosen)
>
> The user we are testing has no local account,
> but we assumed this process would create one following authentication.
>
> Trying this, we fail to login at the GINA, but then after
> getting to the desktop, the EAP plugin tries to authenticate
> the user we have logged in with locally.
>
> Additionally we also see authentication requests for
> 'yadayadauser' which we guess is probably a debug feature?
>
> I'd be grateful to hear from anyone else
> that has been testing this.
>
> Peter Bates,
> Systems Support Officer,
> IT Services,
> London School of Hygiene & Tropical Medicine, London, UK.
>

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: 4.91 SP4 client/802.1x and wireless

Who must I contact if I have problems with a beta version?

M. schreef:
> Same problem's here. Cannot login until you login one time with a wired
> connection. After that login sometimes works with 802.1x, not always. We
> also see yadayadauser flashing by. Especially when you logout.
>
> Logout will also get you that the roaming profile could not be uploaded
> to the server error. I cannot translate this message into English.
>
> Feature request: It also would be nice to see which SSID you're
> connected to in the Novell Client. Or better search for an active
> Wireless network. This way you could see or connect to a Wireless Network.
>
> If you've figured out something can you share you're info with me
> please? Maybe together we can make something working.
>
> Regards.
>
> M. Duran
> mduran(at)aoc-oost.nl
>
>
>
>
>
>
>
>
>
> Peter Bates schreef:
>> Hello all...
>>
>> I know the SP4 client is a recent appearance,
>> but just interested in anyone else is testing it.
>>
>> We have the following:
>>
>> - laptop with 4.91 SP4 installed
>> - one wireless network defined that is set
>> to use 802.1x (WPA/TKIP, PEAP and Novell EAP chosen)
>>
>> The user we are testing has no local account,
>> but we assumed this process would create one following authentication.
>>
>> Trying this, we fail to login at the GINA, but then after
>> getting to the desktop, the EAP plugin tries to authenticate
>> the user we have logged in with locally.
>>
>> Additionally we also see authentication requests for
>> 'yadayadauser' which we guess is probably a debug feature?
>>
>> I'd be grateful to hear from anyone else
>> that has been testing this.
>>
>> Peter Bates,
>> Systems Support Officer,
>> IT Services,
>> London School of Hygiene & Tropical Medicine, London, UK.
>>

0 Likes
Anonymous_User Absent Member.
Absent Member.

4.91 SP4 client/802.1x and wireless

Peter,

I get have the exact same problem over here.

The 802.1X doesn't seem to authenticate to the wireless network untill
after the local login takes place. It does "cache" the login credentials
supplied at the initial Novell login prompt and paas them along to
FreeRadius - but this isn't the funcionality described by the client
download page.

When attempting to login from the initial login screen I get the
following error:

802.1X Authentication failed. Timeout waiting for authentication to
finish. Logging in to the workstation only.


One time I got a more prommising error:

802.1x found no connections to authenticate.

Has anyone gotten this to work??

-Matt

>
> Hello all...
>
> I know the SP4 client is a recent appearance,
> but just interested in anyone else is testing it.
>
> We have the following:
>
> - laptop with 4.91 SP4 installed
> - one wireless network defined that is set
> to use 802.1x (WPA/TKIP, PEAP and Novell EAP chosen)
>
> The user we are testing has no local account,
> but we assumed this process would create one following authentication.
>
> Trying this, we fail to login at the GINA, but then after
> getting to the desktop, the EAP plugin tries to authenticate
> the user we have logged in with locally.
>
> Additionally we also see authentication requests for
> 'yadayadauser' which we guess is probably a debug feature?
>
> I'd be grateful to hear from anyone else
> that has been testing this.
>
> Peter Bates,
> Systems Support Officer,
> IT Services,
> London School of Hygiene & Tropical Medicine, London, UK.
>


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.