DrDoug: You shouldnt HAVE TO name your server, I am sure there is a default G6/BPFTP uses, thats just to personalize.
The BWR should be located at the bottom of the advanced tab page along with 4 other disable/enable options.
Basicaly Doug, I wouldnt mess with the BWR until you get a little more acquainted with the router some. For the time being, unless you have some reason why you want to use PASV mode, just turn off the pasv mode on the client FTP, and you will connect without the socket error problem. Linksys has had this problem with pasv and port 21, and really using pasv mode entirely with the router. They are working on this solution, SLOWLY tho, along with a few other minor uses that not alot of ppl run into, and until they have a largeer # of ppl complaining, I dont think they are worried about getting off their butt anytime soon. I have not went up to 140 or higher as I have the motto of many, "if it aint broke, dont fix it". After you have tried this, and if it still doesnt work, go back to firmware 139 by visiting the ftp site @ ftp.linksys.com/pub/befsr41/ and search for the firmware.
a direct link to firmware 139
ftp.linksys.com/pub/befsr41/befsr-1-39.zip
**NOTE** when applying firmware, all settings will be wiped out, you will need to enter your router config info again ***
For getting an internal IP, and having it to stick to a certain computer ALL the time, just go to the network settings on that particular client computer and enter an assigned IP such as 192.168.1.2 and the default gateway (which is the gateway of the router, not your modem) 192.168.1.1 and your DNS server(s) provided by your ISP, most the time
Then you can go to the port forwarding tab, and then specify the 192.168.1.2 and the tcp port of 21. Even enabling the DMZ host for that client will not solve the Pasv socket issue, you will still need to turn off PASV
FTP and the LinkSys Router
Running FTP clients and servers with the LinkSys routers is a real quagmire. The FTP protocol is an old and strange one to deal with. Here's my findings (mostly based on f/w 1.37-9):
FTP CLIENTS behind the LinkSys - Standard Port 21
The LinkSys firmware actually does address translating of FTP commands (the PORT command in particular) and forwards accordingly. To connect to standard port 21 FTP servers on the internet, full functionality for FTP clients should work.
FTP CLIENTS behind the LinkSys - Non-Standard Ports
Unlike standard port 21, the LinkSys does NOT translate the FTP "PORT" command on other ports. The only way a client behind a LinkSys router can connect to an FTP server on a non-standard port is to use PASV mode.
FTP SERVERS behind the LinkSys - Any Port
Just the opposite of the client case, when a server is behind the LinkSys it can NOT do PASV mode for the outside world. Notice the irony - if both client AND server are behind LinkSys' AND non-standard ports are used, no connection can be made easily. Standard Port 21 is the only quick way.
Why can't clients and servers connect?
In the case when the CLIENT is behind the LinkSys, and PASV is not used, the client may use a PORT command to send an address. Only on standard port 21 does the LinkSys translate the LAN address to the needed WAN address.
In the case when the SERVER is behind the LinkSys, and the client uses PASV, the server must respond to the PASV command with an address. The LinkSys will not translate this reply properly so the other end gets the server's LAN address instead if the needed WAN address.
Note: Serv-U has a setting "IP For Passive Mode" that gets around this - but that's only half the battle.
Can I run an FTP server behind a LinkSys that covers all cases?
I have, but with mixed results. Here's what I did:
1). Use Serv-U and set the "IP For Passive Mode" to your WAN address.
2). Put the FTP server in the DMZ.
3). You can forward the FTP port (21 or whatever) but this is redundant since the box is in the DMZ.
That's for servers, what about clients?
The LinkSys handles clients well as long as it's standard port 21. Other ports I know of no way other than you MUST use PASV mode.
What is PASV mode?
PASV (passive) mode was designed for clients behind firewalls. When NOT using PASV mode the client actually becomes a server for the data channel (that's right!). Since firewalls typically prevent this, PASV mode is used and this switches the data channel to be served by the server side.
Browsers (like Netscape and MSIE) may use PASV mode exclusively but it's really been pot-luck. I found MSIE 5.5 has a setting that seems to lie about what it uses. Most ftp programs (like CuteFTP and WS_FTP) can be set to run PASV or not.
See what I mean about FTP being such a strange protocol?
What does that "PORT" command do?
Clients *may* use the PORT command when NOT running PASV to tell the other end what address and port they will be listening on. Again, the LinkSys only translates this command on standard port 21 (else, the server gets your LAN address which doesn't work!).
How can I tell what's happening in my system?
Many clients and servers can log or view the FTP session. Take a look and you may see when things go bad. Chances are they are after a PORT or PASV command.
Is there any hope for FTP servers and clients on the LinkSys?
LinkSys is trying SPI (Stateful Packet Inspection) techniques. It's possible they will start translating ALL of the FTP commands. Currently, they only do client commands (PORT) on port 21. Time will tell if they actually add other ports and the SERVER commands (PASV), too.
All Comments, Corrections and Bitches Welcomed.