Author Topic: FTP Problem (Read 4402 times)

George Richardson · « **on:** July 24, 2014, 11:18:09 AM »

Much of my weather info that I FTP to my website has failed to upload since 3:30 this morning. Fling, Lightning2000, and Cumulus have their connections timeout but ImageSalsa is shooting stuff up and my Vivotek IP PTZ is also connecting. I have reset the modem, router, and computer. I have talked with the web host and they see no problem. Has anyone had a similar problem and if so, how did you fix it?

Please see:
http://www.smlweather.com/
http://www.smlweather.com/campage.htm
http://www.smlweather.com/PTZCamera4.htm

Thanks for any help.

George

ConligWX · « **Reply #1 on:** July 24, 2014, 12:35:02 PM »

How are you connecting to the site, by domain name or IP address? Possibly a DNS issue?

George Richardson · « **Reply #2 on:** July 24, 2014, 12:45:46 PM »

IP address: 205.178.145.65

ValentineWeather · « **Reply #3 on:** July 24, 2014, 03:27:03 PM »

Whats the ftp server name? Try your browser and see if you can login or get a login box by typing in ftp.what ever servername is. example...ftp.ipower.com
I've had weird issues with Ipower before where I couldn't even get a login box from home computer. It was like I was being blocked because others outside could login. I thought it had something to do with router or the wireless side because when I hooked the cat5 up directly I was able to login again.

meteo-saint-brevin · « **Reply #4 on:** July 24, 2014, 04:31:28 PM »

Hi,
Sometimes, to solve time out, I had to toggle each software from/to passive mode to upload in FTP.
If it can help.
Regards
Marcel

Cutty Sark Sailor · « **Reply #5 on:** July 24, 2014, 04:53:58 PM »

George, do a tracert to your host... then send that to your ISP.... sometimes there's a net problem, and they're not aware, especially to secure logins....
Mike

George Richardson · « **Reply #6 on:** July 24, 2014, 04:57:15 PM »

"do a tracert to your host.."
Please explain, I'm dumber than dirt ( and older too!)

ValentineWeather · « **Reply #7 on:** July 24, 2014, 04:59:29 PM »

I tried, ftp://205.178.145.65 in browser and got the login so your ftp should be working. If you can't login at all, as in don't get login box.... bypass wireless and try hard wire directly into computer.
These are some of the ftp issues I've had, using a netgear router. I finally had to change back to older Linksys router.

Cutty Sark Sailor · « **Reply #8 on:** July 24, 2014, 05:18:53 PM »

Quote from: Cutty Sark Sailor on July 24, 2014, 04:53:58 PM

George, do a tracert to your host... then send that to your ISP.... sometimes there's a net problem, and they're not aware, especially to secure logins....
Mike

Quote from: George Richardson on July 24, 2014, 04:57:15 PM

"do a tracert to your host.."
Please explain, I'm dumber than dirt ( and older too!)

Instructions here: http://www.mediacollege.com/internet/troubleshooter/traceroute.html

Here's what I just did to the URL Valentine listed...likely issues are in bold....
Tracing route to vux.bos.netsolhost.com [205.178.145.65]
over a maximum of 30 hops:

5 13 ms 15 ms 13 ms rrcs-98-102-206-237.central.biz.rr.com [98.102.2
06.237]
6 28 ms 24 ms 22 ms Te8-13.LSVMKYZO1RW.mw.twcbiz.com [65.189.185.205
]
7 20 ms 23 ms 23 ms be24.clmkohpe01r.midwest.rr.com [65.189.140.162]

8 52 ms 36 ms 35 ms bu-ether15.atlngamq47w-bcr01.tbone.rr.com [107.1
4.19.36]
9 62 ms 69 ms 38 ms 66.109.1.76
10 * * * Request timed out.
11 53 ms 49 ms 50 ms vl-3602-ve-226.ebr2.Chicago2.Level3.net [4.69.15
8.54]
12 46 ms 46 ms 48 ms ae-5-5.ebr2.Chicago1.Level3.net [4.69.140.193]
13 * * * Request timed out.
14 * * 120 ms ae-2-3015.ear1.Atlanta2.Level3.net [4.69.150.174
]
15 92 ms 91 ms 48 ms FIDELITY-IN.ear1.Atlanta2.Level3.net [4.30.236.2
]
16 75 ms 46 ms 47 ms 209.17.112.34
17 47 ms 47 ms 53 ms vux.bos.netsolhost.com [205.178.145.65]
18 48 ms 48 ms 47 ms vux.bos.netsolhost.com [205.178.145.65]

Trace complete.Interesingly, the same issues we've had at my ISP periodically, in and out of Chicago...

George Richardson · « **Reply #9 on:** July 24, 2014, 07:57:33 PM »

Is there anyway to increase the time to timeout? Did I say that right?

ConligWX · « **Reply #10 on:** July 24, 2014, 08:01:13 PM »

Can you confirm mtu is set correctly on your PC for the type of broadband you have?

Usually 1500 for cable. 1492 for ADSL.

George Richardson · « **Reply #11 on:** July 24, 2014, 08:31:37 PM »

OK, a different tack. The Cumulus FTP Progress window stayed open 20 seconds before displaying "Connect Timeout" so that should be long enough.

What could the host company have changed overnight with a flip of a switch that could cause Fling, Filezilla, Cumulus, GRLevel3, and L2K to suddenly cease providing FTP data? Am I being paranoid to see everything shut off and yet the host tells me that for a $60 fee they can fix it.

George

ValentineWeather · « **Reply #12 on:** July 24, 2014, 09:11:52 PM »

Can you login with browser ftp://205.178.145.65 ? If you don't get a login box its not your host its your equipment.

George Richardson · « **Reply #13 on:** July 24, 2014, 09:35:16 PM »

Randy,

Thanks for breaking out the baseball bat and hitting me over the head with it! I just took a laptop and hooked directly to the modem and was able to see my web directory. To late tonight but tomorrow I will remove the Linksys router and replace it. Hopefully that will get me back up and running.

Again, thanks to everyone that contributed.

George

ValentineWeather · « **Reply #14 on:** July 24, 2014, 10:13:06 PM »

Quote from: George Richardson on July 24, 2014, 09:35:16 PM

Randy,

Thanks for breaking out the baseball bat and hitting me over the head with it! I just took a laptop and hooked directly to the modem and was able to see my web directory. To late tonight but tomorrow I will remove the Linksys router and replace it. Hopefully that will get me back up and running.

Again, thanks to everyone that contributed.

George

No problem , I've been through it and haven't figured out why it happens. Router just starts blocking the ftp

If you are using Wifi try connecting with just a cat5 cable and it might correct the problem also.

cospringswx · « **Reply #15 on:** July 25, 2014, 12:04:48 AM »

Replace the Linksys with an Asus.

ValentineWeather · « **Reply #16 on:** July 25, 2014, 12:23:36 AM »

Quote from: cospringswx on July 25, 2014, 12:04:48 AM

Replace the Linksys with an Asus.

You have a good point. Netgear and Linksys are the two having this issue. This 2010 thread touches on part of it. Railhound seems to have the best handle speaking with FileZilla techs.
http://community.linksys.com/t5/Wireless-Routers/Linksys-router-blocking-access-to-ftp-server-that-I-need-to/td-p/332740

cospringswx · « **Reply #17 on:** July 25, 2014, 12:41:01 AM »

I have the Asus RT-N66U and I love it. I've had nothing but problems with Netgear and Linksys in the past. The interface control panel is very well designed. Highly recommended.

ConligWX · « **Reply #18 on:** July 25, 2014, 02:51:32 AM »

Quote from: cospringswx on July 25, 2014, 12:41:01 AM

I have the Asus RT-N66U and I love it. I've had nothing but problems with Netgear and Linksys in the past. The interface control panel is very well designed. Highly recommended.

even better when you put Tomato firmware on the N66-U. It transforms the router with more features.

George Richardson · « **Reply #19 on:** July 27, 2014, 08:19:55 AM »

The saga continues. I have been working my IT guy (my son) hard. We replaced the Linksys WRT54G v4 with a new Linksys WRT54G v5. The upload side of the router seemed good but the download and distribution on the LAN was horrible. Especially things like my weather site or even Yahoo News. The page load simply wouldn't finish. I discussed getting the Asus RT-N66U as recommended but it is close to a 70 mile drive (roundtrip) to the nearest BestBuy plus that router ain't cheap. My IT guy suggests Tomato firmware and I say how about DD-WRT. Well, he's heard good things about Tomato and since it's his party, we go with Tomato. Tomato only works on Linksys WRT54G routers thru v4 so we remove the new v5 and replace it with the old v4. It works great, except it doesn't seem to port forward my PTZ cam. So, I have a Logitech 9000pro that uses ImageSalsa and is "port forwarded" and a Vivotek PTZ that I can control locally by typing in the IP address but can't get to over the internet. I see a couple of questions. First and foremost, anyone have any idea on how to get this camera displaying on the internet. Is there a "Tomato forum" I could seek help.

Continued Thanks

George

Logitech 9000pro => http://www.smlweather.com/campage.htm

Vivotek PTZ => http://www.smlweather.com/PTZCamera4.htm

ed2kayak · « **Reply #20 on:** July 27, 2014, 08:35:57 AM »

Some tomato faq's here: http://www.polarcloud.com/tomatofaq

Maybe DNS problem?

Steve Gibson at GRC has an excellent write up and small utility you can download and run. It allows you to check to see if you have the best DNS servers foe your location.

https://www.grc.com/dns/benchmark.htm

Ed

PaulMy · « **Reply #21 on:** July 27, 2014, 09:19:55 AM »

George,
The Cam 1 works fine. Nice view. The other one stays at "Image loading..."

Paul

George Richardson · « **Reply #22 on:** July 27, 2014, 12:35:55 PM »

I want to thank everyone for looking at this for me. My IT guy was able to figure it out. Under Tomato, Port Forward, he had to enable "DMZ" for the camera local IP address. Don't ask me what it means even though he explained it to me. I hope this works forever but. . .

ValentineWeather · « **Reply #23 on:** July 27, 2014, 05:51:58 PM »

That might be the key for all these routers having issues. I read somewhere else where techs had someone turn on DMZ and FTP started again. I'll keep it in mind, DMZ is for opening ports for gaming.

ConligWX · « **Reply #24 on:** July 27, 2014, 07:17:29 PM »

I'd use the v4 wrt over a v5 any day of the week. V5 was a bad router. Asus RT-N66 is a good solid router with tomato firmware. Also the v4 art should take tomato firmware too.

Check out the tomato forum at LinksysInfo.org.

DMZ is opening all Potts for a specific ip address

If you port forward ports 20/21 for ftp, and port xx (for web can access) that should suffice.

Make sure if you port forward that the device you are forwarding the port protocol too has a static IP address and not one issued by dhcp.

News:

Author Topic: FTP Problem (Read 4402 times)