Hi All I was wondering if anybody else has ever seen this. We were at a location a few days ago that uses static ip addressing. Initially they had 1 DNS server and 2 WINS servers for their NT domain. We migrated them all to our WIN2K3 Forest and rather then set up DHCP we used the startup script to change the DNS servers. WINS was being left as it already was setup as we are considering a WINS redesign right now.
The initial configuration (made up ips) DNS 65.65.108.5 WINS 1 65.65.10.5 WINS2 65.65.10.6 We used netsh commands to change the addressing. netsh interface ip set dns "local area connection" static 65.65.150.2 netsh interface ip add dns "local area connection" 65.65.150.4 When we checked the ip configuration on the machines after the startup script ran we had the following: DNS 65.65.150.2 WINS1 65.65.10.5 WINS2 65.65.150.4 For some reason the secondary DNS entry was overwriting the secondary WINS instead. When we put in a line in the startup script to manipulate WINS netsh interface ip set wins "local area connection" starti 65.65.10.5 We got the expected results (1 Wins server and the 2 DNS servers we had specified). Has anybody else seen this behavior? Is this a bug in the NETSH command or something else. We tested this on 5 different machines, both running the script via. startup script and manually running it with admin credentials with the same results. Regards; James R. Day Active Directory Core Team Office of the Chief Information Officer National Park Service (202) 354-1464 (direct) (202) 371-1549 (fax) [EMAIL PROTECTED] List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
