Server Fault is a question and answer site for system and network administrators. 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 Windows Server 2008 r2 with static ip address on WAN interface. I connecting to the server from home from my laptop. Laptop at home is behind nat box. When i connecting to the server from home in Remote Desktop Session Manager i see in client status dialog a local ip address of client behind the nat box not WAN ip address of nat box. I suppose i must see the WAN ip address of the nat box in Remote Desktop Session Manager, isnt it?

share|improve this question

closed as not a real question by Chopper3, Brent Pabst, rnxrx, HopelessN00b, Greg Askew Sep 26 '12 at 21:14

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

It's really not clear what you're asking here, but I'm guessing you're wondering why the client IP is showing your laptop's internal address and not your router's WAN address? Do you have a VPN tunnel between your home machine and the server? If so, there's your answer. – Chris McKeown Sep 26 '12 at 11:46

Your using the Remote Desktop Client on your home PC, so the values you see in RDS Manager (IP and hostname) are that of the computer running RDC, which is your internal IP and real computer name at home.

share|improve this answer
Correct, I was going to point out that you get the computer name as well. Fwiw the internal IP is much better, as when you have 25 users from the same external network on your server it's good info to have when troubleshooting with the other sites remote tech. – Mark Henderson Sep 26 '12 at 20:53
This is by design as Terminal Services was originally designed to allow a central system to be used from remote locations and was created for the corporate world, where we need to be able to identify the machine, not just the network. – John Gardeniers Sep 26 '12 at 21:48

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