Login Script Error Message

[spyser]

Hi everyone,

i have a little problem maybe someone has experienced before. on the network here where i work we have a large mix of Win 98, 2K, and now XP machines. We have this login script which executes a .reg file amongst a few other things, which apparently stops password caching. On 98 and XP machines logging in is no problem. However, on Win 2K machines (all of them)we receive a registry editor error message upon logging in (when the script is executing) which reads "cannot import \\network_path\nocache.reg: error accessing the registry". even with administrative access it still does this. i can get into regedit and regedt32 and make changes, just fine. am i experiencing some kinda hidden restriction or something? anyone have any ideas?

thanks for reading

 

[spyser]

Also I wanted to include what the .reg file contains in it, maybe it will help:

REGEDIT4

[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\Network]
"DisablePwdCaching"=dword:00000001

[HKEY_LOCAL_MACHINE\Network\Logon]
"PrimaryProvider"="Microsoft Network"


thanks again.

 

[FieldSanitation]

What kind of Domain are you running? or is it just shared drives on workgroups?

 

[spyser]

hi,

thanks for responding! i'm not sure what you mean when you ask what kind of domain is it? (i'm not the domain administrator..but apparently those guys don't want to deal with this problem anyway). its not a bunch of shared drives on a workgroup, though. i wanted to find out if this is a local problem (or could be fixed locally) on each persons machine getting this error or would it have to be taken out of the login script or something. the strange this is theres no problems on win xp or win 98 machines.

 

[SgtJarrow]

Shooting in the dark and from the hip here......but I am going to say that this is a permissions issue.....The user is logging in without Admin rights to the machine....therefore, they don't have permission to access the registry in this manner. I would look into a group policy to give the users access to the registry, although this could be dangerous in itself.

The reason this appears in 2000 only is that 98 and XP are OS's designed more for the home user, and do not normally have all the security that 2000 does. 2000 is a business edition OS and has been developed with security as a priority. As you should be aware, there is not much you can do in 2000 except use existing software without Admin rights. But in 98 or XP almost anyone can add hardware/software. If we knew what it was we were doing, it would not be called research, would it? - Albert Einstein

Robert L. Johnson III, A+, Network+, MCP
Access Developer/Programmer
robert.l.johnson.iii@citigroup.com

 

[spyser]

sorry for the delay in my response...

well...one of the machines i am talking about is mine..which is on Win 2K, and i am an administrator for sure, and i still get the error. i can freely look around and make changes to anything in regedit so i'm not sure if the problem is not having access to the registry where the login script is referring to.

if that is the case then is there anyway i can give myself access and see if i still get the error before i go and try an implement a group policy? thanks for getting back

 

[SgtJarrow]

What you need to do is check the permissions of the local login....log into the machine using a local (not your domain) account name and check what the permissions are. Saying this VERY loosely, you are probably going to have to give the LOCAL EVERYONE group access to the machine that will include the ability to edit the registry.

You are probably experiencing the error also because you are logging into the machine using a domain admin profile, but the local profile does not reflect the same permissions.... Please remember to give helpful posts the stars they deserve! This makes the post more visible to others in need!

Robert L. Johnson III, A+, Network+, MCP
Access Developer/Programmer
robert.l.johnson.iii@citigroup.com

 

[spyser]

i logged in locally as administrator and checked everything. the permissions are set as they should be and i am an administrator of the machine locally even when i log into the domain. at first i wasn't, i had to add myself to that group.

like i said i can edit the registry just fine, so i guess i have access to it, along with everyone else having this problem in the network.

i tried something new this time. i took the .reg file that is run from the login script that is giving the problem and copied it to the harddrive. then logged in locally as administrator and ran the .reg file and i still got the same error (error accessing registry). so i opened it up and theres a line in it that points to a location in the registry that doesn't exist. when i removed the line and tried again it worked, with no errors.

i am not sure if this same location exists in win xp, but i never get errors when i try it on win xp. since the line in the .reg file is apparently the cause of the problem, is there an easy way to make this go away? like have windows quietly ignore it and not give errors (without removing it from the .reg file on the server which i don't have access to).

thanks!