If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Sadly the hostnames for the boxes I am trying to replicate are similar:

- db1.nyc.mydomain.tld
- db1.sac.mydomain.tld

The servers can talk to each other over all necessary ports however when I generate a push subscription from the publisher, I am asked to add the SQL Server subscriber and it already shows DB1 listed since itself is DB1.nyc. How can I attach the remote subscriber when setting up the subscription from the publisher if the hostname conflicts in my unique scenario?

Yes, I am aware this naming convention is "bad practice".

I created a entry on the publishers host file to use db2sac for the SAC IP and entering that alias in as the remote subscriber but no dice.

When you look a the distributor's allowed subscribers, does sac show up?

No, sadly in the drop down menu the SAC hostname of SQL Server in Sacramento is not visible. I really wouldn't expect it to be either. I was told I need to create an alias for the SAC host inside SQL Server to circumvent this issue (when two servers in replication have identical hostnames but a unique sub-domain.