Re: securing w2k clients
From: neo [mvp outlook] (neo@mvps.org)
Date: 10/17/02
- Next message: Sajith: "Password Expiry"
- Previous message: neo [mvp outlook]: "Re: Q285903 (error 1332) lack of mapping account names-security ID's Can't find powe"
- In reply to: Ben: "securing w2k clients"
- Next in thread: ben: "Re: securing w2k clients"
- Reply: ben: "Re: securing w2k clients"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "neo [mvp outlook]" <neo@mvps.org> Date: Wed, 16 Oct 2002 21:25:30 -0700
This is a guess, but try creating the policy via the Group Policy editor
(GPEDIT.MSC). Location is, User Config. > Admin. Templates > Network >
Network and Dialup. You should see one on the right labeled prohibit access
to properties of LAN connection.
"Ben" <benntn@hotmail.com> wrote in message
news:484d01c27561$62dad020$2ae2c90a@phx.gbl...
> Is there a way to prevent a w2k client from accessing or
> changing their static IP address? I've used Poledit to
> make this possible on 98x and NT boxes but it doesn't work
> on 2000. I don't really want to change the users
> profile. They have admin rights locally to their
> machine. I'm running an NT domain as well. If I change
> the profile to a standard user, some of our own program
> will not run plus the user loses all of his or her
> configuration. Is there a way around this? All I want to
> do is stop a user from changing their IP address.
>
> Ben
- Next message: Sajith: "Password Expiry"
- Previous message: neo [mvp outlook]: "Re: Q285903 (error 1332) lack of mapping account names-security ID's Can't find powe"
- In reply to: Ben: "securing w2k clients"
- Next in thread: ben: "Re: securing w2k clients"
- Reply: ben: "Re: securing w2k clients"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|