asked
SQL server is replicating to wrong subscriber.
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
The port, in this case, has nothing to do with the issue. Check your publication and verify the subscriber at the publication. Also, check to see if there is an alias setup at the publisher SQL Server pointing at your Server B with the name of your Server C or the IP addresses may be wrong. Port 1433 is the standard port that SQL Server listens on.
i checked the both publication and subscription settings and they all look good to me. I also checked the IP address in the Host file , which happens to be the global (external ) IP address assigned to us by our ISP. i noticed in the host file, both server B and C are pointing to the same global IP assigned to us by our ISP.I'm wondering if somehow our network admin reserved the global IP for server B, hence, constraining data flow destined for server C to go to only server B.... Thanks folks for your help on this one...
19 People are following this question.
