🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Thread View: comp.os.linux.networking
2 messages
2 total messages Started by Steve Wyles Thu, 04 May 1995 00:00
FTP error - 426 Data Connection: Broken pipe.
#604
Author: Steve Wyles
Date: Thu, 04 May 1995 00:00
53 lines
3156 bytes
Hi Guys,
	Earlier today I was attempting to transfer some files via FTP 
from a local machine attached via ethernet to my Linux box and came 
across a little glitch. Basically I'm receiving a 426 Data Connection: 
Broken pipe response to the transfer and the file is truncated to 65439 
bytes!!!!!!!.
	
	 Also in recent months I've noticed a broken pipe message when I've
been un-taring compressed archives with 'tar xvfz...' is this a related
problem and an anybody shed some light as to what might be causing it? 

	However if I do an FTP from the console of a file in my home 
directory all is fine, so something is definately a little fishy.

	The machine I'm connecting from is running Windows for Workgroups,
using the Microsoft tcp stack and FTP client, the session log is below. 

Additional info:-

	Latest kernel (1.2.8) 
	Everything else from Slackware 2.0.1 (CDROM free with Oct 94, PCPLUS)

ftp> open g6vju                                                 
Connected to g6vju.DEMON.CO.UK.                                     
220 g6vju FTP server (Linux g6vju 1.2.8 #1 Thu May 4 09:28:10 BST 1995 i386)
 ready. 
User (g6vju.DEMON.CO.UK:(none)): ftp                                  
331 Guest login ok, send e-mail address as password. 
Password:                                              
230 Guest login ok, access restrictions apply.             
ftp> lcd f:\winword6                                 
Local directory now F:\WINWORD6                        
ftp> ascii                                           
200 Type set to A.                                     
ftp> hash on                                                    
Hash mark printing On (2048 bytes/hash mark).             
ftp> cd incoming                                            
250 CWD command successful.                                  
ftp> put laser1.txt                                             
200 PORT command successful.                                          
150 Opening ASCII mode data connection for LASER1.TXT.                   
######################                                                     
426 Data Connection: Broken pipe.                                          
88276 bytes sent in 1.09 seconds (80.99 Kbytes/sec)                      
ftp> 

Regards,
	Steve
-- 
(=====)-----------------------------------------------------(=====)
 | / |       Steve Wyles             steve@g6vju.demon.co.uk | \ |
 | / | Bracknell, Berkshire, UK         +44 (0)1344 423102   | \ |
[_____]-----------------------------------------------------[_____]
Re: FTP error - 426 Data Connection: Broken pipe.
#605
Author: Paul Civati
Date: Fri, 05 May 1995 00:00
24 lines
1708 bytes
In article <D82Enr.tC@g6vju.demon.co.uk>
           steve@g6vju.demon.co.uk "Steve Wyles" writes:

>         Earlier today I was attempting to transfer some files via FTP 
> from a local machine attached via ethernet to my Linux box and came 
> across a little glitch. Basically I'm receiving a 426 Data Connection: 
> Broken pipe response to the transfer and the file is truncated to 65439 
> bytes!!!!!!!.

I've had this before, and it's commonly caused by running out of disk space
on the machine you are trying to ftp the file to.

>          Also in recent months I've noticed a broken pipe message when I've
> been un-taring compressed archives with 'tar xvfz...' is this a related
> problem and an anybody shed some light as to what might be causing it? 

Don't know about this one sorry, could be the same thing, don't know..

-Paul-

-- 
Paul Civati, paul@xciv.demon.co.uk  FYI it's 'sivarty' ;-)  Civ on IRC
Computer nut looking for internet/unix/PC network support/admin job.
"Don't worry Mr B, I have a cunning plan."
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads