Wireless Network - problem with FTP port forwarding

Me again with yet another Wireless Router problem. Since you guys solved my problem last time I thought I would give it a try again.

I used to run Bulletproof FTP server from behind my wired router without a problem..just configured it to forward the ports 20 and 21. Now when I try this with my new wireless router (Linksys Wireless-G) it doesn't seem to work at all.

If you guys could walk me through some settings again, that'd be great. This is frustrating the hell out of me. (Been trying to fix this on my own since my last post here)

 

New Thread??

Sorry, should I have started a new thread with this?

 

I took care of making it a new thread for you. No problem.

Are you using static addresses in the wireless LAN?

What sort of privacy keys? WEP? others?

How are you setting for pure inbound traffic (not a response to one of your PCs) to pick up the key information?

 

My settings

Under my basic setup, I have it set to obtain an IP automatically. My local IP address is listed as 192.168.1.1

Under my security settings I have not made any changes to the defaults. I have various settings that can be changed - Filter IP Address Range and Filter Port Range which I believe is to limit access to the internet via entering IP addresses. I also have WAN settings here that I have left at default:
Block Anonymous Internet Requests is set to enabled
Filter Multicast is disabled
Filter Internet NAT redirection is disabled
Filter Ident (Port 113) is enabled
All VPN Passthrough settings are enabled

Under my Application and Games settings,for Port Range forwarding this is where I have enabled Ports 20 and 21 for the IP address 192.168.1.1 for Bulletproof.

Port Triggering, UPnp settings and DMZ settings I have left at default.

When I turn the Bulletproof server on, it gives me this message: 12/16/2004 FTP Server On-line : IP(s) 192.168.1.101, on port 21

Hope this gives you some clue. Thanks again.

 

I don't work with wireless at all and am sorta behind the power curve when it comes to understanding all I need to know about it. Given that, a couple of thoughts come to mind.

Block Anonymous Internet Requests is set to enabled

Unless you are set to require folks to connect with a username and password, they will default to Anoymous when trying to connect. I suspect the block you have active will stop them getting in.

I'm not sure what the privacy defaults with your equipment are but if you have any privacy active, a user will need some way to receive validation from you before they can connect. If you aren't set that way than any other wireless systems wandering near your house could jump on your network. You need to take a good look at your documentation about privacy keys and how they operate.

Most common is WEP I think. From Here

 

To keep you posted

Just to keep you posted...
Block Anonymous Internet Requests is set to enabled - tried disabling this with no luck.

All my users connect with a username and password and as far as I can tell there are no privacy concerns blocking them from connecting. I hadn't set any and can't see in my documentation that any was set by default. (Chances of someone hopping on my network are slim as I live out in the boonies but nonetheless will change that after I sort out this mess.)

I have found a few articles online regarding similar problems so I think it lies within the port forwarding and open ports on the router.

I am also a newbie with the wireless stuff so we will all learn together I suppose. I just don't understand how the wireless vs wired can be so different with regards to the Bulletproof program.

I will keep you posted on the results of my experiments with it in case someone out there has the same issues.

 

IP keeps changing

Well, I finally got things working and felt pretty silly when I figured it out. Turns out that the IP address of my router kept changing. When I typed in ipconfig to double check on it, it had changed from 192.168.1.100 to 192.168.1.101 and I didn't realize it. Changing my IP in my port forwarding section of my router setup solved the problem.

The IP changing keeps happening, however...I have to keep checking it and changing my port forwarding settings.

Weird. I had assumed it would always be the same.

 

This will happen if you are turning both machines off and on at different times and your router is the DHCP Server. The first one on will have the 100 at the end of the IP addy when it is restarted.

 

Hmmmm

Totally makes sense now. We are always turning machines off and on at various times. Thanks for clearing it up. One question, though...if we have only 3 computers connected to this router and the first IP usually ends in 100, how can I possibly get an IP ending in 104 (which I've had once or twice)!!??

 

You can tell the router to increase the IP lease time to a really long time like 9999 minutes. This way in effect, all of your DHCP clients practically get a static IP. However, if you only have a few computers in your LAN and you do not play around with their IPs alot, I highly recommend that you take the time to give each client a static IP.