February 4, 2009 at 2:21 pm
I am trying to set up merge replication between a remote server and distributed SQL Express databases. When I try to setup the local subscription I get the error "SQL Server replication requires the actual server name to make a connection to the server. Connections through a server alias, IP address, or any other alternate name are not supported. Specify the actual server name (which it supplies for me and is correct). The problem is if I just put in that name it can not find the remote server. Do I need a VPN or is there another way around this issue?
February 4, 2009 at 2:41 pm
First error message is that you have to register the name of the server when connecting. (Not using . or [local] )
Second, check and see if the Port 1433 is open in the firewall for the remote network where the remote server is situated. SQL uses port 1433 to communicate. If you want to use the SQL GUI (SSMS) to connect then UDP port 1444 has to be opened as well.
VPN makes it safer and secure. I would recommend a VPN connection between the two servers.
-Roy
February 4, 2009 at 4:30 pm
Roy,
The server is registered and I can connect to it. I still get the message when the connection to find the publisher is made. Attached is a view of my server and object explorers.
Thanks. (Image removed)
February 9, 2009 at 12:26 pm
Maria,
You *MUST* use the exact server name that pops up on it when you run
SELECT @@servername
* Noel
February 10, 2009 at 2:38 pm
It's important to note that if you CANT, for some reason; need to resolve with FQDN, etc then you can work around this with an LMHosts or Hosts entry.
We have a situation where there is no DNS between some of our subscribers and our publisher. We had to us Host file entries to make this work.
February 11, 2009 at 7:58 am
Noel,
I already WAS trying to use the server name but I could not connect with that, only with the IP or web address.
Brian - you get the award for the week! I setup a LMHosts entry with my offsite server IP and viola! I was able to connect to my server directly by name. Finishing up the replication setup should be a snap from here. Many thanks!!!
For those of you with the same problem, I cannot find the source I used for this information again, but all I did was use the sample LMHOSTS file called LMHOSTS.SAM to get guidelines for the entry. This is in the C:\WINDOWS\system32\drivers\etc directory. I edited this file with notepad and saved it with the name LMHOSTS - then - this is important - removed the .TXT extension as the OS expects only the name LMHOSTS (no extension).
Maria
February 11, 2009 at 10:07 am
Glad you solved.
What I meant is that you needed to somehow (like above using LMHOSTS or SQL Server ALIASES) have direct connectivity.
It is very nice of you to share the solution 🙂
* Noel
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply