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
"Don Udel \(ETC\)" 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, > 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? 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. -- David W. Fenton http://www.dfenton.com/ usenet at dfenton dot com http://www.dfenton.com/DFA/
