You are using an out of date browser. It may not display this or other websites correctly. You should upgrade or use an alternative browser.
static address
About this tag
On WindowsForum.com, discussions about static addresses often involve troubleshooting network services after an IP change. One thread covers a Server 2012R2 RDS VM where moving to a new static address broke Remote Desktop Services, with errors from the Connection Broker. Another thread asks why Credentials Manager requires a target IP address for automatic logon, noting that static addresses simplify credential setup but are not mandatory if you manually enter credentials. These posts highlight that static addresses are commonly used for servers and network resources to ensure consistent connectivity, but changing them can disrupt dependent services like RDS or credential-based access.
I know, it's not the suggested way of doing things but it has worked for years. I have an 2012R2 Standard with RDS, and Domain Contoller all in one. It has worked for years. I changed ISP's, and moved it to a new static address, tried the original and have tried restoring several backups...
If I want to create a Windows Credential entry to allow automatic access to another machine on my local network (XP and W2K machines), it requires me to enter the target's IP address (as well as username/password). This is all well and good so long as I assign static addresses to those machines...
access issues
authentication
automatic access
computer name
credential manager
credential prompt
ip address
local network
network
network address
password
protocol
remote access
staticaddress
tech support
username
windows 2000
windows 7
windows issues
windows xp