We have an intensley-used Windows 2003 R2 SP2 Enterprise/SQL Server 2005 SP3 two-node cluster. The server's IP is going to change (moving to a new subnet). I know there is code and configuration pointing to the cluster IP address and the sql IP address and not the DNS name. Is there any way to identify those sources? One way I've done this in the past is to create a route on the switches with the old IP, pointed it at both nodes, then put loopbacks on the nodes. DNS is changed to the new IP on the box. I then monitor connections. Anything connecting to the old IP, I can easily capture on the switches. An idea I had would be similar to just add another SQL IP in Cluster Administrator and do similar monitoring as my first suggestion. I would move the DNS name to the new IP. Does anyone have a less cludgy, less latency-adding solution? I guess I'd be interested in any ideas though. The operating premise is to proceed sanely and identify all IP-based connections (and then change them to using DNS).