remote computer shutdown

[Force Flow]

I have a windows 2003 server where I'm using acronis snap deploy 2.0 to deploy images to a lab of workstations. The workstations and server are in the same domain. All the workstations use the same active directory login.

when deploying the image from acronis, the option to change the SID is selected, as well as changing each computer's name.

When the deployment is finished, the computer names show up in active directory as expected (elabpc-01, elabpc-02, etc)

When I try to shut down the computers remotely using the "shutdown -i" command, I can select the computer names, but when I run it, I get this error message for all the computer names:

elabpc-01: the entered computer name is not valid. check the name and then try again or contact your system administrator (53)


Any ideas as to what the problem could be? Did the SIDs not actually change? Is there a problem using multiple logins of the same user?

Thanks

[Force Flow]

Some new info...

SP2's firewall is turned off

If I try to connect with remote desktop using the computer name, I can't connect. If I use the IP address instead, I can.

I can't ping the computer name, but I can ping the IP address.

[EzyStvy]

Did you try the shutdown command with the IP? It should work.

[Force Flow]

yeah, that worked.

I shouldn't have to resort to that, though (DHCP is enabled on the network, so IPs will most certainly change)


I went ahead and set up a WINS server on the 2003 server to see if that helped. It didn't seem to.

[Force Flow]

ok, it looks like there's definitely a name resolution issue.

I cleared the records in the DHCP and DNS servers and rebooted 3 workstations. When they came back up, I was able to contact 2 of the 3 using their computer names.



[edit]: I removed the WINS server, as it really isn't necessary.

[eidt2]: I cleared the DNS and DHCP entries for the workstations, rebooted the workstations, and this time only 1 of the 3 could be contacted via the computer name.

[Force Flow]

Figured this out.

Yes, I did need a WINS server set up.

I needed to either punch a hole in the windows firewall or turn it off all together. I just turned it off since the workstations are behind a NAT firewall anyway.