Link to home
Start Free TrialLog in
Avatar of pmoon77
pmoon77

asked on

> ftp: connect :Unknown error number

ftp xx.xxx.xxx.xxx 21

when I ftp to default 21, it works ok.  When I ftp xx.xxx.xxx.xxx 25, it gives me the above connection error.

I'm working on an xp and win95.  Both machines give the same error message.  There are other machines at work that can dial in ok to port 25.

the default ftp server is sco, port 25 is a win2000 machine.  I can telnet to sco and then ftp to port 25 with no problem.  But I would like to be able to ftp directly to 25 just like some of other machines.  Is there anything I need to do on the sco box??? Thanks
Avatar of jlevie
jlevie

This sounds like either a problem with your non-standard FTP server on the w2k machine or with the ftp client S/W. I'd bet on it being the FTP client you are trying to use and you might try a different FTP client program on your XP or w95 box.
FTP uses two connections, redirecting only one port will lead you to big problems
Avatar of pmoon77

ASKER

ftp client works on other machines comming in.  Redirection and other FTP Client programs have not solved the problem.  I still think it's the way the ftp server is set up.  I have seen some comments from other postings but can't follow the instructions.
Sendmail is common program running on port 25/tcp, it is accessed by Mail User Agent programs like Eudora or Outlook, and not FTP.
Avatar of pmoon77

ASKER

gheist:  

You'll get all the points if you lead me thru this since this is the first mentioning that I can understand.  On port 25 of the ftp server or port 25 of the client?  And how do I disable or determine if port 25 is interfering with my ftp'ing.
ASKER CERTIFIED SOLUTION
Avatar of gheist
gheist
Flag of Belgium image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
FTP basically has two modes of operation - Active and Passive
Both have a common "Control connection" to 21/tcp of the server.

In active mode client issues PORT address.port to server, and listens for connection on that port, server then connects to that port on client , from either 20/tcp or high ports.

In passive mode client issues PASV command and server responds with one port it opens for client (usually high port), client connects here and this is now data connection.

You see - there are no bound ports on client machines, only on server.

If not obvious - Passive mode is more firewall-friendly.
Avatar of pmoon77

ASKER

gheist:

 both your comments went over my head.  Please walk me thru this.  The server has port 25 as SMTP.  However, I don't under how some connection is able to be made to access W2k machine and I can't from my my machine.  Do you know anything about hosts.allow?
You do not forward data connection correctly. There might be no way.

Please give error messages from CuteFTP, WS_FTP_LE or Far Manager of Windows or lftp or ncftp on UNIX or lookalikes...try passive mode too, default ftp is very silent about problems.

I imagine you have ftp service on unix at port 21 and you have windows firewall forwarding port 25 to unix port 21 or something like that - please explain to me if I am wrong.
I know that file, hosts.allow is irreleavant ....
Avatar of pmoon77

ASKER

gheist:

ERROR:>      Can't connect
ERROR:>      Can't log in. Disconnecting...
STATUS:>      Disconnect: Monday 08:09:03 01-05-2004

this is from cuteFTP.  Pretty criptic...
I ftp in xx.xxx.xxx.xxx 25 ---
From that client what happens if you try 'telnet xx.xxx.xxx.xxx 25'? Do you get an FTP server banner?
"Can't connect" - you have incomplete tcp forwarding feature on your firewall that is all.
use tcpdump and ethereal to find out.