Consider the following scenario:
- You have a database mirroring session in Microsoft SQL Server 2005.
- The database mirroring session does not have a witness.
- You set up a witness server.
- On the principal server and on the witness server, you do not use DNS together with DHCP for name resolution. Instead, you specify that a host file should be used for name resolution.
- On the principal server instance, you try to set the witness.
Msg 1456, Level 16, State 3, Line 1
The ALTER DATABASE command could not be sent to the remote server instance 'TCP://ServerName:port'. The database mirroring configuration was not changed. Verify that the server is connected, and try again.
To work around this problem, follow these steps:
The ALTER DATABASE command could not be sent to the remote server instance 'TCP://ServerName:port'. The database mirroring configuration was not changed. Verify that the server is connected, and try again.
To work around this problem, follow these steps:
- On the DNS server, register all the internal IP addresses.
- On the principal server, click Start, and then click Control Panel.
- In Control Panel, double-click Network Connections.
- Right-click the connection that you use to connect to the witness server, and then click Properties.
- Under This connection uses the following items in the Connection Properties dialog box, click Internet Protocol (TCP/IP), and then click Properties.
- In the Internet Protocol (TCP/IP) Properties dialog box, click Advanced.
- In the Advanced TCP/IP Settings dialog box, click the DNS tab.
- On the DNS tab, click Append these DNS suffixes (in order), and then click Add.
- Under Domain suffix in the TCP/IP Domain Suffix dialog box, type the domain suffix, and then click Add.
- Click OK three times.
Comments