I have a remote Windows 2012R2 server that runs a lot of important stuff. I, stupidly, accidentally, did an ipconfig /release on that server from the other side of the continent. Now that server no longer has an IP address and I have no way of accessing it. There is nobody nearby with physical access.
I have full access to literally everything on that network, but I can not figure out any way to have it refresh its IP address or reboot. I have admin access to:
- the DNS server
- the DHCP server
- the AD DC server
- the router
- guest Hyper-V machines that are still running on that server
- other random workstations on the domain
- the MAC address of the server in question
The only thing I don't have is a remote power switch to reset the damned server. I'm travelling for a month and I desperately need this server up, but I seem to have screwed myself so hard with this that there is no recovery. Does anyone have any ideas of any way to force this thing to renew its IP address or reboot?
This question has been marked as a duplicate, but it really is not. The other question is about steps to prevent situations like the one I am in to happen. But my question is, once I have lost contact with my remote machine, is there anything that can be done, given the considerable amount of information I have about the LAN of the remote machine? Is there for instance a generalization of a magic packet technology which can restart a machine, or something similar?
In other words: given that I am already stuck, is waiting my only option?
UPDATE: turns out that the ipconfig /release only released the IPv4 address, but it still had an IPv6 address. Once I found that from looking through the router logs, I was able to reboot it using that and the shutdown -r -m \\IPv6Address command.
EDITOR'S NOTE (Scott): Note that this solution (and the others suggested in the comments below) is irrelevant and not applicable to the question of which this one is allegedly a duplicate.
