(de)activate Ethernet connection by restricted user.

[=?ISO-8859-1?Q?Ren=E9?=]

I am using Win2k professional. For a user without administrative rights
it is impossible to (de)activate the LAN connection. Still the same I
sometimes need this, when DNS server of my LAN got on-line later.

Now I have to log-off as restricted user and log-on as administrator,
(de)activate de LAN connection, log-off as administrator, log-on as
restricted user.

Is there a way to allow a restricted (non-administrative) user to
(de)activate the Ethernet connection? Or another way to do it?

Thanks for your tima and help!

 

[Guest]

Briefly,

1. open a command prompt and type "mmc"
2. Console > Add/Remove Snap-in > Add
3. select Group Policy > Add > Finish (default accept: Local Computer)
4. Close > OK
5. Expand User configuration branch > Administrative Templates > Network

Network and Dial-up Connections

6. Take your pick on right hand pane.
7. Save your mmc console for future access.

The above is for Local Computer Group Policy (GP) only and needs local admin
rights to perform. The same can be achieved in a Win 200x AD domain.

 

[Lanwench [MVP - Exchange]]

I am using Win2k professional. For a user without administrative
rights it is impossible to (de)activate the LAN connection. Still the
same I sometimes need this, when DNS server of my LAN got on-line
later.

Now I have to log-off as restricted user and log-on as administrator,
(de)activate de LAN connection, log-off as administrator, log-on as
restricted user.

Is there a way to allow a restricted (non-administrative) user to
(de)activate the Ethernet connection? Or another way to do it?

Thanks for your tima and help!

In addition to the other reply - how often is your internal DNS server going
down? This should not be a common occurrence -

 

[TheDragon]

if it is, you need to get it looked at. DNS is the number 1 service to keep
running smoothly in Windows OS. Without it nothing runs.

 

[=?ISO-8859-1?Q?Ren=E9?=]

Thanks for the other answer! I will try it.

In addition to the other reply - how often is your internal DNS server going
down? This should not be a common occurrence -

The local DNS is on a Linux box. The box starts up a little bit slower
then the WIN2K workstation. Apparently at start up WIN2K checks the DNS
that are available and registers the first in row that works. The first
in row is the local DNS the rest are remote DNS. I did this that I can
browse the Internet without the local DNS, when in the weekends Linux
box is turned off, for instance.

When I turn on the WIN2K too early it will register one of the remote
DNS that won't know my local domains of cause. The only way I know to
register DNS is to disable and re-enable the network connection. You
know a better way?

 

[Lanwench [MVP - Exchange]]

Thanks for the other answer! I will try it.

The local DNS is on a Linux box. The box starts up a little bit slower
then the WIN2K workstation. Apparently at start up WIN2K checks the
DNS that are available and registers the first in row that works. The
first in row is the local DNS the rest are remote DNS. I did this
that I can browse the Internet without the local DNS, when in the
weekends Linux box is turned off, for instance.

When I turn on the WIN2K too early it will register one of the remote
DNS that won't know my local domains of cause. The only way I know to
register DNS is to disable and re-enable the network connection. You
know a better way?

Are you using Active Directory? And why is the DNS server being turned off
on weekends? Even without AD, you should specify only your internal DNS
server in any client/server's IP config, and that DNS server should be set
up with forwarders to your ISP's DNS servers (and/or use root hints).

 

[=?ISO-8859-1?Q?Ren=E9?=]

Are you using Active Directory?

I don't know what AD is.

And why is the DNS server being turned off
on weekends?

Simply to save energy and noise. It is a mixed home/office situation and
often I just I go on-line sporadicly because I work the whole week with
it already. When we do it, the remote DNS makes it unnecessary to start
up the local DNS. The main reasoon for the local DNS was to have several
local websites, for developement reasons.

Even without AD, you should specify only your internal DNS
server in any client/server's IP config, and that DNS server should be set
up with forwarders to your ISP's DNS servers (and/or use root hints).

The forwarders are set up and during office hours I enjoy the faster
response of the local DNS. Also when new internet domains are
registered, they almost instantly become available (not all domains
though).

 

[TheDragon]

Thanks for the other answer! I will try it.

The local DNS is on a Linux box. The box starts up a little bit slower
then the WIN2K workstation. Apparently at start up WIN2K checks the DNS
that are available and registers the first in row that works. The first in
row is the local DNS the rest are remote DNS. I did this that I can browse
the Internet without the local DNS, when in the weekends Linux box is
turned off, for instance.

When I turn on the WIN2K too early it will register one of the remote DNS
that won't know my local domains of cause. The only way I know to register
DNS is to disable and re-enable the network connection. You know a better
way?

You could set the primary DNS server to your internal one, which mush have
either forwarders set or be using the 12 root hints on the internet.
Then set the secondary to your ISP. So when the internal one is not
available it will fail to respond, and the client will use the secondary.