GeneralThis forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
hey guys...i'm having trouble logging into my filezilla server. i was once able to, awhile ago, but never did anything with my my router so as to be able to view it accross the lan, or remotely. then, today, i managed to get that done, but now, i can't log into filezilla to make anychanges to the server, like make an annonymous account, or anything like that...
when i click to connect to server, it asks for server ip address and port. for address, i have tried the computer's address and i have tried the routers address. for port, i have tried port 21, and various other random ports. i don't ever remember making a password, so, i have tried with and without my typical passwords, and still ntohing. what am i missing? what SHOULD i be doing? thnx
edited: here is an error that i seem to get when i use the routers ip address and port 21. it doesn't matter what i put for password...so i'm thinking that it might be a password problem? anyways :
Connecting to server...
Connected, waiting for authentication
Protocol error: Unknown protocol identifier (0x50 0x50 0x48).
Connection to server closed.
i figured out my problem. i guess when i tried to figure out the port number, i was trying some typical numbers others have tried. i finally decided to uninstall and install again. what i needed to begin with was the port number i set to default. if u are still haveing this trouble, uninstall and install. write down the default port number that filezilla gives u, and just accept it. after that, keep that port number somehwere just incase someone changes it on u.
Distribution: Used to use: Ubuntu. Still use: Debian, Other small distros
I'm not sure about you guys, but I got things to start working by disabling Windows Firewall completely. A very bad idea, I know, but I'm not in the mood to go testing it to see what exactly is causing the problem. My guess is it may be one of the IMCP settings.