Opened 16 years ago
Last modified 11 years ago
#3549 closed Bug report
Cannot connect to server
Reported by: | karmannjro | Owned by: | |
---|---|---|---|
Priority: | normal | Component: | FileZilla Client |
Keywords: | Cc: | karmannjro, Tim Kosse | |
Component version: | Operating system type: | ||
Operating system version: |
Description
After I got notified of the 3.0.11 update and installed it, I tried connecting to my server on the same segment of LAN, but couldn't get any connection at all with FileZilla. I can get through fine by pinging and PuTTY, I can even get FTP files from it with Firefox (but it's so awkward!), but with FZ, a tcpdump on the other host doesn't show a single packet getting to it. Now, I don't know my MS Windows administration as well as the *nix, but the built-in XP firewall claims to be completely off, and I'm pretty sure there's nothing else of the sort on here. I certainly haven't deliberately installed such a thing lately, and I haven't seen any popups asking to allow network access lately.
This is on a MS Windows XP Media Center box, with SP2 but I'm holding off on SP3 yet.
Here's its "about":
FZ 3.0.11
Compiled for: i586-pc-mingw32msvc
Compiled on: x56_64-unknown-linux-gnu
Build date: 2008-06-15
Compiled with: i586-mingw32msvc-gcc (GCC) 4.2.1-sjlj (mingw32-2)
Compiler flags: -g -O2 -Wall -g -fexceptions
Level 3 log attached.
Attachments (1)
Change History (4)
by , 16 years ago
Attachment: | filezilla-log.txt added |
---|
comment:1 by , 16 years ago
This is not a bug.
Either the address is incorrect, the server is offline or there still is some firewall blocking you. Also check your virus scanner or any other so-called "security solution".
comment:2 by , 16 years ago
Look, I agree it's not necessarily a bug in FileZilla, but I think given that I can run tcpdump on the server and not see a single packet coming its way, I can be pretty sure it's not offline, OK? And given that I can access it from Firefox, it's neither offline nor wrong address. Besides, I have tried other servers not under my control, and gotten the same result.
But I would agree that a "security solution" is fairly likely at fault. This computer's got Norton stuff on it (it's not my own), and they're always reluctant to loosen their grip on a computer.
Followup: OK, for comparison, I tried downgrading to 3.0.10, connected to everything just fine, and then, only after I upgraded back to 3.0.11, Norton finally asked me if I wanted to allow this program to connect, blah blah blah. I hate this stuff. (Thie Norton, that is, not FileZilla! Love it!)
Incidentally, maybe this should be a different bug report, but while investigating, I noticed that your http://ip.filezilla-project.org/ip.php page is returning 127.0.0.1. Is that page intended for actual use by FileZilla users, or is it just a sample page to give people the general idea?
comment:3 by , 16 years ago
Incidentally, maybe this should be a different bug report, but while
investigating, I noticed that your http://ip.filezilla-project.org/ip.php
page is returning 127.0.0.1. Is that page intended for actual use by
FileZilla users, or is it just a sample page to give people the general
idea?
It only returns the correct address to FileZilla, not to your web browser. Had to implement it that way due to abuse of that service by too many third party programs.
FileZilla can't-connect log