UNIX for Advanced & Expert Users

network: 90.90.12.0/24
Bad SCO: 90.90.12.3
good SCO: 90.90.12.199

No internal router. "In a nutshell" no network architecture has really been defined. Just assigned each PC and host with it's own static ip with a default gateway address of
90.90.12.200.

All units connect to a switch which connects to firewalls trusted interface.

While using cuteftp from XP box with address of 90.90.12.2, I ftp to the address of 90.90.12.3 on 21 with username and password
Cute shows me Socket Connected, Waiting for welcome message.

This is where it stalls and times out.

If you need any more info I can provide more detail.

Additional notes:
While ftp is uncommented in the inetd.conf file like the other services, when executing "ps -Af" there is no trace of ftpd.

On bad sco, try
ftp localhost
to see if ftp is running at all.

Try
netstat -an
you want an entry like: *.21 LISTEN
to prove that it;s listening on port 21 for an ftp connection.

When the XP thinks it's connected, look for the connection.
netstat -an
and look for something like:
90.90.12.3.21 90.90.12.2.X
see what state the socket is in. If the socket does not exist, power off the bad sco and retry the experiment. Does the xp still connect? If so some other box has the same ip address as the bad sco.