Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Win98 problem

Status
Not open for further replies.
Sep 26, 2002
65
US
Early this afternoon I received a call from a client that had the following problem on several Win98 workstations:

When they get to the login screen (Win2003 Active Directory domain) they can put in their username & password, the dialog box then goes away, an error message pops up "explorer caused a stack fault in module shlwapi.dll" (I'm not sure if the .DLL is the same on all of them - it may differ), and they then either get a black screen or their normal wallpaper but nothing else -- no Start button, no icons, zelch. For all practical purposes it locks the computer up.

The computers will come up in safe mode with no problem. We use CA's eTrust InoculateIT (version 6). Signatures are today's date (one workstation that I know of had updated it's signatures 2 to 3 hours before it started having problems) and no viruses have been found on the computers we have scanned thus far. We have also ran SpyBot - it found & cleaned some "problems", but unfortunately not the real problem at hand. These are your basic workstations - Win98se, InoculateIT, Office 2000, and some custom VB programs that they have been running for years (the executables for the VB programs reside on the server). This is basically it. Also, these computers are in different towns. The login script we use is the run-of-the-mill drive-mapping scripts -- nothing fancy. There was nothing other than the signatures updated today (that I am

If I can provide more information, please let me know.

Has anyone else had this problem pop up today??

Thanks,
bw
 
Shortly after posting this I came upon what I think is the problem. Earlier today I *did* make another change that I had completely forgotten about. When I create a new user in AD, in their profile I always map U: to \\server\users\username. Late this morning I discovered that when I create a new user, it gives <domain users> to that user's folder -- thus EVERYONE can get to it. Not good. I found that it was inheriting this from the security of the share (ie, Users). I removed <domain users> group from the share thinking I had solved the problem.

Turns out, the Win98 workstations (not sure about XP) couldn't get to their U:. I'm pretty sure that was the problem (I put the security back to the way it originally was). I'll know in the morning when the clients gets to work.

This leads me to the quesiton I really need to know -- how do I set up my 'Users' share so that when I create a new user, it does *not* give everyone access to it? I just want that user & administrator to have security.

Thanks again -
bw
 
The trick is to NOT manually create the user's individual folder, let the server do it.


In Ad Users & Computers, open a user account, go to the profile tab, Put the drive and path you wnat in the 'Home Folder' section.

Windows will automatically create the folders with the appropriate permissions.
 
dearingkr -

That is what I'm doing -- and it is adding the group 'Domain Users' to each individuals' folder. As it is, the folder is automatically being created, but I'm having to manually remove 'Domain Users' from the folders.

bw
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top