Re: FTP

I think I found my problem.

I use McAfee personal firewall 6.1.6144. Before all the updates, the windows
firewall was disabled. Somehow it was re-enabled. Now everything woks great
with the windows firewall disabled! Don't you wish that when someone changes
you windows default settings, they should let someone know? Like the
user/owner of the hardware/software.

Let us all stop and pay $$$$ ......

"Gott" wrote:

The issue here is not that FTP can not be accessed via command line FTP or
previously via IE6 even through a NAT router. The issue is that there has
been an Windows or a Microsoft update which prevents FTP access regardless
of whether you select or deselect passive checkbox or use folders for FTP
checkbox. This IE7 update, whatever it is, has also now effected IE6 so it
does no good to do an IE rollback. Using a third party FTP browser is
suspect because all of them entail an eventual cost. This is the suspicious
part of whatever is going on - perhaps a MIP paving the way to make money by
selling a browser for FTP or helping a friend to do this.

--
Best Regards
"KLHNet" <KLHNet@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4B04DD45-A1D4-401C-A87C-723FF5A1F5B6@xxxxxxxxxxxxxxxx
Thanks Tim for the information.

I bypassed the router last night and verified that "IE7" & command prompt
did not work.

Before I posted my first message I verified that passive and active did
not
work.

I used to use WS_FTP before I started using Windows XP. I think I should
try
something like that.

If you see any fixes for this "Windows XP" problem, please do not hesitate
to post here.

KLHNet


"Tim Slattery" wrote:

KLHNet <KLHNet@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

Has anyone found a solution to the FTP problem?

I know it worked a few months back for me. The only thing common between
my
two computers is IE7, Windows updates! (and router) but as mentioned
above I
know it was working a few months back.

My guess is that the "and router" part is what's causing you grief.
You probably need to switch your FTP client to use passive mode.
Unfortunately the built-in command-line FTP client doesn't know
anything about passive mode. I'm quite sure there's a setting in IE7
someplace, but I don't know where. And I know you can find dedicated
FTP clients via Google that will handle this.

FTP normally uses "active mode". When you ask for a file to be
transferred, or even for a directory listing to be sent to you, the
server asks your computer for a port that it can be contacted on. The
server then opens a connection to that port, sends the file, and
closes the connection. So your client knows exactly when all the data
has been transmitted, and the command connection still exists, ready
to handle more commands.

If you have a NAT (Network Address Translation) router controlling
your home network - and pretty well all home routers do that, that's
how they share a single Internet connection among multiple computers -
this won't work. The router won't know what to do with the incoming
connection request from the server, and will ignore it. This behavior
protects your net from *lots* of Internet -transmitted grief.

In passive mode, the client asks the server for a port. The client
then opens a connection to the server on that port. The router
understands this, and has no problem with it. And your FTP connection
works.

--
Tim Slattery
MS MVP(DTS)
Slattery_T@xxxxxxx
http://members.cox.net/slatteryt




.