Problems with ftp

<newbie alert>
I have a problem connecting to and issuing commands at a ftp-server.'
The ftp server is Windows based and requires active ftp. I have a
linux pc with Fedora (FC1).
PS: If I do the same ftp-command in DOS from a Windows XP box
on the same LAN and connect to the same server I have no problems.

I can log in without problems, but at the instant I try to issue a command
I get error messages and it hangs. Here is a log of what happens (ip-
address replaced by aaa.bbb.ccc.ddd):
===
[mylocalusername@dhcppc1 ~]$ ftp -d www.mysite.com
Connected to www.mysite.com (aaa.bbb.ccc.ddd).
220 iis11 Microsoft FTP Service (Version 4.0).
Name (www.mysite.com:mylocalusername): myusernameatftpserver
---> USER myusernameatftpserver
331 Password required for myusernameatftpserver.
Password:
---> PASS XXXX
230-Welcome to blablabla
230 User myusernameatftpserver logged in.
---> SYST
215 Windows_NT version 4.0
Remote system type is Windows_NT.
ftp> ls
ftp: setsockopt (ignored): Permission denied
---> PASV
227 Entering Passive Mode (aaa,bbb,ccc,ddd,9,202).

[program hangs and must be CTRL-C'ed]
===
A "nmap localhost" command at my Linux-box:

[mylocalusername@dhcppc1 ~]$ nmap localhost

Starting nmap 3.48 ( http://www.insecure.org/nmap/ ) at 2004-11-30 08:33 CET
Interesting ports on localhost.localdomain (127.0.0.1):
(The 1651 ports scanned but not shown below are in state: closed)
PORT STATE SERVICE
22/tcp open ssh
25/tcp open smtp
111/tcp open rpcbind
631/tcp open ipp
32770/tcp open sometimes-rpc3
32771/tcp open sometimes-rpc5

Nmap run completed -- 1 IP address (1 host up) scanned in 0.706 seconds
===

1) When I do for example "ls" it seems that the program forces PASV even if
I do
not specify this since I have been told that I need to use ACTIVE for
this server. Why does this happen?

2) What are the 9 and 202 after my IP-address in the
"Entering Passive Mode ..."-command?

Any clues what might be wrong? Any easy workarounds?

Borge
</newbie alert>

On 2004-11-30, B H <(E-Mail Removed)> wrote:
> The ftp server is Windows based and requires active ftp.
> ftp: setsockopt (ignored): Permission denied
> ---> PASV

Your client try to go in passive mode and it doesn't work. Tell him to
not use passive, since the server requires only active.

Davide

--
The BOFH's First Axiom: There are no inappropriate means for achieving
the goal of getting questions or silence.
Named by Mike Andrews, defined by Rebecca Ore

"Davide Bianchi" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) .net...
> On 2004-11-30, B H <(E-Mail Removed)> wrote:
> > The ftp server is Windows based and requires active ftp.
> > ftp: setsockopt (ignored): Permission denied
> > ---> PASV
>
> Your client try to go in passive mode and it doesn't work. Tell him to
> not use passive, since the server requires only active.

Does this mean that I have to force it to use ACTIVE? I do not issue
the PASV command. It seems to go into passive mode automatically
even if the server wants active.

So this means I should use "ftp -a" to force active?

Borge

On 2004-11-30, B H <(E-Mail Removed)> wrote:
> So this means I should use "ftp -a" to force active?

Yes.
Davide

--
I love the way Microsoft follows standards. In much the same manner that
fish follow migrating caribou.
--Paul Tomblin on alt.sysadmin.recovery

"Davide Bianchi" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) .net...
> On 2004-11-30, B H <(E-Mail Removed)> wrote:
> > So this means I should use "ftp -a" to force active?
>
> Yes.
> Davide

Ok. I'll try this. Thanks.

Borge

"B H" <(E-Mail Removed)> wrote in news:NaXqd.10265$rh1.254959
@news2.e.nsc.no:

> 230 User myusernameatftpserver logged in.
> ---> SYST
> 215 Windows_NT version 4.0
> Remote system type is Windows_NT.
> ftp> ls
> ftp: setsockopt (ignored): Permission denied
> ---> PASV
> 227 Entering Passive Mode (aaa,bbb,ccc,ddd,9,202).


Try doing a "dir" instead of "ls"?
Just guessing.

Gandalf Parker

"Gandalf Parker" <(E-Mail Removed)> wrote in message
news:Xns95B25CA972DC4gandalfparker@208.201.224.154 ...
> Try doing a "dir" instead of "ls"?
> Just guessing.

It didn't help. Last night I even tried using ftp through a GUI...in this
case gFtp. Even switching between passive and active did not give
me any solution....it seems to hang anyway.

So I am getting desperate now.
As I have said before a Window XP box at the same LAN can
do ftp to the same ftp-server without problems. So the problem
must be isolated to my Linux.box and not my Firewall Router.
I still wonder what those numbers 9 and 202 in this error message
means though. Port numbers?:

227 Entering Passive Mode (aaa,bbb,ccc,ddd,9,202).

Borge

>I still wonder what those numbers 9 and 202 in this error message
>means though. Port numbers?:
>
>227 Entering Passive Mode (aaa,bbb,ccc,ddd,9,202).

I'm pretty sure they are the port number.

Network geeks usually use tcpdump to look at things like
this when they run out of other ideas.

--
The suespammers.org mail server is located in California. So are all my
other mailboxes. Please do not send unsolicited bulk e-mail or unsolicited
commercial e-mail to my suespammers.org address or any of my other addresses.
These are my opinions, not necessarily my employer's. I hate spam.

Hal Murray wrote:

>>I still wonder what those numbers 9 and 202 in this error message
>>means though. Port numbers?:
>>
>>227 Entering Passive Mode (aaa,bbb,ccc,ddd,9,202).
>
> I'm pretty sure they are the port number.
>
> Network geeks usually use tcpdump to look at things like
> this when they run out of other ideas.
>

They are the port number, I believe it's 9*256+202 = 2506.
Are you sure there's no firewall blocking these ports... Possibly your WinXP
software uses another range of ports, that are open in your firewall...

More info on FTP:
http://slacksite.com/other/ftp.html

prompt

"Nico Declerck" <(E-Mail Removed)> wrote in message
news:comkj7$go1$(E-Mail Removed)...
> They are the port number, I believe it's 9*256+202 = 2506.
> Are you sure there's no firewall blocking these ports... Possibly your
WinXP
> software uses another range of ports, that are open in your firewall...

Could be a possibility. But I'm not an expert on this so I don't
know. But I guess I need to investigate the firewall settings better.
If I could find out ports used for Linux (2506?) and my XP box
then I guess it could be easier to see. But the nature of the problem
would indicate that the firewall is stopping something.

>
> More info on FTP:
> http://slacksite.com/other/ftp.html

Thanks. I'll check it out.

Borge