ALERT! The community will be read-only starting on April 19, 8am Pacific as the migration begins. Read more for important details.
ALERT! The community will be read-only starting on April 19, 8am Pacific as the migration begins.Read more for important details.
This website uses cookies. By continuing to browse or login to this website, you consent to the use of cookies. Learn more.
OK
jschick
Absent Member.
Absent Member.
‎2013-09-05 20:11
1076 views

NMAS installed but broken, how to fix?

Hi,

I had a user mention that his password suddenly stopped being case sensitive. I looked at his workstation (XP running client 4.9.1 SP5 IR1) and noticed the "Did you forget your password?" link was missing on the initial login screen, along with the NMAS tab when I clicked Advanced.

The IR2 client had just become available, so the first thing I tried was installing that over the top. No change.

I went to check the Location Profile (only Default exists) to make sure the NMAS tab is enabled. It is, but that screen also says "NMAS client version: (unknown)".

I went to a command prompt and ran "ncc.exe -i". The response was version 3.4.5.0 is installed.

I went to Add Remove Programs and verified NMAS Client and Challenge Response Method are listed. They are. On the NMAS client I clicked the link for Support Information, and then the Repair button. No change.

A side note, that Support Information window lists the version as 3.4.3.0. But it shows that on a correctly working IR2 client, so have to assume that was just an oversight by the developers and not related to this problem.

Anyway, I am not sure what to try next. Would doing an NMAS client trace offer any help? Are there specific files or registry keys I can compare against a working machine? Do I need to do a complete uninstall, and if so, is there a specific order to follow, and would I have to manually clean up said files or registry keys?

Thanks for any insight,

- Justin
Labels (1)
Labels
0 Likes
Report Inappropriate Content
3 Replies
buckesfeld
Absent Member.
Absent Member.
‎2013-09-09 16:06

What if you simply install the entire client again? Or just the nmas/nici MSIs? Or uninstall NMAS first?

Uwe
0 Likes
Report Inappropriate Content
jschick
Absent Member.
Absent Member.
‎2013-09-16 13:59

buckesfeld;2281315 wrote:
What if you simply install the entire client again? Or just the nmas/nici MSIs? Or uninstall NMAS first?

Uwe


The re-install over the top did not help.

After that I did try a complete un and re-install. NMAS was happy until I ran AutoLogon to automate local Windows authentication, and that is when I found the root of the problem.

My predecessor was using an old version of AutoLogon (3.0.1.1). I ran it and had it disable itself, and NMAS was happy again.

I found a new version of AutoLogon (3.0.1.3). Applied that and NMAS was still happy afterward.
0 Likes
Report Inappropriate Content
buckesfeld
Absent Member.
Absent Member.
‎2013-09-18 19:07

Glad you got it sorted!

Uwe


--
Novell Knowledge Partner (NKP)
Please don't send me support related e-mail unless I ask you to do so.
0 Likes
Report Inappropriate Content
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.