GPO: User to change TCP/IP settings:

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Server: Windows 2003 Standard
Clients: Windows 2000 SP4

Problem:
All users are part of the domain, all users are part of a specified OU with
GPOs set.

While I know it is not common practice, I require that my users are able to
get into the properties of the 'Local Area Connection' and configure the
tcp/ip settings without getting the following error:

'The controls on this property sheet are disabled because you do not have
sufficient privileges to access them. Please contact your Administrator'

When editing the GP of the OU using the GPOE (User Configuration ->
Administrative Templates -> Network -> Network Connections) there are a
number of options here that specifically allow you to modify this behaviour
and allow users the ability to change these network settings. However, try as
I may it doesn't matter what I set in these GPOs or how many times I reboot
the client machine, I still get the same error message.

I have also try to stop policy inheritance and set the no overide option and
neither proved to have any effect.

Any immediate help in this regard would be most appreciated.
 
Hi Rhys-

If you happen to have any Windows XP or Server 2003 member server clients do
you see the same issue with them? The reason I ask is that I beleive that
setting will only process for the 'up-level' or newer operating systems if I
recall correctly.
 
Thanks for your reply Tim,

There are 21 configuration options within the 'Network Connections' tab of
the GPOE. All but 3 of them specify a minimum of Windows 2000 SP1 required,
the other 3 are for a minimum of Windows XP or 2003 server family.

Options such as the following are all (apparently) Win2k SP1 compatible:

- Ability to rename LAN connections and RAS connections availabe to all
users. (This works by the way)
- Prohibit access to the properties on the LAN connection. (when disabled,
it still denies me access)
- Prohibit access to disable/enable LAN connections. (If I recall correctly,
this does work)
- Prohibit tcp/ip advanced configuration. (I cant test this as I cant get
into the properties of the LAN connection)

These three options are for XP and 2003 server family:

- Ability to rename LAN connections. (This works with setting above for W2k)
- Ability to rename all user remote access connections.
- Enable Windows 2000 network connection settings for Administrators.

--
Am I missing something? Some of these options work and some dont - is there
anyway another configuration option is conflicting? I'm completely puzzled,
and in dire need of some pointers.

I have spoken to an MS 'representative' who spoke to the MS Engineer (I
never spoke to the Engineer directly) who in turn told me I cannot access
these settings unless Im the local administrator on the system, which I
absolutely refuse to believe considering the options I am presented with in
the GPOE. I was also told that I cant enable the option to double click on
the local system time for domain users machines (which I CAN btw, by enabling
it via GPOE) and so am rather skeptical about that engineer on the other side
of the phone.
 
Rhys said:
*Server: Windows 2003 Standard
Clients: Windows 2000 SP4

Problem:
All users are part of the domain, all users are part of a specified
OU with
GPOs set.

While I know it is not common practice, I require that my users are
able to
get into the properties of the 'Local Area Connection' and configure
the
tcp/ip settings without getting the following error:

'The controls on this property sheet are disabled because you do not
have
sufficient privileges to access them. Please contact your
Administrator'

When editing the GP of the OU using the GPOE (User Configuration ->
Administrative Templates -> Network -> Network Connections) there are
a
number of options here that specifically allow you to modify this
behaviour
and allow users the ability to change these network settings.
However, try as
I may it doesn't matter what I set in these GPOs or how many times I
reboot
the client machine, I still get the same error message.

I have also try to stop policy inheritance and set the no overide
option and
neither proved to have any effect.

Any immediate help in this regard would be most appreciated. *
Click to expand...

I have the exact same problem, what am I missing?
 
Anybody ever find the answer to this??? This is driving me nuts! I have hunted through forums for hours now, tried everything I could find, still no work.
 
Back
Top