Binding the RDP listeners to localhost can also be a cheap way to enable multiple concurrent sessions stemming from a single console session.
I'm guessing you want the localhost functionality, not strictly wanting 127.0.0.1. I'm also guessing that you don't want to expose the adapter to the network.
If you're still wanting to do this, I can think of the below method:
- Install a local loopback network adapter. (See here.)
- Configure the RDP Listener to bind only on the loopback network adapter. In Server2K8 and higher, this will be possible via the tsconfig.msc snap-in. I've never tried in Server2k3 but that should be a similar procedure. (I can go in more details about the configuring the registry if needed.)
From there, you'll be able to RDP to the loopback adapter using its link-local address.