Re: netsh
- From: "Herb Martin" <news@xxxxxxxxxxxxxx>
- Date: Wed, 13 Apr 2005 16:34:11 -0500
"charleh (moif)" <charleh@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3c4g6sF6lrp11U1@xxxxxxxxxxxxxxxxx
> Hello,
>
> I have been given the task to disable DNS on a number of client machines.
> Currently, due to the servers remote location, I am remoting in via
> PCAnywhere and browsing the network via Network Neighbourhood. We aren't
on
> AD, just basic peer to peer and the server acting as a file server.
> What I don't want to do (only as a last resort) is login to each client
via
> PCA individually as Admin and change the settings manually as this causes
> downtime. I have been researching netsh and it appears that I can connect
to
> a client from the server and change the DNS settings that way.
SysInternals.com provides the free PSTools which
include PSExec and PSService etc and these can
be placed into a batch file which perhaps could loop
through the (filtered) output of Net View (which is
roughly equivalent to your Net Neighborhood method
although both are incomplete in the general case.)
> Is this the case and if so, what is the correct syntax? Given that the
> client machine name is L123 and we want DNS settings of either 0.0.0.0 or
> 127.0.0.1
So you don't want the machines to be able to RESOLVE
DNS names for themselves?
Easiest way to get NetSh syntax is to use the DUMP feature
then pull in and edit/use the output for exec'ing a file back in.
You do realize this is not true security? (IP addresses
or even Hosts file could still work locally on each machine.)
Changing the Default Gateway would be closer, but even
that might not do what you really want.
netsh inter ip set dns name="Local Area Connection" static addr=192.168.x.y
[Local Area Connection = your actual connection name]
OR are you talking about DNS Server?
One wonders why someone would bother with such a
fruitless task (in an unmanaged environment) since
there is no harm to anything except perhaps that server
by having the DNS server running....
It will not be used unless some clients are configured
to use it, and then presumably they NEED it.
.
- References:
- netsh
- From: charleh \(moif\)
- netsh
- Prev by Date: Re: Installing "File and Printer Sharing" remotely
- Next by Date: Re: SP1 Breaks Perl and Python
- Previous by thread: Re: netsh
- Next by thread: post WINS migration
- Index(es):
Relevant Pages
|
