Does that mean that you get the same results even if you use the index?  

I can't speak for the 'softies but if you want to report it as a bug, you
either open a case direct off the support pages, else you go through your
support rep.  An organization your size/stature, likely has a TAM of some
sort right?  That would be a fair way to submit a bug.

Bugs usually result in no-charge service.  But I would highly suggest that
you verify that it doesn't work with the index option added prior else it
*might* work and you'd have a bug to file that would have an expected
workaround. 

http://support.microsoft.com/?LN=en-us&scid=fh%3Ben-us%3Bofferprophone&x=12&;
y=4



-----Original Message-----
From: [EMAIL PROTECTED]
To: [email protected]
Cc: [email protected]; [EMAIL PROTECTED]
Sent: 1/6/2005 9:29 AM
Subject: RE: [ActiveDir] Bizarre NETSH Behavior - Startup Script on XP

Hi Al

Any idea how to report it as a bug?  I was kind of hoping Microsoft guys
would be monitoring this discussion group and one of them would look
into
it / address it internally.

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]


|---------+---------------------------------->
|         |           "Mulnick, Al"          |
|         |           <[EMAIL PROTECTED]>|
|         |           Sent by:               |
|         |           [EMAIL PROTECTED]|
|         |           tivedir.org            |
|         |                                  |
|         |                                  |
|         |           01/05/2005 02:03 PM EST|
|         |           Please respond to      |
|         |           ActiveDir              |
|---------+---------------------------------->
 
>-----------------------------------------------------------------------
-------------------------------------------------------|
  |
|
  |       To:       [email protected]
|
  |       cc:       (bcc: James Day/Contractor/NPS)
|
  |       Subject:  RE: [ActiveDir] Bizarre NETSH Behavior - Startup
Script on XP                                                |
 
>-----------------------------------------------------------------------
-------------------------------------------------------|




I haven't seen that and it's not what I would expect.  I would have
expected
a failure instead or replacing the WINS entry.

Do you get the same results if you do use an index?

add dns [name=]InterfaceName [addr=] DNSAddress [[index=]DNSIndex]

It's not listed as 'required' but seems that you should be able to
specify
a
location for the target.

Might be worth it to report it as a bug.

Al

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Wednesday, January 05, 2005 1:40 PM
To: [email protected]
Subject: [ActiveDir] Bizarre NETSH Behavior - Startup Script on XP

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/
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/


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/
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/

Reply via email to