Background Replication busted

Have a WinXP client w/R6.0.2 which can not do any background replication. I can access any files on the server no problem, can create new replicas and can do a “foreground” replication on any database, can use TCPIP trace utility. Connection document is set to TCPIP only with 15 sec timeout.

HOWEVER, any time I try to do background replication of any NSF (including sending of outgoing mail!), I immediatly get error. From Log:

Network: Available Ports: TCPIP

Network: Checking normal priority connection documents only…

Network: Local network connection document found for ser/ve/r

Verifying address ‘10.177.25.100’ for ser/ve/r on TCPIP

 Unable to connect to ser/ve/r on TCPIP (The server is not responding. The server may be down or you may be experiencing network problems. Contact your system administrator if this problem persists.)

Network: Server ser/ve/r is not responding


(note “ser/ve/r” listed in above appears as proper fully qualified server, edited in this post for security reasons)


Are there hidden settings for replication connection document used for BACKGROUND replication?

Any thoughts greatly appreciated!

THANKS IN ADVANCE!!

Subject: Background Replication busted

I have exactly the same environment (XP and 6.0.2CF1 clients) and I had a remote user with this same problem. When Notes first started a replication event completed successfully but subsequently when you tried replicating it would just state “background replication submitted” but nothing would happen.I fixed it by closing Notes and deleting the cache6.ndk.

Hope this helps.

Subject: Background Replication busted

Hi Ted,

I am also using background replication, only few clients are corrupting in XP, but otherwise replication is ok, i am fully dependent on the background replication. Infact I feel R6 replication engine is better than previous version.