Wireless Networks Thread, Set DNS Servers Automatically in Technical; We have had an issue on our network which was partly resovled last week: Some issues are still hanging around.
7th July 2008, 03:07 PM #1
Set DNS Servers Automatically
We have had an issue on our network which was partly resovled last week: Some issues are still hanging around.
I have found that by going to each station in turn and entering a preferred and alternate DNS server at the stations which still show issues it will mop up the majority of the remaining issues.
I don't fancy going round and setting this at each station where it is needed. Does anyone know of a way of automating this [as our DNS server does not seem to want to do it!]
7th July 2008, 03:11 PM #2
DHCP will set DNS properties.
7th July 2008, 03:14 PM #3
There is a little detail I left out in my original post. DHCP is not running on site here: It runs at another establishment [can't give any more detail]
Originally Posted by jcollings
7th July 2008, 03:24 PM #4
Can anyone say 'Recipe for disaster'?
Originally Posted by DaveP
7th July 2008, 03:28 PM #5
I can and I have been saying so for ages: Nobody listens. We are pushing ahead with further developments along these lines.
Originally Posted by Dos_Box
7th July 2008, 03:53 PM #6
Do you have working machine startup scripts? If so, add the appropriate "netsh" command to the script.
("appropriate" means I'm afraid I've not got time to google at the moment but google for netsh set dns and you'll find it ...)
If you don't have startup scripts and you don't have too many machines then you can use sysinternals psexec to run the netsh command on each remote machine - something like:
When you've got that done, bang heads until you get DHCP in place - life is just too short to run a network of more than a few machines without it :-)
psexec \\computer01 netsh set "local area connection" dns 10.0.0.1
Thanks to srochford from:
7th July 2008, 04:08 PM #7
Thanks for that it looks like a plan. I will give it a try tomorrow.
DHCP situation here is complicated: It is not that we do not run it but rather it is not in my hands. Can't give much more detail than that.
7th July 2008, 05:06 PM #8
OK; plan B:
bang heads until you get a properly working DHCP in place :-)
7th July 2008, 08:50 PM #9
Tried it! Bored with that idea now [not joking here!] It just isn't working. I am now in quiet compliance mode. When disaster strikes I can say 'I told you so' but by then I suppose 'they' won't remember.
Originally Posted by srochford
By the way this is not the only point I have raised issues on.
By GlennT in forum MIS Systems
Last Post: 1st April 2008, 09:16 AM
By techyphil in forum Windows
Last Post: 26th November 2007, 09:28 PM
By Quackers in forum Windows
Last Post: 18th October 2007, 02:43 PM
By TechSupp in forum How do you do....it?
Last Post: 12th April 2007, 12:05 PM
By Jamie_a in forum Windows
Last Post: 1st February 2007, 03:08 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)