Router stopping FTP through IE?

[archcommus]

I use IE to access my Comcast-provided storage space, simply by typing ftp://upload.comcast.net in the address bar. It has always worked fine but hasn't since I set up my network, so I'm assuming the router it somehow stopping it. When I try to access it, before it even pops up the log-in dialog box, it says "Windows cannot access this folder. Make sure you typed the file name correctly and that you have permission to access the folder. Details: The connection with the server was reset."

Do I simply have to forward a specific port for FTP to work? This is my first time with a router. I tried forwarding port 21 but it didn't help.

 

[keeleysam]

http://flashfxp.com

 

[archcommus]

Not interested in another program, thank you.

 

[Vertimus]

IE ftp is inherently broken. Don't use it. Case Closed.

 

[archcommus]

Originally posted by: Vertimus
IE ftp is inherently broken. Don't use it. Case Closed.

Functioning every day for years doesn't seem inherently broken to me. I can transfer to, I can transfer from, that's all I need, case closed.

Stop wasting my time, if you can't help, don't post.

 

[randal]

Have you tried clicking the "file" menu, then selecting "login as..." once you receive the error message? On my IE, it always fails immediately if I don't supply a username & password in the URL. (in URL: ftp://$USERNAME$:$PASSWORD$@upload.comcast.net ... minus the $s)

 

[archcommus]

Thanks, no go, though. I tried putting the username and pass in the URL, brought up the same message. Then I tried clicking Login As... and entering my info, did the flashlight searching a folder thing, brought up the same message.

If I exit Sygate, I'm able to at least sign in, but even then, when I try to drop a file in it, it says I don't have permission to do it. I never had a problem with Sygate and this method of accessing my storage space before. I'm almost certain the router's blocking it.

 

[Sunner]

Try passive mode(don't know how to do that under IE, should be under "Internet Options" or whatever it's called).

If that doesn't work, try another program, if nothing else to try to identify the problem.
Not wanting to even try one to just see if it's IE messing with you is like refusing to open up your computer for a troubleshoot.

And I will add that I agree with the others, I used to admin an FTP server where customers would retrieve data a few times a week, and all the problems they ever called us about were related to IE's crappy FTP client.

 

[nweaver]

incomplete implementation is pretty close to inherently broken. It's probably a passive mode issue, and several good alternatives have been offered. I always just use the command line when I have to ftp from a windows machine.

try an alternative to make sure there was not an update to security on the server causing the problem.

 

[ronzilla]

"Use Passive FTP" is under "Browsing" on the Advanced tab of the Internet Options dialog box.

You should seriously consider (at least try) something other than IE for FTP transfers. SmartFTP is one I really like.

 

[TGS]

Open port 20 and 21, if that doesn't work try putting your machine in the DMZ. Run some firewall software if you do.

 

[archcommus]

Passive FTP is already checked, I'll try opening ports 20 AND 21 and maybe another program when I get home tonight.

 

[randal]

Try unchecking passive FTP and see if it goes. I have always had serious problems with IE+Firewalls.

 

[lansalot]

You can't set a port range in IE for PASV connections. Unlike in a proper FTP client.

Forwarding 20 + 21 won't help you at all as that's not what your problem is. There's nothing you can forward that will make IE work.

 

[spidey07]

Originally posted by: lansalot
You can't set a port range in IE for PASV connections. Unlike in a proper FTP client.

Forwarding 20 + 21 won't help you at all as that's not what your problem is. There's nothing you can forward that will make IE work.

this is the fault of the router, not IE (not that IE is the worst FTP client ever known because it is)

If the nat router doesn't know how to deal with FTP it shouldn't be on the market. Maybe its an option in the config?

Posting the router model would help.

 

[archcommus]

Well, Windows Firewall turned out to be the problem. If I turn it off, FlashFXP and IE FTP both work just fine. That's very odd, as I never had a problem with FTP in the past with Windows Firewall on.

Up until now I left Windows Firewall on because it never really got in the way, so I figured why not, it's an extra layer of protection. But after this I guess I'll leave it off. Not like I really need it with Sygate and my router, anyway.

So for the router, do I really need to forward port 20? It seems I only have to do TCP 21.

 

[Washoe]

Did FlashFXP not work also when you had Windows Firewall turned on?

 

[archcommus]

Originally posted by: Washoe
Did FlashFXP not work also when you had Windows Firewall turned on?

Yep, even with an exception created for it. STILL didn't work.

 

[Jon855]

ftp may need port forwarding on your router, just set these port numbers, 21 to be forwarded

 

[archcommus]

Yes, I did that, but it still would not work until I turned off Windows Firewall. Very peculiar, considering it never caused a problem with FTP in the past.

 

[archcommus]

Another question, how come when certain applications need specific ports, i.e. eMule requiring TCP 4662, it must be forwarded to your computer for the router to let traffic through, however I don't have to do this with a software firewall like Sygate? I've never created advanced rules to open up ports in Sygate for things like eMule, Shareaza, FTP, etc., however all those things work just fine. Why?

And even with the router, if I don't forward port 21 to my computer, FTP usually still works fine. Again, why?

 

[archcommus]

Hmm?

 

[lansalot]

Because port21 is the OUTGOING port, you don't need to forward it to anything. Unless you are running an FTP server on your own machine.

Read up on specifying the PASV port range as I said earlier.

 

[archcommus]

Originally posted by: lansalot
Because port21 is the OUTGOING port, you don't need to forward it to anything. Unless you are running an FTP server on your own machine.

Read up on specifying the PASV port range as I said earlier.

Outgoing, right, makes sense.

No need to do anything more, though, now, disabling Windows Firewall did the trick.

 

[JackMDS]

Being connected directly to a Modem is not as using a Router and having a LAN.

Switching Off a Firewall, and using the Internet with a Router only is not very safe either.

Given the nature of your first post and the mentioning of the error that popped up:

"Windows cannot access this folder. Make sure you typed the file name correctly and that you have permission to access the folder. Details: The connection with the server was reset."

I would not be surprised if you would have more trouble in the future,

:sun: