Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a Windows Server 2008 R2 running remote desktop for me to connect to from my Windows 7 laptop when I am out of the office.

So when I am at home, I can log into the server using remote desktop via the IP address of the server just fine.

Now when I take my laptop to the office, on the server's local network, it won't let me connect via IP, like it used to. It will connect perfectly fine using the machine name, however.

This just started happening on Friday - I connected to the server Friday morning via IP from the local network. A few hours later, it would no longer accept connections via IP address, even though I had changed nothing!

share|improve this question
Sounds like the DHCP lease expired, give it a static IP on your local network. – Not Kyle stop stalking me Jun 5 '12 at 2:35
up vote 1 down vote accepted

The problem seemed to resolve its self after a recent Windows Update. I don't know which update it was that fixed it and I still don't know what the issue(s) was/were.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.