Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Replication / December 2007

Tip: Looking for answers? Try searching our database.

Synchronizer question

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Don Udel (ETC) - 06 Dec 2007 18:18 GMT
We have a server behind the firewall.  We use the Cisco DSL modem to NAT the
fixed address to the internal address.  In other words, an external request
to address of xxx.xxx.44.82 gets converted to 10.0.0.24.  The synchronizer
was set up with the xxx.xxx.44.82 address. Things have been working fine for
several years now.

Syncing on the internal LAN does not work.  The thought was that the
xxx.xxx.44.82 request would head out (since it was not an internal address,
get turned at the router and come back to 10.0.0.24.  However this does not
work.  Cisco admits a problem with NAT.  I would like to have the replicas
sync to the hub on the replica farm using the internal LAN (vs dialup).

Can I have two synchronizers running at the same time.  One handling
requests for xxx.xxx.44.82 and the other handling requests for 10.0.0.24?

Surely this situation has been dealt with before.  Is there a better answer?

TIA

Don
David W. Fenton - 06 Dec 2007 23:26 GMT
"Don Udel \(ETC\)" <donudel@ellijay.com> wrote in
news:OA5KeRDOIHA.4688@TK2MSFTNGP06.phx.gbl:

> We have a server behind the firewall.  We use the Cisco DSL modem
> to NAT the fixed address to the internal address.  In other words,
[quoted text clipped - 15 lines]
> Surely this situation has been dealt with before.  Is there a
> better answer?

Don't use Internet replication?

That's the only answer I know of, and it's definitely one of the
reasons I don't use Internet replication, i.e., because it can't do
host resolution, which makes it unsuitable for any situation where
the IP address can change, or might be different in different
network contexts.

Signature

David W. Fenton                  http://www.dfenton.com/
usenet at dfenton dot com    http://www.dfenton.com/DFA/

 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.