Of course I have 3 options but only 2 fit my situation. I'm clarifying what they are since I was on the site:
Merge replication - Merge replication, like transactional replication, typically starts with a snapshot of the publication database objects and data. Subsequent data changes and schema modifications made at the Publisher and Subscribers are tracked with triggers. The Subscriber synchronizes with the Publisher when connected to the network and exchanges all rows that have changed between the Publisher and Subscriber since the last time synchronization occurred.
Snapshot replication - Snapshot replication distributes data exactly as it appears at a specific moment in time and does not monitor for updates to the data. When synchronization occurs, the entire snapshot is generated and sent to Subscribers.
Now to the heart of the issue:
I copied the following from here.
Different types of replication over the Internet have different
security levels. Additionally, when transferring replication files
using FTP sites, precautions must be taken to secure the site and
still make it accessible to replication agents.
Virtual Private Network
Using a Virtual Private Network (VPN) is the most secure option for
implementing replication over the Internet. VPNs include client
software so that computers connect over the Internet (or in special
cases, even an intranet) to software in a dedicated computer or a
server. Optionally, encryption at both ends as well as user
authentication methods keep data safe. The VPN connection over the
Internet logically operates as a Wide Area Network (WAN) link between
A VPN connects the components of one network over another network.
This is achieved by allowing the user to tunnel through the Internet
or another public network (using a protocol such as Microsoft
Point-to-Point Tunneling Protocol (PPTP) available with the Microsoft®
Windows NT® version 4.0 or Microsoft Windows® 2000 operating system,
or Layer Two Tunneling Protocol (L2TP) available with the Windows 2000
operating system). This process provides the same security and
features previously available only in a private network.
To sum it up, I need to use to be on the same domain, a VPN, or IIS to publish. SQL Server will not publish directly from Sql Server to Sql Server unless it is on the same domain.