Domino Server & VPN

0 pts.
Tags:
Availability
Bandwidth
Lotus Domino
Microsoft Exchange
Network management software
Network monitoring
Network protocols
Networking
Platform Issues
TCP
Tech support
Hello, I have this problem: environment: 2 Domino 6.5.1 in Head Office (one for mail, the other for applications), a Domino 5.0.7a in remote office (in a different country). The connection to this country is based on VPN over internet; problems: 1)sometime the home router "hangs" and the mail was not delivered to the remote server; 2)frequently the scheduled replications to remote host do not work, with error "remote system no longer responding"; in both cases I can ping the remote host and the "trace" command from the domino console return the correct IP... the VPN is "home made", and for connection to task other than Domino (ERP for example) works well; There is perhaps some problem using VPN for Domino server to server connections? For the other Domino system using WAN, replication and router work... Thnak You in advance, Maurizio
ASKED: March 17, 2006  5:16 AM
UPDATED: March 17, 2006  1:04 PM

Answer Wiki

Thanks. We'll let you know when a new response is added.

Any chance the connection is slow enough to cause the servers to think they’ve lost the connection? VPNs have a good deal of overhead and it could be an “operation did not complete in time” sort of thing.

Discuss This Question: 4  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Mauriz14
    Thank You for the reply! Ok, but Domino cannot restore a lost connection? The replications are scheduled every five minutes, if one have failed, I expect that the next one works, but often this does not happen for many times... moreover, the problem is restricted to the head office... in the remote system all works... Some bad or missing configuration? Regards, Maurizio
    0 pointsBadges:
    report
  • 131313
    Create a connection doc, that will be use to replica and send email to this server. Before doing this, make sure you can ping the remote server. Then, create the connection document, set the mail routing to one, meaning, your server will send email to the remote server if there is one message pending in the queue. Set the replication to something like 30, 60 or 90 minutes. In the connection doc your will have, SourceServer, Destination, Domain, Schedule, Timeout, IP address for the Destination server, replication setting, and mail routing setting. hope this help.
    0 pointsBadges:
    report
  • Mauriz14
    Thank you for reply, I have connection doc, indeed the problem occurs occasionally for routing and more frequently for scheduled replications; please note that manual replication and replication from server console always works... Regards, Maurizio
    0 pointsBadges:
    report
  • 131313
    If manual replication always work, then, instead of using the dns name for the server, use the server ip address. I hope this is a static ip address. A lot of time this happen because the server can't resolve the dns name. Using the IP address should improve things....
    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following