SQL Server 2005 Database Mirror Error

Question

When I try to configure SQL Server 2005 mirroring on my servers, the following error occurs. I start two Win2K3 servers with SQL 2005 on each of them, one of which works with the version of SQL 2000. After restoring the database using NORecoveryand configuring the endpoints, I run the following error when I try to start a mirroring session.

TITLE: Database Properties
------------------------------

An error occurred while starting mirroring.

------------------------------
ADDITIONAL INFORMATION:

Alter failed for Database 'TestDB'.  (Microsoft.SqlServer.Smo)

------------------------------

An exception occurred while executing a Transact-SQL statement or 
batch. (Microsoft.SqlServer.ConnectionInfo)

------------------------------

The server network address "TCP://S-01.ssl.local:5022" can not be reached 
or does not exist. Check the network address name 
and that the ports for the local and remote endpoints are operational. 
(Microsoft SQL Server, Error: 1418)

I also want to note that I can telnet to a port using the full name from both servers.

Update

The secondary server starts SQL Server 2005 as a named instance on local 1434 and over the network as 1433 on IP addresses that match the FQDN used.

[EDIT]

I was able to Telnet to connect to port 5022 on both servers.

[DECISION]

, , , , SQL Server, . , . , .

Answer 1

, , , , SQL Server, . , . , .

Answer 2

telnet 5022 ? , , SQL- 1433/1434.

SQL Server .

, :

http://blogs.msdn.com/grahamk/archive/2008/12/08/database-mirroring-error-1418-troubleshooter.aspx

Answer 3

SQL , SQL Server 5022, .

, TCP- - ?

Answer 4

, , , SQL Profiler, , ?

, Profiler, ( SQL 2000, 2005 ).

Answer 5

, SQL Server 2008, Windows 7 ( ),

:

:

1) SQL Server.

2) → → SQL Server 2005 → TCP/IP. , SQL SERVER 1433.

, , .

3) → → SQL Server 2005 → TCP/IP.

: Pinal Dave (http://blog.SQLAuthority.com)

and then this: http://www.youtube.com/watch?v=VHAUtCiN1M4 the witch basically goes to SQL Server Configuration Manager, and for each instance set your local user and password.

Just my two cents, because it seems that every solution is not suitable for everyone ... and once I lost the opportunity to understand this