Having problems with my FTP(possibly my fault)

[andyrose]

I'm having trouble connecting with ALL of my FTP programs. This includes CuteFTP standard and pro, WS FTP, and even Dreamweaver.

Here's what CuteFTP says when the problem happens(while trying to connect):

STATUS:> Resolving host name ftp.neomega.net.
STATUS:> Host name ftp.neomega.net resolved: ip = 63.151.112.235.
STATUS:> Getting listing ""...
STATUS:> Connecting to ftp server ftp.neomega.net:21 (ip = 63.151.112.235)...
ERROR:> Can't connect to remote server. Socket error = #10061.
STATUS:> Waiting 30 seconds...

Now, it's very possible that I'm the cause of this problem. For various reasons I had to mess with my network address last month, and this may be the cause of the problem.

*sigh* Anyone familiar with Socket error #10061? I'm going to do some searching on google right now.

[sheila]

Andy,

I just tested and was able to make an FTP connection to ftp.neomega.net with no problems at all.

This does appear to be a network problem.

Have you tried running a traceroute to ftp.neomega.net from your computer?

http://www.aota.net/Server_Performance/index.php4

Try the tutorials linked above, if you haven't done traceroutes before.

[andyrose]

No, I hadn't actually tried the traceroute before. Thanks for letting me know.

Tracing the route to ftp.neomega.net (63.151.112.235)

1 a1-3-1-0-1.a01.hstntx01.us.ra.verio.net (128.241.2.65) 0 msec 0 msec 4 msec
2 ge-5-0.r01.hstntx01.us.bb.verio.net (129.250.29.94) [AS 2914] 0 msec 0 msec 4 msec
3 p16-2-0-0.r00.hstntx01.us.bb.verio.net (129.250.3.46) [AS 2914] 0 msec 0 msec 4 msec
4 p16-1-1-1.r21.dllstx01.us.bb.verio.net (129.250.5.4) [AS 2914] 4 msec 8 msec 8 msec
5 p16-2-0-0.r02.dllstx01.us.bb.verio.net (129.250.3.31) [AS 2914] 4 msec 8 msec 4 msec
6 p4-0.qwest.dllstx01.us.bb.verio.net (129.250.9.82) [AS 2914] 8 msec 4 msec 8 msec
7 dal-core-01.inet.qwest.net (205.171.25.45) 4 msec 8 msec 8 msec
8 iah-core-02.inet.qwest.net (205.171.8.126) 12 msec 8 msec 12 msec
9 iah-core-01.inet.qwest.net (205.171.31.1) 12 msec 12 msec 12 msec
10 tpa-core-02.inet.qwest.net (205.171.5.105) 44 msec 44 msec 48 msec
11 tpa-core-01.inet.qwest.net (205.171.27.181) 44 msec 48 msec 48 msec
12 tpa-edge-03.inet.qwest.net (205.171.27.26) 44 msec 48 msec 44 msec
13 63.144.0.106 48 msec 52 msec 52 msec
14 ftp.neomega.net (63.151.112.235) 52 msec 52 msec 52 msec

According to the tutorials, that seems to be a pretty normal response. I may have to try resetting all of my network settings.

[Jeff]

<taking a stab in the dark>
Any chance you are running a firewall locally?

[andyrose]

Negative, good buddy. :(

Although.....I will check again.

[Jeff]

I take it you've tried connecting in Passive Mode? What was the nature of the network change you made?

[kitchin]

Sometimes your internet provider (or computer) goes out to lunch on just one protocol. Using Earthlink yesterday, I was unable to POP to any email account, including one at Earthlink itself, for about half an hour, even though everything else worked fine (web, traceroute,...). Something fixed it: either restarting Win98 or something at Earthlink.

[andyrose]

Jeff: my network address seems to be set at 000000000(all zeros) on this new PC that I just built. I built it from scratch, and I'm using Windows XP Pro.

I had a program that needed a certain network address to work, so I tried a few different options to try to fix my all zeros problem. It ended up working with the all zeros address, so I assumed everything would work normally.

I have tried PASV mode, that's what Futurequest requires anyway, right? I have found out that it's on my end, not Futurequest's end. I can't connect to ANY FTP sites.

I'll do some more research, I'm sure I'll be able to fix it sometime down the line. :\

[andyrose]

Ran a self diagnostic in Windows XP Pro, got this back:

DefaultIPGateway = 208.170.85.3(Same Subnet) (FAILED)
Pinging 208.170.85.3 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 208.170.85.3:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)


and also this

IPAddress = 208.170.85.3 (FAILED)
Pinging 208.170.85.3 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 208.170.85.3:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)

I think I found my problem. Not sure exactly how I can go about fixing the problem, but I'm going to start by reinstalling all of my network drivers.

[andyrose]

Does anyone know what a 10061 error signifies?

I totally reinstalled Windows XP, and I seem to still be having the same problem. For some reason, however, Dreamweaver has been connecting fine.

If I can't get my FTP clients to work, then I have to ask one question:

Will using Dreamweaver to upload my files possibly lead to problems? Does it switch file transfer modes like most FTP clients?

[Deb]

Are you connecting with Port 21 non-SSL ?

I am not a DW user so I hesitate to answer that part..though I'm sure others may be able to.

Deb
- Tested again.. worked again %)

[Bruce]

Originally posted by andyrose:
Does anyone know what a 10061 error signifies? From my searching on the web, socket error #10061 appears to happen when the server flat out rejects the connection. However, unless the FTP server was shut down, the connection would not normally be rejected. It may be delayed, or dropped after connection, but not rejected up front.

COLOR=indigo]I totally reinstalled Windows XP, and I seem to still be having the same problem. For some reason, however, Dreamweaver has been connecting fine.[/COLOR] I have scanned the logs on your CS, and find no obvious errors on any of your connections to our FTP server. I find it excedingly odd that DreamWeaver FTP would work, and others FTP clients would fail.

Will using Dreamweaver to upload my files possibly lead to problems? Does it switch file transfer modes like most FTP clients? I have not used DreamWeaver to handle web sites, so I can't speak authoritatively, but I am aware of no current problems with uploading using DreamWeaver FTP.

[sheila]

Originally posted by andyrose:

If I can't get my FTP clients to work, then I have to ask one question:

Will using Dreamweaver to upload my files possibly lead to problems? Does it switch file transfer modes like most FTP clients?
Andy,

I do use DreamWeaver a fair amount for uploading files. Although my files are almost exclusively .html, .txt, .gif and .jpg files. Maybe some .shtml or .php. I have defined the file extensions for .shtml, .php, .html, etc... in the DreamWeaver configuration/preferences set up. I have no trouble transferring files with DreamWeaver. It seems to automatically detect whether to use text mode or binary mode for file transfers. I never seem to have to check that. YMMV. At least, that's how it works for me.

[Jeff]

It still sounds very much like a local firewall issue to me - doesn't Windows XP have a built in firewall?

[andyrose]

I don't know, maybe there's some 'hidden' firewall that I can't find. I'm still doing research into the problem, but I don't seem to be getting anywhere.

Dreamweaver isn't doing a bad job at all, but one thing makes it difficult: The files you want to upload have to be in your default Dreamweaver directory(ex: c:\neomega.net). I guess that's not a bad thing, it forces me to organize my files better.

I'm going to keep trying. There has to be a reason.

[skolnick]

It certainly *sounds* like a firewall problem, but I can't imagine a firewall discriminating between one process (ftp) and another (Dreamweaver)--particularly on Windows--without a lot of purposeful work. It seems to me it must be a rather subtle configuration issue (an easy one would be found already, and would affect both ftp and Dreamweaver).

[andyrose]

Are CuteFTP/WS FTP dependant upon Internet Explorer in any way? I had a problem connecting with Sun Microsystem's download site a few days ago, but Netscape did the job fine. I think I may try reinstalling IE and see what happens.

[Jeff]

but I can't imagine a firewall discriminating between one process (ftp) and another (Dreamweaver)
I'm used to running ZoneAlarm which does exactly this - when it installs it picks up your default browsers and then for every other program which tries to connect (either purposefully like if you start an ftp program and click connect, or install a new browser, or things like software trying to call home) it prompts you whether you want them to access the internet and whether you want them to act as a server. After a while you build up a list of all your programs when you open ZoneAlarm, and from there you can check always / never / or maybe. If you click never for a program that program will never be able to connect to the internet and you won't be prompted (unless you have the notification on). Anyway, it's a pretty remote chance, but I've accidentally clicked no for some old programs which are cryptically identified in the list and found that this or that no longer works. I also know that when FutureQuest switched FTP servers with ZoneAlarm set to High (the free version of ZA) I had to specifically allow my domain names for WS_FTP to be able to connect. (or I could have set ZA down a notch to medium). But maybe it is something else entirely. Certainly a strange problem.

Can you ftp from the dos prompt / command line?

[skolnick]

Jeff makes some good points, particularly for the case where a firewall is running on the same machine as your applications. That does make it much more likely that process identification could be happening (I use a separate firewall/router between my network and the Internet).

Try hitting ctrl-alt-delete to bring up the task manager, click on Processes, and scroll down the list looking for something that might be a firewall. Note that arbitrarily killing processes is likely to make your system unstable (bloody WIndows), but the list may lead you to the problem if it is the result of a firewall or other process.

I still lean toward a configuration problem, but what do I know?

[kitchin]

Windows XP has a firewall you can apply or disable in
Control Panel / Network Properties / Properties / Advanced

[andyrose]

It wasn't a firewall, it was some sort of misconfiguration. I wasn't able to access secure servers or use my various FTP programs.

However, the problem has been fixed. I reinstalled Windows, downloaded all of the latest XP updates, and reinstalled all of my FTP programs. Whatever was wrong is fixed now.

Thanks for all the support, though. :)

[andyrose]

I found out what the problem was. Windows XP Pro does not like Symantec Norton Internet Security 2001 version. That was my problem, nothing on FQ's end.