Post reply

Duplicate computer name problem for merge replication with central publisher

  • June 9, 2015 at 10:13 am

    #297595

    Central publisher/distributor is on a cloud provider. Some customer servers are named just SERVER

  • June 9, 2015 at 10:49 am

    #1804039

    jsullivan 18251 (6/9/2015)

    Central publisher/distributor is on a cloud provider. Some customer servers are named just SERVER

    Quick question, can you share some more details?

    😎

    Edit: typo

  • June 9, 2015 at 11:35 am

    #1804061

    Sorry. It's my first post here and I wanted to get to the point rather than be overly wordy.

    My distributor/publisher is an Amazon EC2 server running SQL Server 2012 Standard. It currently has about 15 publications and 40 subscribers. Some subscribers belong to my company, some to our customers. We use LogMeIn Hamachi (VPN) which provides us with static IP addresses in addition to encryption. Those addresses and server names are in the distributor's hosts file, and its name and IP are in the subscribers' hosts files. So with the correct SQL account and password, the SQL instances can communicate with one another even though they're not in the same domain.

    I found that for SQL replication to work, the DNS (hosts) name must match the actual server name that's running SQL. I have 3 customers who have named their server SERVER. If I add all three servers with their actual name and IP addresses to the hosts file, the disstributor won't know who's who. If I try to connect to the customer's SQL with a different name than the actual server name (e.g. SERVER2 25.1.1.2 and SERVER3 25.1.1.3) SQL yells at me for the names not matching. I tried using SQL aliases to no avail.

    The error is something like this.

    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, 'XXXXXXXXXXXX\XXXXXXXXXXXX'. (Replication.Utilities).

    This thread was started in the hopes that one of you wise DBAs knew of a workaround. I'm a long time sysadmin, but an accidental DBA .

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply