Re: Replication over a firewall

From: Jack Lee (jack_at_tek-files.com)
Date: 10/07/04


Date: 7 Oct 2004 15:21:09 -0700

Thanks for taking the time to answer. I'm actually using eVC 3.0 and
not the CF, it's an older application that was shelved because of the
problem, now we are trying to figure it out again. Is the 3.0
replication code more probmatic than 4.0?

when you say "make sure the snapshot folder name is the default
name..." are you suggesting that a file structure such a "c:\snapshot"
for a publication named "MyDB" should be "c:\MyDB"? In the properties
i set the location to be "\\MY_SVR\C$\snapshot"

item 2, i'll double check but i beleive it is a user account.

item 3, IIS and SQL are on the same machine, so there is no delegation
and i use the parameters for sql authentication.

Since it works inside the firewall, i think items 1,2 and 3 are ok.
I only found a few articles in the newsgroups, 3 of them mentioned
they had norton's firewall and that caused the problem, it was somehow
stripping some of the data from the messages for no good reason. We
are not using Norton but maybe what we are using is somehow based on
the same engine Norton uses.

The person in charge of the firewall said they block inbound requests
on port 80 and 1433 (SSL). Is inbound required?

thanks
Jack

"Darren Shaffer" <darrens@nospam.com> wrote in message news:<#YolO5CrEHA.452@TK2MSFTNGP09.phx.gbl>...
> That's very good news. It means your CF app should also be able to get to
> the publication
> using the same credentials. Double check the parameters you are passing
> with your
> SqlCeReplication object according to:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfsystemdatasqlservercesqlcereplicationclasstopic.asp
>
> If you are effectively setting the exact same values for:
>
> repl.InternetUrl = "<http://jackspath/sqlce/sscesa20.dll>";
> repl.InternetLogin = "<username>";
> repl.InternetPassword = "<password>";
>
> that you just used from Pocket IE, then that means there is something about
> the publication you
> created which resolves fine when inside the firewall, but cannot be resolved
> from outside.
>
> Some troubleshooting advice:
>
> 1. make sure the snapshot folder name is the default name that SQL Server
> suggested when
> you indicated that this publication could be used for merge - merge will
> only work with that default
> name
>
> 2. make sure you're running sql server and sql server agent under an acount
> other than localsystem.
>
> 3. check users and permissions for the InternetLogin parameter above - you
> know you can get to IIS
> and sscesa20.dll but can that be delegated through to Sql Server and the
> tables you are trying to replicate?
>
> We'll figure this out, merge replication just has a lot of points of failure
> to eliminate.
>
> -Darren
>
>
>
> "Jack Lee" <jack@tek-files.com> wrote in message
> news:31cf38f6.0410052232.5a14360a@posting.google.com...
> > navigating to sscesa20.dll works fine in pocket IE. i get prompted for
> > authentication, after i log in, the standard "SQL Server CE Server
> > Agent" message is displayed.
> >
> > jack
> >
> > "Darren Shaffer" <darrens@nospam.com> wrote in message
> > news:<eFmaemyqEHA.3416@TK2MSFTNGP15.phx.gbl>...
> >> Jack,
> >>
> >> From your device, go to Pocket IE and enter the URL to the virtual
> >> directory
> >> containing sscesa20.dll on your IIS server. If you cannot successfully
> >> get
> >> the response,
> >> merge replication will not work either because of firewall issues or some
> >> other
> >> routing/configuration issue.
> >>
> >> -Darren
> >>
> >>
> >> "Jack Lee" <jack@tek-files.com> wrote in message
> >> news:31cf38f6.0410051252.57ab54d@posting.google.com...
> >> > Does Sql Server Ce replication over IIS require the inbound port on
> >> > the firewall to be open in addition to the outbound?
> >> >
> >> > It works fine when i'm on the WAN, but when i try it outside the WAN,
> >> > i get an error
> >> > Error Number: 80072F76
> >> > Native Number: 28035
> >> > Error Description: Header information is either corrupted or missing.
> >> >
> >> > The only difference is a firewall and server proxy. The logs have
> >> > nothing interesting in them. So i can only think that it is the
> >> > firewall and i do not have control over it, so i can not simply open
> >> > the inbound to test it. Can i assume the
> >> > CEMerge->put_InternetProxyServer is for the client side and not the
> >> > server's proxy settings?
> >> >
> >> > thanks
> >> > Jack



Relevant Pages

  • Re: Replication Monitor didnt work because different collations
    ... Looking for a SQL Server replication book? ... SQL 2005 filtered merge replication. ... We changed collations to match the server collation and Replication ... After this change we started all publication snapshots. ...
    (microsoft.public.sqlserver.replication)
  • Re: Passing SQL data from one server to another
    ... Will your ISP open up post 1433 for inbound traffic on the firewall? ... Replication will work best if you can get around this firewall issue. ... Looking for a SQL Server replication book? ...
    (microsoft.public.sqlserver.replication)
  • RE: Error creating new push subscription after deleting the existi
    ... To drop a push subscription to all articles for a transactional ... At the Publisher, open SQL Server Enterprise Manager, expand a server ... group, expand the Replication folder, expand the Publications folder, click ... the publication that has the subscription you want to delete, ...
    (microsoft.public.sqlserver.replication)
  • When do we need to delete/recreate a subscription?
    ... I'm using SQL Server for Merge replication and I looking for a list of ... Deleting a sub. ... when modifying a publication table's structure (like ...
    (microsoft.public.sqlserver.replication)
  • HELP: Dropped table column causes sp_addmergearticle to fail with replication
    ... I'm setting up merge replication on sql server 2000 sp3. ... there is no identity column in this table ... The article 'tkDPLRS' could not be added to the publication 'TEST1'. ...
    (microsoft.public.sqlserver.replication)

Loading