shutdown.exe or shutdown -i

[Incognitotj]

Where I work we have about 150 computers in six rooms. I've infrequently used the shutdown -i command from a prompt. This allows me to browse AD for the computers in a specific room (we name them by room and tag number).

After the Christmas break, several of the computers were having problems. The AVG server was reporting that they didn't have the latest defs. A check of the computers showed them to be current, but the server couldn't see that. Checking IP's showed the server looking for a different IP than the computer had. If it had just been a few minutes, I wouldn't have questioned it. However the computers had been on for several hours at this point and the network should have had the IP's straight by then.

Back to shutdown -i. While doing a shutdown -i, the same exact computers failed. A short time later, the AVG server showed the correct IP's and a test shutdown -i worked on all but two that still didn't have the correct IP's.

I am trying to understand exactly how does shutdown -i works. I realize that when I choose browse and select computers by the name field, that I am actually querying AD. After that I am not sure how the computer name translates into an IP. Is it through Netbios or WINS (which I don't think we are using), DNS, or my guess through an ARP request.

A clue is that the AVG server is also having the problem, but I think that it is just because the use the same method of finding the IP's.

Thanks for any help,

Terry

[SeanC]

Since the query is through AD, I would think it uses DNS to resolve the IPs. From what I recall of AD, if a computer is listed in AD it needs to be in the DNS table. I could be wrong since I haven't used AD for almost 6 months now.

[Incognitotj]

It is incorrect in the DNS table. By pinging the computer name, I get an ip of 192.168.1.126 (and of course 100% packet loss). IPconfig shows the current IP of 192.168.1.40. I am trying to avoid flushing the DNS, but it probably will come down to that. We removed the computer from the network and AD, but when we put it back on the network, it still shows the .126 address in the DNS table. First we are going to try ghosting the computer again. If that doesn't work, we will either change the entry in the table or flush the DNS.

Thanks Sean,

Terry