Anon | FTP works then it doesn't work. WTF???? OK I had my linksys working with BPFTP 2.15 for at least weeks. Then today it decides it doesn't want to connect. It does find the server, but it stops at getting the list and never shows what's in the folder. I tried updating the firmware to 1.39, but that hasn't helped. I have everything connected right. Port 21 is forwarded to the static IP of the server. SPI is disabled. I even tried putting the server in the DMZ and still nothing. I'm not sure what's going on. Is it possible bellsouth is blocking port 21? That really doesn't seem right since I can connect, but not get the folder list. I can connect internally. Help...
Greg |
|
|
|
 Bill_MIBill In MichiganPremium,MVM
join:2001-01-03
Royal Oak, MI
kudos:1
 ·Comcast
·WOW Internet and..
| Greg,
Turn on all the BPFTP logging options (screen or file, your choice). Look at the failed connection for a "PORT xx,xx,...." command from the client. Or is there a "PASV" from the client? The client is either at fault or trying to do PASV - I bet. Either won't work unless you've set up more than you describe.
[text was edited by author 2001-06-11 19:56:03] |
|
Anon | reply to Anon
OK here you go. After it says the user is logged in says PORT 208,236,74,90,5,22. I wouldn't think it would matter a whole lot since I have the server in the DMZ. All ports should be forwarded right?
I actually have the luxury of having cable and DSL in my apartment. I've tried quite a few times to login with WSFTP le from the cable access to the server which is running off DSL. I've tried both passive and non-passive modes. The funny thing is I connected this morning using a MAC on campus. Thanks,
Greg |
|
Bill_MIBill In MichiganPremium,MVM
join:2001-01-03
Royal Oak, MI
kudos:1 Reviews:
·Comcast
·WOW Internet and..
| said by GregorySH:
PORT 208,236,74,90,5,22. I wouldn't think it would matter a whole lot since I have the server in the DMZ. All ports should be forwarded right?
It's the opposite of what you think, Greg. The client end is the server for the data channel in this case. Here's what the PORT boils down to...
The client is at 208.236.74.90. No problem if that's the right IP. Double check the log it is (I don't expect this to be bad).
The client is saying THEY will be a server for the bad data channel on TCP port 5x256 + 22 = 1302.
Now... either the client cannot be a server *or* you can't connect OUTbound on port 1302. That's OUTbound, not INbound (INbound is your forwarded ports).
Now we're down to who's bad... your end or the client? Does the client have a firewall? Does your end do anything with outbound port 1302?
By the way, you can setup PASV with a little more entries using BPFTP, otherwise your server should never work in PASV. The catch-can is if the client is behind a firewall it (and you) *must* usually run PASV. I think this is your best bet - I suspect the client end in this case.
[text was edited by author 2001-06-11 20:38:02] |
|
Anon | reply to Anon
OK heres one that's going to flip your wig. The cable is using the same Linksys router. Ah Ha you say. But...I have a friend who is using the same linksys router as the cable connection I have and the DSL connection, and I used to be able to connect from his house (I would try from his house tonight, but he's not home) Also, I connected from one school computer this morning, but couldn't connect from another lab this afternoon. I'm sure the school is running routers a little better than my crappy Linksys.
Thanks for your help,
Greg |
|
Bill_MIBill In MichiganPremium,MVM
join:2001-01-03
Royal Oak, MI
kudos:1 Reviews:
·Comcast
·WOW Internet and..
| Greg,
You *are* on port 21 right? The LinkSys, even though it's an NAT firewall, handles FTP port 21 fine for *clients* and has since about... oh... f/w 1.2x (I'm not sure). It still does zilch for servers. If you're not on port 21 a LinkSys at both ends is a curse right now.
I suspect something is iffy... like... if the client picks a particular port range things go amuck. Every client can pick any port it wants above 1023 - so funny selections could do it. We just don't know why yet  .
I'd suggest doing PASV mode on your server. This is far more universal. I'll post the info for BPFTP if you like.
[text was edited by author 2001-06-11 21:21:51] |
|
Anon | reply to Anon
Yes I would love that information. And yes I am on port 21. On the router I have port 20-21 forwarded and on BPFTP I have it set for port 21. Thanks for your help,
Greg |
|
Bill_MIBill In MichiganPremium,MVM
join:2001-01-03
Royal Oak, MI
kudos:1 Reviews:
·Comcast
·WOW Internet and..
| BPFTP/LinkSys Setup for full FTP Server Function I hope this helps, Greg. In your case port 20 is not needed. Just port 21 plus the PASV port range needs to be forwarded.
--
Expert Opinions: $5... I Shut Up: $10 |
|
| reply to Anon
Re: FTP works then it doesn't work. WTF???? This is "probably" not a linky problem.
Try ftp from the command line. If ls fails and hangs, then first issue the pasv command, changing the mode of ftp. Then it will work. The ftp server probably changed, not you. You are using the same setup you always did, and suddenly stops? It's probably them.
This symptom is very common for pasv/non-pasv ftp. Try it...
C |
|
Anon | reply to Anon
Here is another tid-bit of info. I was in the mac lab again today, and it connected fine. Bill I tried your information, but that did not work. Why can a mac using IE 5 connect and PC's using WS FTP can't. Could it be the client program? Should I switch to another FTP program? Any suggestions?
Greg |
|
| reply to Bill_MI
Re: BPFTP/LinkSys Setup for full FTP Server Function Excellent explanation Bill, and great examples.
Can you please give a pointer as to where I can get hold of the BPFTP Server software?
Thanks |
|
Bill_MIBill In MichiganPremium,MVM
join:2001-01-03
Royal Oak, MI
kudos:1 | Hi Murray. It's at »www.bpftpserver.com. This server became popular as "G6" or "Gene-6" FTP.
To not sound as partial someone posted Serv-U is or has added the same features we need. |
|
Bill_MIBill In MichiganPremium,MVM
join:2001-01-03
Royal Oak, MI
kudos:1 Reviews:
·Comcast
·WOW Internet and..
| reply to Anon
Re: FTP works then it doesn't work. WTF???? said by GregorySH:
Why can a mac using IE 5 connect and PC's using WS FTP can't. Could it be the client program? Should I switch to another FTP program? Any suggestions?
Greg, it almost has to be the client end now. Once your server can do PASV you became much more universal. Make sure you try PASV mode in WS_FTP... if it still fails something else is wrong. That log can be a good way to tell what's wrong. |
|
Anon | reply to Anon
OK here is the log for the FTP client
connecting to 65.81.204.93:21
Connected to 65.81.204.93 port 21
220 BulletProof FTP Server ready ...
USER Unknowng
331 Password required for Unknowng.
PASS (hidden)
230 User Unknowng logged in.
PWD
257 "/" is current directory.
SYST
215 UNIX Type: L8
Host type (S): UNIX (standard)
PORT 192,168,1,106,4,44
200 Port command successful.
LIST
150 Opening data connection for directory list.
This is where it hangs.
This is the log for BPFTP for the same client. |
|
Anon | (000007) 6/13/2001 11:05:21 AM - (not logged in) (208.236.74.90) > connected to ip : 192.168.1.50
(000007) 6/13/2001 11:05:21 AM - (not logged in) (208.236.74.90) > sending welcome message.
(000007) 6/13/2001 11:05:21 AM - (not logged in) (208.236.74.90) > 220 BulletProof FTP Server ready ...
(000007) 6/13/2001 11:05:21 AM - (not logged in) (208.236.74.90) > USER Unknowng
(000007) 6/13/2001 11:05:21 AM - (not logged in) (208.236.74.90) > 331 Password required for Unknowng.
(000007) 6/13/2001 11:05:21 AM - (not logged in) (208.236.74.90) > PASS ********
(000007) 6/13/2001 11:05:21 AM - Unknowng (208.236.74.90) > logged in.
(000007) 6/13/2001 11:05:21 AM - Unknowng (208.236.74.90) > 230 User Unknowng logged in.
(000007) 6/13/2001 11:05:21 AM - Unknowng (208.236.74.90) > PWD
(000007) 6/13/2001 11:05:21 AM - Unknowng (208.236.74.90) > 257 "/" is current directory.
(000007) 6/13/2001 11:05:21 AM - Unknowng (208.236.74.90) > SYST
(000007) 6/13/2001 11:05:21 AM - Unknowng (208.236.74.90) > 215 UNIX Type: L8
(000007) 6/13/2001 11:05:21 AM - Unknowng (208.236.74.90) > PORT 208,236,74,90,4,11
(000007) 6/13/2001 11:05:21 AM - Unknowng (208.236.74.90) > 200 Port command successful.
(000007) 6/13/2001 11:05:21 AM - Unknowng (208.236.74.90) > LIST
(000007) 6/13/2001 11:05:22 AM - Unknowng (208.236.74.90) > 150 Opening data connection for directory list.
(000007) 6/13/2001 11:05:22 AM - Unknowng (208.236.74.90) > 226 Transfer ok
The server seems to think the transfer went OK, but the client has not recieved the folder list. Can you make heads or tails of this?
Greg |
|
Anon | reply to Anon
Upon suggestion I tried to FTP from the dos prompt. After I did a little research to figure out the commands, I get the same response from it as well. I connect with my user name and password, but it will not list the files in the directory.
Greg |
|
Bill_MIBill In MichiganPremium,MVM
join:2001-01-03
Royal Oak, MI
kudos:1 Reviews:
·Comcast
·WOW Internet and..
| Greg, we're back to that original problem. In both these log cases (and probably Windows commandline ftp) they are not doing PASV *and* apparently something is blocking the ports (1068 and 1035 in the 2 logs) for the data channel. It's an OUTbound for the server but an INbound for the client. Any software firewalls (e.g. ZoneAlarm) involved?
Those 2 logs show what the LinkSys DOES do for clients on port 21. Notice the client sends PORT... 192.168.1.106 but after it translates through the LinkSys the server gets (properly) the 208.236... address. This isn't a problem but just confirmation it's doing what it should.
Are these 2 logs the exact same connection? I suspect not or the PORT-port would be the same (unless the LinkSys shifts it, too).
Again... this client is behind a LinkSys? What f/w? "Working before" is still a puzzle.
EDIT: If that first log is WS_FTP it's definitely not in PASV mode... it's an advanced setting in WS_FTP. There will be no "PORT" in the log, only "PASV".
[text was edited by author 2001-06-13 14:23:33] |
|
Anon | reply to Anon
OK I'm back at you again. I went to my friends house who is behind the same linksys router I have, and guess what. It connects with no problems. He's actually downloading from me right now. Now if I could just get it to work from school in the PC lab. I guess I'll tinker with it somemore. At least I know it is working, but the main reason for the server is so I can get files from school. Thanks for your help.
Greg |
|
Bill_MIBill In MichiganPremium,MVM
join:2001-01-03
Royal Oak, MI
kudos:1 | Greg, the client at the school is important - I'll guess it must do PASV if they have a typical firewall. MSIE has been buggy as hell in doing PASV so I thought I'd mention this. |
|
Anon | reply to Anon
I have actually tried using WS FTP at school as well using both passive and non-passive. They end up doing the same. In passive mode the log from WS FTP says it's transfering data, but nothing every happens. Thanks again for your help,
Greg |
|
