Thanks for replying to my posting, Simon.

After racking my brains trying to fix the issue, I decided to open a
support case with Microsoft. The solution was fairly simple. I erred by
searching for a solution to an SQL server 2005 issue rather than SQL
Server issue. According to Microsoft engineer that assisted me and
totally new to me, Microsoft does not support DNS resolution when
replicating thus using an alias to a subscriber in a non trusted domain
prevents replication from occurring. This came as a total surprise to
me specially since I manage over 80 replications and all with the
exception of this one connects by using and alias and using DNS
resolution. Anyway, he directed me to place a record for my subscriber
in the hosts file and that did the trick. Learn something new everyday.

Thank you,

Pete Ocasio
Senior Software Developer

MS Sql Server LazyDBA home page