Discussion Locked

username of 1st login stays in explorer?

0 helpful
45 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

i'm running a netware 4.11 environment with various versions of novell client (3.1 and above). there are different model workstations running windows 95 and a NAL shell. the first person that logins has no problem. however subsequent users retain the username of the first login's in their drive mapping to their home directory. they are actually correctly mapped to their user directory but 'explorer' or the 'save as' functions display the first users drive mappings. any ideas what is causing this and how to correct it?
thanks,
chuck

45 replies

by ahevans

I'm going to take a shot at this. I've seen it before and had corrected it but I can;t recall exactly what I did. Here it goes, go in to you windows explorer and in the windows dir. remove the file with the extension .pwl. I hope this helps resolve the login issue.

by chazthespaz

it was a good thought. i tested the theory out. the original drive mappings from the original user are still there despite deleting all existing *.pwl's. the only way to get the correct mapping information to display is to reboot.
thanks anyway,
chuck

by gregory w. smith

So basically, what you are saying is that Explorer displays the mappings as if they are for the first user, but instead, they are actually pointing to the currently logged on user. (and that this resets with a reboot).

To me, it sounds like the client is not updating Explorer, and there are a few ways to test. With the same client on 95OSR2, 95OSR2.5, 98, 98SE is the behaviour consistent? That would point to the client. Otherwise you will see a version of Win9x where your trouble is fixed. You could then "rev up" the workstations to the working version.

What exactly is the NAL client (NetWare AutoLogon?) and is there a newer version available?

by mark fenwick

I have witnessed this issue manu times with Windows 98SE, though I dont know if it is specific to any particular version of Windows.

The problem is not Network OS dependant as, in my experiences, the workstation was logged into an NT domain.

Does pressing F5 in Explorer or from the Desktop refresh the drive mapping names correctly? It did for me in the past.

Are you using group policies at all? Policies were in use on each occasion I observed this behaviour and suspected they were related.

Let me know!

by chazthespaz

there are no group policies and f5 does not refresh the drive mappings unless you have the specific drive mapping highlighted.

by bmarks

I believe you need to make sure that the local machine needs to have profiles turned on. Try using the profiles command in the control panel. This will enable the desktop to be saved for each of the end users that log on to that particular machine. One can, also, set up roving profiles which allows users to log on using any machine connected to the users domain and get their own personal desktop, along with the needed mapped drives, etc. This get a little more complex in a WIN98/NT/2000 environment, however.

by white wolf

This problem sounds like a another wrinkle to the novell client Bug where the registry changes it made become persistant or permanent for some reason. My problem specifically was the first person who logs in was being remembered no matter who was logging in afterward. I eventually figured out which registry items to edit in order to fix this annoyance by refering to Novell's TID# 10013620. Check that out, there's a good chance you'll find that registry changes the client is making relates to your problem.

- Good Luck!

(You can find the TID at http://support.novell.com/cgi-bin/search/search.pl?database_name=kb&type=HTML&docid=%03%23F219757%3a976645110%3a%20%28%20client%20bug%20%29%20%20%07%01%00&byte_count=140533)

by mpastore

DL Power Toys from MS, and Install tweak.ui
Go to the covering you tracks section and clear everything, this might help.

by max

Back up the registry, use regedit,edit and find the name of the 1st logon person. Every time the name comes up, right click , modify, and remove the name. If you run into trouble, re-instate your old registry. Contact me if you do not know haw to backup the registry

by chazthespaz

we have over 1300 pcs in this school district. with new students logging in hourly i don't see how this would be manageable. sorry, chuck

by max

The first person who logged on must be the network administrator, all files will be referred to him. So there is nothing you can do about it, as he has his own password, and is in control of the system. Nothing short of a hack will change this. He can change it though.

by patrick_mulrean

Given the information, I would say that the "clear current connections box" is not checked. If it is not available in the client version you're using, you may enable it in regedit (provided you're using client 2.5 or higher)
the string you'll need to check in Win 9x
Registry Key: HKLM\SOFTWARE\Novell\Location Profiles\Services\{1E6CEEA1-FB73-11CF-BD76-00001B27DA23}\Default

there will be up to five keys labled "Tabx" (where x= a numerical value between 1 and 5)
these will be differenton individual machines. check in each until you find the string called "Tab" (you may have 2 if you use both bindery and NDS)
Once located, find the DWORD "Clear Connections" set it to "1" to enable.
hope that helps.

by baziite

I agree with Answer Number 5 . It seem to relate to the User profile . By setting up profiles so that all users use the same desktop settings every user will get the same label for their Network drives after the first Login . So you should change the user profile settigs on the passwords applet in control panel to
" user can cutomize desktop settings and preferences " . This will refresh the label every time a user logs on . I hope this Helps ...

Good Luck !!!

by tbradley

How are you accomplishing the drive mappings?

Through a static Workstation mapping, or via login scripts? I would assume login scripts.

If login scripts, the mappings must be done per user, not as a container, workstation, or
group login. user logins have the lowest heirarchy, and container scripts will not be cleared by subsequent user login scripts.

You didn't mention any error messages. Do you have the display scripts tab checked, so you can see what error codes are returned?
Also, ensure your current connections tab is checked.

One last step to try, to help trouble shoot is to completely clear all connections, without the start-run-logoff, and log in as a different user to see if the connection does clear.

areyou using map root statements? if not, do so. Also, avoid the @ and # characters for drive mapping.

by tbradley

as usual, having re-read the question, I now see what you mean, and it may have something to do with the tools/synchronize function in explorer. This would explain the drive mapping, but I still don't have a clue on the save as.....

by mr_cellophane

How are the subsequent users loging in ?
You say that the only way to get the correct mappings is to reboot. Does this mean that once someone has logged in a second person comes along and uses the START/PROGRAMS/NOVELL/NOVELL LOGIN icon ?
If so then this is where your problem is. I have found that login script never seem to run properly this way.

by jhoyt

Client 3.1 should be fine, but Client 3.21 and 3.3 will leave the username of the first person to login, unless you edit the registry, but then it will hold the username of the next person to login. Recommend using Client 3.1 w/ SP1 or SP2.
-Jeff

by phil jackson

there are 2 logins happening when you first type in your username & password: - Windows & Netware. How are your clients loging out? through the Novell sotware or Windows logoff. Try logging out through windows (start, shutdown & logo-on as a different user). Profiles are reliant on username so that wouldn't clear the problem. Another thing you could try is right click on each drive mapping and select disconnect. Then go into Network properties and make sure that quick logon is selected. This will ensure that drives are mapped when the user logs on & drives are automatically disconnected when the user logs-off. If you are using group policies then you may need to modify the same setting in there as well. If you dont know if you are or not - look for a file in the public directory on the servers with a .pol extension. If you dont know how to modify this file, let me know. Another thing you could do with checking is if user-level security is enabled (it should be). This is also in Network Properties.

by mhenning

I'm not sure of the cause of this, but implementing a login script (if not in place already,) would definetly be the best answer. Be sure to add a delete statement in the script as well. i.e.:
net use h: /delete /yes
and
net use h: \\server_name\server_share
or
net use h: /home
Hope this helps!

by walterzalewski

Since you are using client 3.x, try this..
1. Bring up the properties for the client
2. Go to the "Location Profiles" tab
3. Highlight the "Default" profile, then click on "Properties"
4. Under "Service Instance", make sure "Default" is shown, then click on "Properties"
5. There will be a check box that says "Save profile after successful login", UNCHECK it
*** This will wipe the properties (user name, mappings, etc) of the previous user after they log out***
6. If using NDS, then click on the "NDS" tab and CHECK the "Clear current connections" box

Hope that helps, good luck.

by bruceh

Under regedit Hkey_Local_Machine/Software/Novell/Contexts
Hkey_Local_Machine/Software/Novell/Preferred servers
Hkey_Local_Machine/Software/Novell/Trees

You can clean out those settings. Novell goes there first to pick up old settins. If you have NT then check in Hkey_Current_User settings as well.

by emcs

Get tweakui for windows 95. When you run tweakui got to the Paranioa tab and uncheck the Clear Last User at logon.

dennie

by emcs

You can also go to the registry, but why go there if you do not have to.

dennie

by emcs

You can also go to the registry, but why go there if you do not have to.

dennie

This discussion is closed to new replies.