Hi,

I have a problem accessing a particular FTP site from a particular
network.  I can access other FTP sites from this network and I can
access this FTP site from other networks.
When I try to connect, I get back the 'connected to xxx.xxx.xxx.xxx'
message but it then hangs.  I can connect to it from my home machine
and it continues on to the login.  The FTP site admin assures me there
is no Reverse DNS requirement in action and my network admin assures me
the Firewall is not the issue.  (I can connect to other FTP sites
successfully anyway)

I don't know if it is relevant but the FTP site doesn't have a DNS
entry.  I'm trying to connect to the IP address directly.

Any FTP or network gurus able to cast any light?

JohnK

[ Post a follow-up to this message ]

In article <1127467935.037413.115760@g43g2000cwa.googlegroups.com>,
JohnK <johnk.dev.null@gmail.com> wrote:
>
>
>Hi,
>
>I have a problem accessing a particular FTP site from a particular
>network.  I can access other FTP sites from this network and I can
>access this FTP site from other networks.
>When I try to connect, I get back the 'connected to xxx.xxx.xxx.xxx'
>message but it then hangs.  I can connect to it from my home machine
>and it continues on to the login.  The FTP site admin assures me there
>is no Reverse DNS requirement in action and my network admin assures me
>the Firewall is not the issue.  (I can connect to other FTP sites
>successfully anyway)
>
>I don't know if it is relevant but the FTP site doesn't have a DNS
>entry.  I'm trying to connect to the IP address directly.
>
>Any FTP or network gurus able to cast any light?
>
>JohnK
>

Try passive FTP if your client supports it.  There can be firewall
issues with regular FTP.  For some clients

ftp -p

will invoke passive mode, or you can try

ftp
ftp> passive
ftp> open wwww.xxxx.yyyy.zzz



Ted

[ Post a follow-up to this message ]

Ted Nolan <tednolan> wrote:
> Try passive FTP if your client supports it.  There can be firewall
> issues with regular FTP.  For some clients
>
> 	ftp -p
>
> will invoke passive mode, or you can try
>
> 	ftp
> 	ftp> passive
> 	ftp> open wwww.xxxx.yyyy.zzz
>

Sun Microsystems Inc.   SunOS 5.8       Generic Patch   December 2002
$ ftp -p 193.195.77.150
ftp: p: unknown option
$ ftp
ftp> passive
?Invalid command
ftp>

No luck with that Ted... thanks anyway.

JohnK

[ Post a follow-up to this message ]

In article <56SdnVE8-_1BpKneRVnyhg@pipex.net>,
JohnK  <johnk.dev.null@gmail.com> wrote:
>
>
>Ted Nolan <tednolan> wrote: 
>
>Sun Microsystems Inc.   SunOS 5.8       Generic Patch   December 2002
>$ ftp -p 193.195.77.150
>ftp: p: unknown option
>$ ftp
>ftp> passive
>?Invalid command
>ftp>
>
>No luck with that Ted... thanks anyway.
>
>JohnK

Ok, you're on a Sun, and Sun's FTP client dates back to when petroleum
was on the hoof..

You can try this then.  If you have a web browser like netscape7
(probably firefox or mozilla as well, but I just checked netscape7)
on your Sun, it will do passive FTP for you.  Use a URL like

ftp://userid:password@ftp.anywhere.com/

So, if you need to get file from subdir1 on machine somebox.example.com
and the user name is fooby with password quiix, use the URL

ftp://quiix:fooby@somebox.example.com/subdir1

and see what happens.  With luck you will get a directory listing
that you can click to download files.


(You could also install a modern FTP client).

Ted

[ Post a follow-up to this message ]

Just to follow up my own response, when you use an FTP URL

ftp://userid:password@ftp.anywhere.com/some_path

if it's an anonymous FTP site, you can leave off the "userid:password" like

ftp://ftp.anywhere.com/some_path



Ted

[ Post a follow-up to this message ]

JohnK wrote:
> Hi,
>
> I have a problem accessing a particular FTP site from a particular
> network.  I can access other FTP sites from this network and I can
> access this FTP site from other networks.
> When I try to connect, I get back the 'connected to xxx.xxx.xxx.xxx'
> message but it then hangs.  I can connect to it from my home machine
> and it continues on to the login.  The FTP site admin assures me there
> is no Reverse DNS requirement in action and my network admin assures me
> the Firewall is not the issue.  (I can connect to other FTP sites
> successfully anyway)

Sounds like a firewall.... possibly a hosed route.

You're inbound on port 21, but not outbound.

This is the sort of thing you see when someone has blocked
the ports that ftp is trying to respond to.

Check the inbound rules on the firewall you're trying to
ftp *from*.

A static route on the ftp server sending the bits to neverneverland
could do the same sort of thing... seems like.

>
> I don't know if it is relevant but the FTP site doesn't have a DNS
> entry.  I'm trying to connect to the IP address directly.
>
> Any FTP or network gurus able to cast any light?
>
> JohnK
>

[ Post a follow-up to this message ]

In article <qUVYe.116$yl.25@bignews1.bellsouth.net>,
ted@loft.tnolan.com (Ted Nolan <tednolan> ) wrote:

> In article <1127467935.037413.115760@g43g2000cwa.googlegroups.com>,
> JohnK <johnk.dev.null@gmail.com> wrote: 
>
> Try passive FTP if your client supports it.  There can be firewall
> issues with regular FTP.  For some clients

The difference between passive and active FTP is only in the data
connection, not the control connection.  He's never getting far enough
into the FTP protocol for it to matter.

--
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***

[ Post a follow-up to this message ]

In article <L44Ze.72200$Jp.1656473@twister.southeast.rr.com>,
base60 <nobody@whitehouse.com> wrote:

> JohnK wrote: 
>
> Sounds like a firewall.... possibly a hosed route.

No it doesn't.  If it were a routing problem, he'd never get connected
in the first place.

--
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***

[ Post a follow-up to this message ]

base60 wrote:
> You're inbound on port 21, but not outbound.
> Check the inbound rules on the firewall you're trying to
> ftp *from*.

So would there not need to be a specific firewall entry for this FTP
server that was in some way broken, in light of the fact that I can
connect fine to other sites like ftp.sun.com?

In any case I have already asked our firewall dept to rouse themselves
and look at that very issue as well asking here.

> A static route on the ftp server sending the bits to neverneverland
> could do the same sort of thing... seems like.

I am on a corporate network and my own IP is a 10.xx.xx.xx address.  I
would have thought this would be NATed and so wouldn't be a problem but
if the FTP server had a specific 10.xx.xx.xx static route (say for a
management LAN or backup LAN) then could this be causing my packets to
go astray?

JohnK

[ Post a follow-up to this message ]

JohnK wrote:
> base60 wrote:
> 
>
>
> So would there not need to be a specific firewall entry for this FTP
> server that was in some way broken, in light of the fact that I can
> connect fine to other sites like ftp.sun.com?

Firewalls are used to filter traffic and produce lots of strange
and wonderful effects.

>
> In any case I have already asked our firewall dept to rouse themselves
> and look at that very issue as well asking here.
> 
>
>
> I am on a corporate network and my own IP is a 10.xx.xx.xx address.  I
> would have thought this would be NATed and so wouldn't be a problem but
> if the FTP server had a specific 10.xx.xx.xx static route (say for a
> management LAN or backup LAN) then could this be causing my packets to
> go astray?

As indicated to my response to Barry, this is speculation that seemed
to fit what you were seeing.

You probably should do a snoop on the ftp server to see if you're
getting a connection and go from there.

[ Post a follow-up to this message ]