SQL Server Forums
Profile | Register | Active Topics | Members | Search | Forum FAQ
 
Register Now and get your question answered!
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 SQL Server 2008 Forums
 SQL Server Administration (2008)
 Remote Connection Problem
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

Dennis Falls
Starting Member

USA
41 Posts

Posted - 04/22/2014 :  14:19:47  Show Profile  Reply with Quote
I am trying to make a remote connection between 2 2008 r2 servers. Because the University I work for blocks port 1433 I have the remote server listening on port 1434. I have created an alias on the client server for port 1434.

The only way I can make the connection is if I include the port # i.e. <server_name>,1434 or Admin:<server_name>. I have no idea where I found the suggestion to use the Admin: prefix, but it works.

Normally, this would not be a problem, but I am trying to setup a Mirror between these 2 servers. The setup get all the way to the Start Mirroring step when I receive "the server can not be reached or does not exist" error.

I'm not sure if this is causing the error, but if anyone else has experienced this, I would certainly appreciate any suggestions you might have.

tkizer
Almighty SQL Goddess

USA
36817 Posts

Posted - 04/22/2014 :  15:50:01  Show Profile  Visit tkizer's Homepage  Reply with Quote
Add a SQL alias to both machines that references the other machine+port. You can do this through the configuration manager utility or through regedit. I prefer regedit.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\ConnectTo (Create ConnectTo if it doesn't exist)
Create a String Value
Value name: RemoteServerName\InstanceName
Value data: RemoteServerNameOrIpAddress,PortNumber

For instance:
On Server1, create this string value:
Server2\InstanceA
Server2,1434

On Server2, create this string value:
Server1\InstanceZ
Server1,5555



Tara Kizer
SQL Server MVP since 2007
http://weblogs.sqlteam.com/tarad/
Go to Top of Page

tkizer
Almighty SQL Goddess

USA
36817 Posts

Posted - 04/22/2014 :  15:50:26  Show Profile  Visit tkizer's Homepage  Reply with Quote
Please note that the mirroring port will need to be open between the two servers.

Tara Kizer
SQL Server MVP since 2007
http://weblogs.sqlteam.com/tarad/
Go to Top of Page

Dennis Falls
Starting Member

USA
41 Posts

Posted - 04/25/2014 :  10:39:37  Show Profile  Reply with Quote
Ok, I had to wait for a time when I could take production offline but I finally made this setup. I set both servers to listen on port 1434 and created an alias on both servers. This made no difference in the connection properties. I still have to add the port number, <server_name>,1434 or Admin:<server_name>. Any other ideas? Am I wrong in assuming that I should be able to connect to a remote server without using the port number?
Go to Top of Page

tkizer
Almighty SQL Goddess

USA
36817 Posts

Posted - 04/25/2014 :  16:59:29  Show Profile  Visit tkizer's Homepage  Reply with Quote
You are not wrong. You definitely should be able to connect without using the port number, especially if you added the SQL alias. Try adding the SQL alias to the Wow6432Node section of the registry too. If the client is 32-bit but the OS is 64-bit, then you need the SQL alias in both locations.

By the way, I'd highly recommend not using 1434. 1433 and 1434 are often blocked, and 1434 is supposed to be used for the SQL Browser service. Use a 5 digit port number instead, anywhere under 64000. We use ports in the 20000-40000 range.

Tara Kizer
SQL Server MVP since 2007
http://weblogs.sqlteam.com/tarad/
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.03 seconds. Powered By: Snitz Forums 2000