RE: process could not connect to Distributor

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Not sure if the following will help, but let me try to clarify a few things:

1) Ftp support in SQL replication applies only to transfer of snapshot
files, movement of SQL changes would require a regular connection to SQL
server (Publisher and Distributor).
2) The Ftp* properties on the Merge\Distribution ActiveX control have
actually been deprecated in SQL2000, configuration of FTP snapshot support is
done at the publication level (right-click publication for properties). Once
that is confiigured, you will need to regenerate a new snapshot for the
settings to take effect. And when you start the merge control, all you need
to do is to specify a FileTransferType of FTP. In hind-sight, it was probably
a mistake not to take out the FTP* properties completely.
3) There is still the all important task of getting the merge activeX
control to establish a regular connection to SQL Server from an untrusted
domain in the first place. This typically means that either 1) to expose
whatever port that the distributor and publisher are listening on (default
SQL Server port is 1433) to the outside world (or accessible from the
laptops) and then use the Distributor|PublisherNetwork|Address properties to
point to the exposed IP address\port configuration, or 2) (recommended) to
configure VPN between the laptops and the Publisher\Distributor machines so
regular SQL Server connections can be established. If you decide to use the
VPN approach, there really is no need to configure FTP for the snapshot files
as regular UNC shares should be accessible by the laptops.

HTH

-Raymond



"Buzz" wrote:

> All that and it turns out it was a software firewall issue with XP on the
> subscriber laptop.
>
> However, now I am stuck with the next issue. Part of replicating over
> untrusted domains or the internet means I need to use FTP. On the subscribers
> I use the ActiveX merge module.
>
> I specify the FTP address:
>
> _merge.FileTransferType = FILE_TRANSFER_TYPE.FILETRANSFERFTP
> If Me.txtFtpAddress.Text.StartsWith("ftp://";) = False Then
> Me.txtFtpAddress.Text = "ftp://"; & Me.txtFtpAddress.Text
> End If
> Me.txtFtpAddress.Text = Me.txtFtpAddress.Text.Replace("\", "/")
> _merge.FTPAddress = Me.txtFtpAddress.Text
>
> But it keeps erroring out saying it cannot find the FTP location specified
> at the value I have for _merge.Publisher???
>
> The value for the Ftp is ftp://192.168.1.2/repldata.
>
> The value for the Publisher is server909.
>
> I put an LMHOSTS entry to route the 192.168.1.2 to server909 it works.
>
> But I'm not going to be doing LMHOSTS management on 500+ production laptops
> and we plan on using different FTP servers that are different than the SQL
> Server.
>
> "Sophie Guo [MSFT]" wrote:
>
> > Hello,
> >
> > Name resolution must be working between all machines involved in
> > replication. Otherwise, you may receive the error message.
> >
> > I suggest that you perform the following steps to narrow down the issue:
> >
> > * Drop the subcription and then drop the publication.
> >
> > * Setup name resolution both ways between the machines. There are several
> > options for achieving name resolution. You can use CNU aliases
> > (cliconfg.exe), hosts files, WINS, and/or DNS.
> >
> > * On the publisher reregister in publisher and subscriber in Enterprise
> > Manager by netbios name instead of by IP address.
> >
> > * On the remote server, register the publisher and the subscriber in
> > Enterprise Manager by netbios name (@@servername).
> >
> > * Recreate the publication and then recreate the subscription.
> >
> > * Run the Merge agent. Check the issue.
> >
> > The following information is for your reference:
> >
> > Potential causes of the "SQL Server does not exist or access denied" error
> > message
> > http://support.microsoft.com/?id=328306
> >
> > 324992 How to use replication with SQL Server 2000 Desktop Engine (MSDE
> > 2000)
> > http://support.microsoft.com/?id=324992
> >
> > I hope the information is helpful.
> >
> > Sophie Guo
> > Microsoft Online Partner Support
> >
> > Get Secure! - www.microsoft.com/security
> >
> > =====================================================
> > When responding to posts, please "Reply to Group" via your newsreader so
> > that others may learn and benefit from your issue.
> > =====================================================
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> >
> >
> >
> >
.

Relevant Pages

  • Re: Is there any problem by running both ftp and Http in the same Machine
    ... SQL best practices in general. ... > The problem associated with me is that, our client wants to remove our ftp ... They actually changed the Http server and the FTP ... > Servers is using System Administrator as the database user. ...
    (microsoft.public.windows.server.security)
  • Re: Is there any problem by running both ftp and Http in the same Machine
    ... We use the FTP to simply Upload the new pages. ... First Both FTP and HTTP were ... on the same server, so we can test our pages without any help from there. ... > SQL best practices in general. ...
    (microsoft.public.windows.server.security)
  • Re: Editing Web Pages
    ... I did use an FTP to upload the pages after editing which was ... upload the files to the server. ... Some folks with Publisher 2003 and 2007 use a ftp to get their websites up ...
    (microsoft.public.publisher.webdesign)
  • Re: FTPing and Calling an EXE from a SQL Statement
    ... But first I need to encrypt the SQL Server backup file and then ... FTP it up to our secure FTP server... ... >> FTP a file from within a SQL Statement and also to run an .EXE from ...
    (microsoft.public.sqlserver.programming)
  • Re: Editing Web Pages
    ... I'm a Publisher 2000 user which after creating the webpages a ftp is used to ... upload the files to the server. ... Double-click the folder where you want to save the file. ...
    (microsoft.public.publisher.webdesign)