Ok. I have 3 computers connected to my Linksys BEFSR41 Router which is currently running 1.42.6 Firmware.
Now 1 of the computers runs my FTP Server. Another computer I use for IRC so I need it to be able to DCC send/receive files.
In the DHCP Clients Table it would label any given computer either 192.168.1.100, 192.168.1.101, or 192.168.1.102. Depending on when the computers were shut off and on, the IP would change for any given computer. So sometimes the FTP Server would be 192.168.1.100...the next day it might be .101.
Now I obviously went into Port Forwarding & forwarded Port 21 to ALL of the 3 possible IP addresses (.100 to .102). I did the same for the IRC DCC port range.
However today my FTP Server was not accessible for some stupid reason. I found out it was because my FTP Server's IP changed and in the Port Forwarding section the computer was in the middle of the list. Once I swapped it's IP address to the top of the list it worked just fine!
This NEVER happened before. Where I put the IP's on the Port Forwarding list never used to matter.
Currently I found how to setup a Static IP in Windows XP from some website & did that to the FTP Server. Problem is, when my Cable Modem service changes their DNS numbers I'm screwed until I change them manually.
What I'm guessing is that the DNS change at my ISP will happen a lot less often than my internal network changing the local IP numbers (which would cause me to keep manually bumping the FTP Server's Local IP number to the top of the Port Forwarding list).
Here's a funny sidenote that's baffling me. On my 2nd computer....the one that needs access to DCC in IRC....I found that DCC sending & receiving will function NO MATTER WHERE I put the lousy computer's Local IP number in the Port Forwarding list!!! Go figure.
Does anyone have a permanent solution for this? The ONLY thing I can think of is that the newer firmware is causing this.
Would going to an older version fix things? Am I overlooking something?
Thanks for any help you can give.
Now 1 of the computers runs my FTP Server. Another computer I use for IRC so I need it to be able to DCC send/receive files.
In the DHCP Clients Table it would label any given computer either 192.168.1.100, 192.168.1.101, or 192.168.1.102. Depending on when the computers were shut off and on, the IP would change for any given computer. So sometimes the FTP Server would be 192.168.1.100...the next day it might be .101.
Now I obviously went into Port Forwarding & forwarded Port 21 to ALL of the 3 possible IP addresses (.100 to .102). I did the same for the IRC DCC port range.
However today my FTP Server was not accessible for some stupid reason. I found out it was because my FTP Server's IP changed and in the Port Forwarding section the computer was in the middle of the list. Once I swapped it's IP address to the top of the list it worked just fine!
This NEVER happened before. Where I put the IP's on the Port Forwarding list never used to matter.
Currently I found how to setup a Static IP in Windows XP from some website & did that to the FTP Server. Problem is, when my Cable Modem service changes their DNS numbers I'm screwed until I change them manually.
What I'm guessing is that the DNS change at my ISP will happen a lot less often than my internal network changing the local IP numbers (which would cause me to keep manually bumping the FTP Server's Local IP number to the top of the Port Forwarding list).
Here's a funny sidenote that's baffling me. On my 2nd computer....the one that needs access to DCC in IRC....I found that DCC sending & receiving will function NO MATTER WHERE I put the lousy computer's Local IP number in the Port Forwarding list!!! Go figure.
Does anyone have a permanent solution for this? The ONLY thing I can think of is that the newer firmware is causing this.
Would going to an older version fix things? Am I overlooking something?
Thanks for any help you can give.