Thanks Glenn. Of course, now I have the issue of dealing with a bunch of NT machines, and apparently netsh doesn't work right in NT unless I were to (possibly) update and re-register some dlls. I don't know what side effects that would have, and I'm not going to find out on 400 workstations. So, it looks like I'll have to script something for the NT machines. Arg. Thanks, Ray at work > -----Original Message----- > From: Sullivan, Glenn [mailto:GSullivan@xxxxxxxxxxxxxx] > > Netsh > > For example: > NetSH Interface IP set wins name="Local Area Connection" > source=static addr=192.168.1.1 NetSH Interface IP Set dns > name="Local Area Connection" source=static addr=192.168.1.1 > > Assuming your Interface is still named "Local Area Connection". > > Or, if you have more than one interface, parse the output of: > NetSH Interface Show Interface > > -----Original Message----- > From: Costanzo, Ray [mailto:rcostanzo@xxxxxxxxxxx] > > > Hi group, > > I'm wondering if anyone knows of a way to set a couple of > WINS and DNS entries on machines from the command prompt. I > know where these entries are stored in the registry, and I > could do it that way, but it's a PITA to enumerate through > dead NIC entries and what not and try to determine the > correct NIC. Is there a command line tool for such a thing? > I do not see anything in the reskit. > The information contained in this e-mail message is intended This weeks sponsor - RTOSoft TScale Complaints about applications response time - DO SOMETHING ABOUT IT! TScale 2.0 improves applications response time and increases terminal server capacity. Really get MORE from your existing servers! Free eval: http://www.rtosoft.com/enter.asp?id=131 ================================== To Unsubscribe, set digest or vacation mode or view archives use the below link. http://thethin.net/win2000list.cfm