I have configured Remote Desktop IP Virtualization with static ip adresses in the registry.
All works fine. When I log in, I get the IP address i specified in the registry.
The appliciation that we use connects based on IP address. But now we have 2 ip adresses:
The IP address of Remote Desktop Services Server and the virtual IP address from the registry.
The application is not working now.
When I type ipconfig /all, i see the IP address of Remote Desktop Services Server is the "Preferred" one and the one from the registry is the "Deprecated".
I think when the virtual ip address can be changed to the "Preferred" one, the application is going to work.
So can I change the Preferred IP address to the Deprecated IP address? Or just disable the "Preferred" IP address, so there is only the virtual IP address?
Remote Desktop Services Team Blog: http://blogs.msdn.com/b/rds
- Proposed as answer by Silvia Doomra [MSFT]Moderator Monday, August 23, 2010 7:19 PM
We had the same issue not that long ago trying to activate the virtual ip option into our Windows 2008 R2 environment.
First we noticed that within our RDP sessions we did not get any virtual ip address. Afer a few tests we found out that the Forefront TMG client blocked this for some reason, maybe because it sits deep into the IP stack. We de-installed the program and now we did get a virtual ip address back as described in all the articles that are written.
The only strange thing that happened that one of our Windows 2008 R2 servers changed its prefered address in DNS to its depricated IP within the time as described within DNS. The other servers where also virtual ip was activated did not had these problems. What we did then was manually removing the server from DNS and registrated the server again into DNS.
For now everything seems to be working just fine as mentioned in the articles.