Are you sure the settings in the new GPO are applied to this user? The new GPO needs to have priority over the original one for the settings in it to "win". If they do, there must still be something missing. Could you post the settings of the new GPO?

Hey Ctrl-X,

thanx for yer response m8.

I performed all the steps you mentioned in yer last post.

Yes, the new GPO is listed above the original one. I found out that all users/groups except the admins, and Network Configurations Group are denied acccess to Network Settings. So, I addded the user to the Network Configurations Group, but that did not make any difference either.

The only settings that I made in the new GPO are under Userconfiguration\Administrative Templates\Network\Network Connections.

Anyone ??

Ctrl-X ???

Here I am I'm sorry, but I can't imagine what's going wrong... Are you really really sure the user in question is getting the correct combination of policy settings? To make sure, run the Resultant Set of Policy snap-in (rsop.msc) under that user's account. If the settings appear correct, post the results here. There may still be something that's overlooked...

Hi,

Did you tried to add the user into the 2003 "Buildin Group" named "Network Configuration Operator"????

Will this help????

Yes Hons, I tried that, but it did not work. It seems to be some over-sight on my behalf, but I cannot figure out what.

Hi Ctrl-X,

I've attached the result generated by GPresults.exe, for the user. The username is LtdAdmin. This is the user for whom I want to permit access to modify network settings on any of the workstations on the Domain.

A few things I think you should know when reading the GPresults

The Domain name is Crest.com

The servername is Crestserv01.Crest.com

The general blanket group policy for all computers, and users is Crest Group Policy

The group policy that permits LtdAdmin to modify network settings is Limited Admin's Group Policy. I have placed this GP above the generic group policy : Crest Group Policy

The name of the file generated by GPresult.exe is LtdadminPol.txt

I hope this info helps. If you require any further info, please do let me know.

Thanks !

LtdadminPol.txt

Edited October 28, 200619 yr by Hamins

Hi Ctrl-X,

I have attached the GP settings. Please look at it, and let me know whats wrong.

I have attached the GP settings. Please look at it, and let me know whats wrong.

Sorry for taking so long to reply... As far as I can see, there's nothing wrong with the settings. I'll see if I can get this working in our test environment and let you know what the results are, OK?

I hope you can figure out what the problem is.. Do lemme know.

Thanx

Well, I checked this in our test environment today, and I was able to get it working just by adding the user to the Network Configuration Operators group! Said user could change all kinds of network properties, including IP address, subnet mask, default gateway, DNS servers, and so on. So that should be enough, as long as the user isn't prohibited from changing network settings through Group Policy.

Hi Ctrl-X, the user is already a part of the Network Configuration Operators group, yet the problem

At this point, if the user is not working even in the proper group, take a test machine off of the domain and create a test user in the appropriate network operators group, and see if it works. This should rule out whether or not a domain policy is causing this. Also, filemon/regmon while attempting to change network configuration data may point us at a policy or OS mod to get this to work as well.

Hi Cluberti,

I don't quite understand what u're sayin .. ??