Merge replication on MSDE using VPN

I suspect your issue is that you don't have an alias, but
have a look at this article which should help:
http://support.microsoft.com/?id=321822
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Hi Paul,
Thanks for the reponse. I have created an alias for the msde at the server
and registered it in EM. I was still getting the same error so I enabled
output logging for the merge agent. Apon inspection of the log it indicated a
logintimeout error had occurred and suggested increase the timeout value. I
created a new profile for the merge agent extending both the logintimeout and
the querytimeout parameters. I stopped and started the merge agent and now
the log contains the following message ("Cannot generate SSPI context"). Just
to recap, I am trying to replicate a database using SQL 2k sp3 enterprise
(windows 2003 server) and msde 2k sp3 (xp professional) between two
non-trusted domains using a vpn.
Thanks Jeff
"Paul Ibison" wrote:

> I suspect your issue is that you don't have an alias, but
> have a look at this article which should help:
> http://support.microsoft.com/?id=321822
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Can you change to sql serurity if you don't have it
already. Also, change the jobs to be owned by sa. If the
VPN is set up correctly, I believe you should be able to
assign rights to the replication share for the sql server
agent of the pull job. In my case I used FTP but this
shouldn't be necessary. This error message has loads of
potential causes mostly connected with authentication
that you can find in Google. For my part, I have seen it
when the system clocks weren't synchronized at all
accurately.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

>--Original Message--
>Hi Paul,
> Thanks for the reponse. I have created an alias for the
msde at the server
>and registered it in EM. I was still getting the same
error so I enabled
>output logging for the merge agent. Apon inspection of
the log it indicated a
>logintimeout error had occurred and suggested increase
the timeout value. I
>created a new profile for the merge agent extending both
the logintimeout and
>the querytimeout parameters. I stopped and started the
merge agent and now
>the log contains the following message ("Cannot generate
SSPI context"). Just
>to recap, I am trying to replicate a database using SQL
2k sp3 enterprise
>(windows 2003 server) and msde 2k sp3 (xp professional)
between two[vbcol=seagreen]
>non-trusted domains using a vpn.
>Thanks Jeff
>"Paul Ibison" wrote:
but[vbcol=seagreen]
www.replicationanswers.com
>.
>
|||Hi Paul,
I set the SQL Server Agent service on both machines to run under a local
windows account with the same name and password and everything is working
fine now. Is there a preferred configuration for security purposes. Our SQL
Server Services have always run under a network account. I have read several
articles on how to make this work but, I would like to make sure I am paying
significant attention to security. If you know of a good source for
replication security let me know.
Thanks for all you help! Jeff
"Paul Ibison" wrote:

> Can you change to sql serurity if you don't have it
> already. Also, change the jobs to be owned by sa. If the
> VPN is set up correctly, I believe you should be able to
> assign rights to the replication share for the sql server
> agent of the pull job. In my case I used FTP but this
> shouldn't be necessary. This error message has loads of
> potential causes mostly connected with authentication
> that you can find in Google. For my part, I have seen it
> when the system clocks weren't synchronized at all
> accurately.
> HTH,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
>
> msde at the server
> error so I enabled
> the log it indicated a
> the timeout value. I
> the logintimeout and
> merge agent and now
> SSPI context"). Just
> 2k sp3 enterprise
> between two
> but
> www.replicationanswers.com
>
|||What you have set up is pass-through security. As you
say, normally between computers Active Directory users
are used, or Workgroup users.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Jeff,
I don't know what your deployment timeframe is but SQL 2005 has the ability
to perform synchronization over HTTPS. Is this something you would be
interested in trying?
Philip Vaughn
Program Manager
SQL Server Replication
This message is provided "AS IS" with no warranties, and confers no rights.
"Jeff Rowley" <JeffRowley@.discussions.microsoft.com> wrote in message
news:4C8310C5-AC8D-4FD9-8152-1BFCADE59A29@.microsoft.com...[vbcol=seagreen]
> Hi Paul,
> I set the SQL Server Agent service on both machines to run under a local
> windows account with the same name and password and everything is working
> fine now. Is there a preferred configuration for security purposes. Our
> SQL
> Server Services have always run under a network account. I have read
> several
> articles on how to make this work but, I would like to make sure I am
> paying
> significant attention to security. If you know of a good source for
> replication security let me know.
> Thanks for all you help! Jeff
> "Paul Ibison" wrote: