#: 19852 S1/General Interest
    31-Mar-94  10:06:06
Sb: #FTP problems
Fm: roy harrell 72520,1636
To: ALL

        We have a tcp/ip network consisting of a Force CPU30 box running OS9
2.4, an OS2 box running 2.1 and an HP Integra system running SCOUs Xenix. In
addition, we periodically attempt to tie into a LANtastic network of seven
pcUs, one of which has ArtisoftUs tcp/ip package. When separate both the tcp/ip
and LANtastic nets appear to work ok. When connected, things may run smooth for
a week or so with ftp and telnet services working properly across the various
platforms. Eventually however, sparks will fly, packet collisions detected on
the LANtastic net go through the roof and our periodic, background ftp tasks
originating on the Force hang during execution even though you can successfully
ftp in the foreground from the OS9 shell.


        We are prepared to sever the LANtastic connection in order to restore
network integrity which will, in most likelihood, eliminate our OS9 ftp
problems. Regardless, I would like a better understanding of the problem. Our
ftp tasks are periodically initiated from a C program with a system call
similar to the following:


#define FTP_TRANS R/dd/internet/ftp_tranpsS

I

I

I

                system(FTP_TRANPS);


The ftp_tranps file contains the following:


ftp -nv -/dd/internet/output.ftp >>-


The tcpscript1 file contains the following:


open hphost

user opus meadow

lcd /dd/internet

append produxion.new

bye



When the system is working properly the data are transferred, the errors.ftp
file is null, and output.ftp contains the following:


Not connected.

Mode: stream       Type: ascii        Form: non-print    Structure: file

Verbose: on        Bell: off          Prompting: on      Globbing: on

Hash mark printing: off               Use of PORT commands: on

ftp> Connected to hphost.

220 hphost.UUCP FTP server (Version 5.52 #6 Mon Feb 5 16:28:10 CST 1990) ready.

ftp> 331 Password required for opus.

230 User opus logged in.

ftp> Local directory now /h0/USERS/INTERNET

ftp> 200 PORT command successful.

150 Opening ASCII mode data connection for duxion.new.

226 Transfer complete.

71 bytes sent in 0.03 seconds (2.31 Kbytes/s)

ftp> 221 Goodbye.


When the ftp task hangs the output.ftp file remains open and contains:


Not connected.

Mode: stream       Type: ascii        Form: non-print    Structure: file

Verbose: on        Bell: off          Prompting: on      Globbing: on

Hash mark printing: off               Use of PORT commands: on

ftp> Connected to hphost.

220 hphost.UUCP FTP server (Version 5.52 #6 Mon Feb 5 16:28:10 CST 1990) ready.

ftp> 331 Password required for opus.





The Error #000:003 message originates after I C to break out of the list
output.ftp command. The procs list entry for the ftp task is:


Id PId Aging   F$calls I$calls Last      Read Written Module & I/O

22  21   250         7      47 SetStt     309     498 ftp dd >>dd


or, more typically,


Id PId Aging   F$calls I$calls Last      Read Written Module & I/O

22  20   250         5      17 Read       128     341 ftp dd >>dd


It is interesting that, by killing this ftp task, our data is transferred and
the system runs normally until this happens again.



IUd appreciate if someone could explain whatUs going on here. One last note,
the IP addresses all begin with 127 (eg, 127.1.1.1, 127.1.1.2 and 127.1.1.3).
Could this be part of the problem?



Thanks,


Roy Harrell


There is 1 Reply.