Jump to content
Sign in to follow this  
jismay

IPsec related communications problems.

Recommended Posts

Ever since I implemented IPsec between my linux client machine and the Windows 2000 backup machine I have had major communications problems when talking to the retrospect client on the linux side. I am getting messages such as:

Mar 15 09:20:21 foobar Retrospect[21317]: PmcOpen: connect() failed with error 110

Mar 15 09:23:30 foobar Retrospect[21317]: PmcOpen: connect() failed with error 110

Mar 15 09:26:40 foobar Retrospect[21317]: PmcOpen: connect() failed with error 110

Mar 15 09:29:49 foobar Retrospect[21317]: PmcOpen: connect() failed with error 110

Mar 15 09:32:59 foobar Retrospect[21317]: PmcOpen: connect() failed with error 110

Mar 15 09:36:18 foobar Retrospect[21317]: PmcOpen: connect() failed with error 110

Mar 15 09:39:27 foobar Retrospect[21317]: PmcOpen: connect() failed with error 110

 

I am also getting errors in dmesg:

 

sending pkt_too_big (len[1500] pmtu[1293]) to self

sending pkt_too_big (len[1500] pmtu[1293]) to self

 

I am suspecting that there are some sort of MTU related issues going on here, but I am fresh out of things to try. General communications to and from the linux machine are fine, including SSH, HTTP, CVS. It is on retrospect that seems to be having troubles.

Share this post


Link to post
Share on other sites
Guest psykoyiko

strange, it looks like connect() is timing out (according to errno.h). Is this happening when you try and open the client GUI on the Linux machine, or when you try and connect from the Windows machine?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×