I have a publication which is intended to push data to a subscriber over the internet from a remote server to our onsite local subscriber but it ends up on a wrong subscriber.Here is the scenario:
Server A is a remote server hosted in south Dakota ( Publisher)
Server B is a local server ( Virtual Box) subscriber
Server C is also a local server on a virtual box ( subscriber)
Both server B and C listens on port 1433
What I'm trying to do is to replicate a table from server A to server C but replication is pushing the data to server B
Is replication pushing the table to server A because both server B and C listens on port 1433 or Am I missing something else. Any contributions or pointers will be appreciated... Thanks folks