UNIX Integration NIS Authentication Feature Issue

RoyATokeshi
March 26, 2004 4:47 pm

Citrix states in their article: CTX524944

CTX524944 - UNIX Integration NIS Authentication Feature Issue

This document was published at: http://support.citrix.com/kb/entry.jspa?externalID=CTX524944

Document ID: CTX524944, Created on: Aug 2, 2000, Updated: Apr 23, 2003

Products: Citrix MetaFrame 1.8 for Microsoft NT 4.0 Server Terminal Server Edition, Citrix MetaFrame 1.8 for Microsoft Windows 2000, Citrix WinFrame 1.8

The FMJAUTHauthentication package from UNIX Integration Services replaces the default Microsoft authentication package. Standard Windows NT allows you to change any account's password from the

Here are the reproduction steps:

1. Log onto any Windows NT server.
2. Press Ctrl+Alt+Del and change the password.
3. Enter a vaild username (different from the user currently logged on).
4. Choose the current domain, trusted domain, non-trusted domain, or type servername for a workgroup server.
5. Type the old passsword and new password information.
6. The password changes successfully.
7. Log onto a Terminal Services/MetaFrame 1.8 server with or without Service Pack 1.
8. Repeat Steps 1 through 6.
9. Install UNIX Integration Services 1.0a or 1.0b with or without Service Pack 1.
10. Repeat Steps 1 through 6. The current domain and trusted domains still work.
11. Non-trusted domains and workgroups return the following error message:

"The username or old password is incorrect. Letters in passwords must be typed using the correct case. Make sure the Caps Lock is not accidentally on."

12. If you uninstall UNIX Integration Services, all works fine again.

If NIS authentication is needed and the Windows NT feature is absolutely needed, please notify Technical Support to determine the status on this issue.

If NIS authentication is not needed, a workaround is necessary.

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Back up the registry before you edit it. If you are running Windows NT, also update your Emergency Repair Disk (ERD).

1. Run Regedt32.

2. Go to the following registry key:

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlLSA

value authentication packages:

With UNIX Installation Services installed, the value fmjauth exists

The default value is msv1_0.

3. Remove fmjauth and add msv1_0.

4. Close the registry.



Primary links

Custom Search

User login

Who's new

  • japhabept
  • Rullydery
  • eagenorce
  • rittaarier
  • swasseZex

Who's online

There are currently 0 users and 3 guests online.

KrissysCorner.com RuthSwensonLaw.com CreativeLizardProductions.com

DISCLAIMER:

None of this has anything to do with us, someone else is responsible for the entire thing, and we have no idea who or why. We do not know anything about it. It may be alien life forms for all we know: we haven't a clue. You cannot blame us for anything that may result from your visit. That was entirely your own personal choice, made by you of your own volition, and without our knowledge. We do not, after all, have any control over you and cannot by any stretch of the imagination be expected to accept or acknowledge, be it legally or morally, any accountability for decisions made by you on an independent basis, utilizing your own free will, and without our intervention. We are therefore in no way, shape, or form answerable to anyone for any consequences arising from the aforementioned or indeed any other actions, similar or otherwise, because it was not us that did, or did not do anything. It is not even remotely our fault, and we are in no way prepared or willing to accept any liability, not even slightly, ever. We are, in fact completely and utterly blameless, in that it is definitely not our concern, and no blame can possibly be laid at our doorstep, even if we had one, the possession of which we hereby reserve as being entirely our own free choice. The onus is not on us at all, and furthermore, never has been. The entire matter is wholly beyond our control, and completely out of our hands, each of which are washed scrupulously clean of the whole business. We are not accountable for anything at all, and we hereby categorically deny all responsibility for all that has ever, or will ever happen. Our innocence is therefore wholly beyond doubt and absolutely unimpeachable, and so cannot, under even the remotest or unlikeliest circumstances, be brought into question. By clicking either on a link on this site, clicking on a link that leads to this site, or by arriving at this site by natural or supernatural means, you are in effect accepting responsibility for the fact that it is all entirely your own fault, down to the most miniscule detail, and that you are wholly accountable for whatever outcome may arise as a consequence of the aforementioned action or actions insofar as they were undertaken personally by you on an entirely voluntary basis and without any persuasion, coercion or influence from any party or parties other than yourself. Don't come sniveling to us, we are only figments of your imagination. I also agree that if I am ever with a contributor to this website during mealtimes I agree to pay for any super-sizing of their meal, or at least a nice dessert or one of those foo-foo drinks with an umbrella or a monkey. By admitting to have seen the worthless spineless drivel on this website (also known as content)

I Agree Wholeheartedly and Without Reservation to the above. (Except maybe for that part about the monkey.)

All Your Base Are Belong To Us.

Soylent Green Is People!

Never make a bet with a Sicilian when Death is on the Line!

No. Really, I do agree.