We are planning multiple remote sites, each running 5 XP Pro or XP Embedded
which will logon to a Windows Server 2003 machine at Head Office via a WAN.
Each XP machine in the site will be replicating its single db to the 4
others via Merge Replication. We will also be using MSMQ 3 for
communication between 2 computers in any site.
I am unsure of how replication (and MSMQ) affects the 10 connections limit
of XP Pro. In replication, would there only be 1 incoming connection on
each machine? (i.e. The Publisher)
I bump into this limit all the time when running pro. The short answer is
you need to bypass this by using SQL Authentication and use a pull
subscription with FTP.
You may have to disable MSMQ, reboot, then ensure that the first thing you
do when you come up is download the snapshot. Then start up MSMQ.
After the snapshot is deployed you shouldn't have to use NT authentication
any more. You should be good from there.
"Chris" <chris.spamhater@.ihatespam.co.uk> wrote in message
news:OSXzqUPXEHA.1764@.TK2MSFTNGP10.phx.gbl...
> We are planning multiple remote sites, each running 5 XP Pro or XP
Embedded
> which will logon to a Windows Server 2003 machine at Head Office via a
WAN.
> Each XP machine in the site will be replicating its single db to the 4
> others via Merge Replication. We will also be using MSMQ 3 for
> communication between 2 computers in any site.
> I am unsure of how replication (and MSMQ) affects the 10 connections limit
> of XP Pro. In replication, would there only be 1 incoming connection on
> each machine? (i.e. The Publisher)
>
>
No comments:
Post a Comment