"Jørn Jørgensen" <jorn@hotmail.com> wrote in message
news:eSLjTCKAGHA.1312@TK2MSFTNGP09.phx.gbl...
> Hi,
>
> We have two SQL Servers, both running 2005, located in separate domains in
> different physical networks connected by VPN. The servers can "see" each
> other at IP address level and can resolve FQDN's correctly.
>
> The servers are named like this:
> abcserver.domain1.local
> abcserver.corporate.net
>
> Note that both servers share the same node name, abcserver.
>
> We are able to create publications at both abcserver SQL Servers, but when
> we try to create a subscriber at either end it fails with the error below
> when trying to connect to the 'other' e-site server:
> 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, 'ABCSERVER'. (Replication.Utilities)
>
>
>
> The error is the same regardless of whether IP address or Fully Qualified
> Domain Name is used to point to the other server. Of course, if we use
> just 'abcserver', we connect to the localhost.
>
>
>
> Assuming the issue was related to the name being "passed" from the
> subscribing server to the publishing server not matching the "internal"
> name of the publishing server, we have tried changing the "internal"
> server name in both SQL Servers to match the FQDN's. We have also created
> the replication services using scripts to have full control to make sure
> the server name is identical etc. All this to no avail - same error.
>
>
>
> We have created a test environment consisting of "abcserver.domain1.local"
> and another server running SQL Server. These are in different domains, but
> on the same subnet and can "see" each other directly (ie. NetBIOS).
> Replication between these two works without a hitch when we use the
> NetBIOS names. We have tried both directions. At the same time, it is not
> possible to get it working if we use IP address or FQDN.
>
>
>
> We have also tried adding 'abcserver' (just the NetBIOS name) to the hosts
> file to try and trick 'abcserver.domain1.local' into thinking 'abcserver'
> means 'abcserver.corporate.net', but turns out the server was too smart
> for us:-)
>
>
>
>
> So, we are running out of ideas. ANY feedback on this would be very
> helpful.
>
>
>
> Thanks in advance!
>
>
>
> Jørn
>