Re: Ports and Replication in SQL Server 2000
From: José Araujo (josea_at_mcrinc.com)
Date: 02/08/05
- Next message: Gordon: "Log Shipping has failed - question of restarting"
- Previous message: Saeed Abd Al-Ati: "Re: Foreign Keys with Queued Transactional Replication"
- In reply to: vivek: "Ports and Replication in SQL Server 2000"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 8 Feb 2005 10:06:14 -0400
If you don't use FTP SQL will download the snapshot from the default folder
which is usually a shared folder (NETBIOS).
I don't know the ports you have to open to make that works... but you
certainly don't want to do that...
I think you should activate the FTP server in your internal network (ie:
using the VPN) and make the subscribers download the snapshots from there.
José.
"vivek" <vivek@discussions.microsoft.com> wrote in message
news:9F8EF204-2EB0-489C-AF3C-4D12B4BCEC59@microsoft.com...
> Hi,
> We are trying to configure sql server 2000 transactional replication
across
> 2 data centres through vpn and firewall. While port 1433 is open for sql
> server communication, it looks like the anonymous pull subscription uses a
> different port to download the initial snapshot files.
>
> We are not using FTP to download the snapshot files, bu the option to find
> the snapshot files in the default folder.
>
> We would like to know which port that the replication agent uses to
download
> the snapshot files to be opened? Can this port be configured to a fixed
> unused port and how? Is FTP the best way for this scenarion?
>
> Thanks for your help and time.
>
> Vivek
- Next message: Gordon: "Log Shipping has failed - question of restarting"
- Previous message: Saeed Abd Al-Ati: "Re: Foreign Keys with Queued Transactional Replication"
- In reply to: vivek: "Ports and Replication in SQL Server 2000"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|