Re: Question about SCP stalling over VPN

[Matthew Case <mattcase@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>]

First and foremost, thank you to everyone for your responses. I checked 
the MTU on both sides and it's currently 1500 so I'm assuming it's not a 
mismatch. My VPN is a pair of old Netscreen 5xp boxes, and I can't find 
anything relating to MTU or packet size in the configuration, but I'm 
still looking.

Secondly, to answer your question John, There is no persistent 
connection between the servers. I could feasibly set up an NFS share 
between the two but I have a sneaking suspicion that if the problem is 
some sort of packet mangling by the VPN during file transfers, the 
actual mechanism used to transfer the file will be irrelevant.  However, 
I will set this up and test it and report back my results, most likely 
next Monday.

On 3/12/2010 3:41 AM, John Morrison wrote:
> Matt,
>
> If you are using ssh do you need to use scp as well? Or is just plain copy ok?
>
> On 10 March 2010 03:04, Darren Tucker<dtucker@xxxxxxxxxx>  wrote:
>    
> > Matthew Case wrote:
> > [...]
> >      
> > > I've looked high and low and haven't really come up with anything
> > > definitive. Someone somewhere had mentioned fiddling with MTU settings, but
> > > I'm not really sure what that will accomplish as I am unfamiliar with what
> > > MTU is and does. If this question has been answered previously, I apologize
> > > ahead of time. Thanks!
> > >        
> > This does sound like the MTU problem to which you refer.  See
> > http://www.snailbook.com/faq/mtu-mismatch.auto.html for details.
> >
> > --
> > Darren Tucker (dtucker at zip.com.au)
> > GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4  37C9 C982 80C7 8FF4 FA69
> >     Good judgement comes with experience. Unfortunately, the experience
> > usually comes from bad judgement.
> >
> >      
>
>
>    

--

Matthew Case
Specialized Business Software
Software Engineer
SCJP 5 Certified
Phone: 440-542-9145
Fax: 440-542-9143




This message and any files transmitted with it may contain information that is privileged, confidential, and exempt from disclosure under applicable law.   They are intended solely for the use of the intended recipient.   If you are not the intended recipient, distributing, copying, disclosing, or reliance on the contents of this communication is strictly prohibited.   If this has reached you in error, kindly destroy this message and notify the sender immediately.   Thank you for your assistance.

We attempt to sweep harmful content (e.g. viruses) from e-mail and attachments, however we cannot guarantee their safety and can accept no liability for any resulting damage.   The recipient is responsible to verify the safety of this message and any attachments before accepting them.