jismay Posted March 15, 2004 Report Share Posted March 15, 2004 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. Link to comment Share on other sites More sharing options...
Guest psykoyiko Posted March 16, 2004 Report Share Posted March 16, 2004 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? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.