Try some basic connectivity tests.
- Verify that 5022, 5023 and 5024 are listening.
- Verify that the server name you are using is correct.
From the command line :
netstat -an
On my server, you can see that 5022 is listening.
Next make sure that you can connect to those ports via telnet
telnet fully-qualified-server-name 5022
As it mentions in the Note section of the Mirroring Properties GUI, just below the witness field, the server names have to be fully qualified tcp addresses.
You should just see a black screen. In this example I chose a name that would cause a connection failure. If you see "Could not open connection", then the server(s) defined as mirror, principal and witness aren't reachable or you are not using the right name.
The telnet client can be added under Features in Windows 2008.
In Windows 2008, when you right click on Computer, you can see the full computer name.
You should be able to ping it as well from the command line. ex: ping myservername
Update
Please run the following queries on each SQL Server instance and put the results in your question. Many of these troubleshooting tips come from: http://msdn.microsoft.com/en-us/library/ms189127.aspx
Show tcp endpoints
SELECT type_desc, port FROM sys.tcp_endpoints;
Display status of mirroring endpoints
SELECT state_desc FROM sys.database_mirroring_endpoints;
Check that the ROLE is correct
SELECT role FROM sys.database_mirroring_endpoints;
Display permissions to endpoints
SELECT EP.name, SP.STATE,
CONVERT(nvarchar(38), suser_name(SP.grantor_principal_id))
AS GRANTOR,
SP.TYPE AS PERMISSION,
CONVERT(nvarchar(46),suser_name(SP.grantee_principal_id))
AS GRANTEE
FROM sys.server_permissions SP , sys.endpoints EP
WHERE SP.major_id = EP.endpoint_id
ORDER BY Permission,grantor, grantee;
GO
The login for the service account from the other server instance requires CONNECT permission. Make sure that the login from the other server has CONNECT permission. To determine who has CONNECT permission for an endpoint, on each server instance use the following Transact-SQL statement.
Example output:
name STATE GRANTOR PERMISSION GRANTEE
TSQL Local Machine G sqladmin CO public
TSQL Named Pipes G sqladmin CO public
TSQL Default TCP G sqladmin CO public
TSQL Default VIA G sqladmin CO public
Mirroring G SERVERNAME\Grantor CO SERVERNAME\Grantee
Grantor is the account that assigned (CO) connect permission, Grantee is the account that has connect permission
From the command line run ipconfig /all and note what Host Name returns.
Best Answer
It's a little bit strange to have log file bigger than data file. I guess you didn't take a backup for long time and that is a reason for such a huge log file.
First try with this link: http://social.msdn.microsoft.com/Forums/sqlserver/en-US/633ea08c-942d-4703-bc03-f2befd35f612/log-file-size-keeps-growing-replication?forum=sqlreplication
The simplest solution is log backup, log backup should reduce the size of file.
If that fails you can try to truncate log file (see dbcc command). However, you should use this as a last resort since truncation of log file is "quick and dirty" solution.