Windows 2008 Incoming Connection: Where/How is Server IPv4 address defined
Posted
by
revelate
on Server Fault
See other posts from Server Fault
or by revelate
Published on 2010-12-20T22:32:24Z
Indexed on
2010/12/21
6:55 UTC
Read the original article
Hit count: 411
We're evaluating a VM hosted externally which runs Windows Server 2008 R2 Web Server Edition and wish to access it via a VPN connection for maintenance and administration.
RRAS isn't included in Web Server Edition, but it does have a form of VPN server called "Incoming Connections". This appears to work well and even supports multiple simultaneous connections. As we'll be using this VPN regularly we'd like to know if this is a viable solution or if we'd be better off upgrading to Standard Edition and full-fledged RRAS.
In particular we're accessing the VM via the Private IP given by the Incoming Connection (currently 169.254.135.207) so we'd like know:
- if the server private IP might change every so often?
- if so is there any way to define it manually?
- or should we be using the server name rather than the private IP address?
- if so how can we be sure that it will resolve correctly?
- Name resolution over the "Incoming Connection" has worked on and off during our tests.
- if so how can we be sure that it will resolve correctly?
Thanks for your help
© Server Fault or respective owner
