i have this setup running at 3 locations with befsr41 routers and it works perfectly. in theory, a befsr41 with its built-in switch should function no differently than a befsr11 with a hub or switch behind it.
i have 4 machines behind the befsr11 router, connected to it via a hub, at a remote location. the 4 machines have standard private static ip addresses ending in .11, .12, .13, .14. internet access works fine. i need to be able to pcanywhere from our corporate office into each remote PC at different times. pcA 9.2 doesn't allow for easy changes in the ports it uses. it requires registry changes in both the controlled (their) machine(s) and the controlling (my) machine. by default, it uses ports 5631 and 5632. all 4 machines are listening on this port (pcanywhere host is waiting for a connection), and i have those two ports forwarded to 192.168.1.11. this works fine, and allows me to connect to the .11 pc. however, when i want to connect to a different pc, and change the ip address on the forward page, click apply, click continue, and see the new ip address on the refreshed forward page...the router still forwards those ports to 192.168.1.11. this lasts for about 7 minutes, then it finally starts forwarding to the new ip address, and i can connect to the correct computer via pcAnywhere.
the same thing occurs if i remove port forwarding completetely after having it work properly. despite having all 0's and no checks on the forward page, the router will continue to forward those ports for about 7 minutes, then it will stop. i've tested the DMZ, and it seems to have the same delay.
on an interesting note: i set the port forwarding to an internal ip address that does not exist on the network, or to 192.168.1.255 (and waited the 7 or so minutes for the router to begin trying to forward to it). pcanywhere failed to connect, as it should. however, NOW when i change the ip address to an existent internal IP (192.168.1.11), the changes are instantaneous, and i can immediately connect via pcanywhere to that machine.
i have tried firmware version 1.36, 1.42.3, 1.42.7, 1.43, and 1.44 to no avail. i have made sure UPnP is turned off, and tried both settings on Block WAN Request.
ports ip address
router forwarding 5631/5632 to 192.168.1.11
change to "" 192.168.1.12
(or .13, or .14)
or change to 0/0 192.168.1.0
(and uncheck tcp, udp, and enabled)
router continues to forward to 192.168.1.11 for about 7 minutes. (yes, i clicked apply, and got the "settings are successful" screen.) this same symptom occurs when setting the DMZ. after that time, the router will begin forwarding to the new ip address (or stop forwarding altogether, if i have disabled it.)
ports ip address
router forwarding 5631/5632 to 192.168.1.255 (or any ip that doesn't exist on the LAN.)
change to 192.168.1.13
router immediately begins forwarding to 192.168.1.13.
as i said, i have 3 befsr41's at different locations, and they do not suffer from this delay.
i have 4 machines behind the befsr11 router, connected to it via a hub, at a remote location. the 4 machines have standard private static ip addresses ending in .11, .12, .13, .14. internet access works fine. i need to be able to pcanywhere from our corporate office into each remote PC at different times. pcA 9.2 doesn't allow for easy changes in the ports it uses. it requires registry changes in both the controlled (their) machine(s) and the controlling (my) machine. by default, it uses ports 5631 and 5632. all 4 machines are listening on this port (pcanywhere host is waiting for a connection), and i have those two ports forwarded to 192.168.1.11. this works fine, and allows me to connect to the .11 pc. however, when i want to connect to a different pc, and change the ip address on the forward page, click apply, click continue, and see the new ip address on the refreshed forward page...the router still forwards those ports to 192.168.1.11. this lasts for about 7 minutes, then it finally starts forwarding to the new ip address, and i can connect to the correct computer via pcAnywhere.
the same thing occurs if i remove port forwarding completetely after having it work properly. despite having all 0's and no checks on the forward page, the router will continue to forward those ports for about 7 minutes, then it will stop. i've tested the DMZ, and it seems to have the same delay.
on an interesting note: i set the port forwarding to an internal ip address that does not exist on the network, or to 192.168.1.255 (and waited the 7 or so minutes for the router to begin trying to forward to it). pcanywhere failed to connect, as it should. however, NOW when i change the ip address to an existent internal IP (192.168.1.11), the changes are instantaneous, and i can immediately connect via pcanywhere to that machine.
i have tried firmware version 1.36, 1.42.3, 1.42.7, 1.43, and 1.44 to no avail. i have made sure UPnP is turned off, and tried both settings on Block WAN Request.
ports ip address
router forwarding 5631/5632 to 192.168.1.11
change to "" 192.168.1.12
(or .13, or .14)
or change to 0/0 192.168.1.0
(and uncheck tcp, udp, and enabled)
router continues to forward to 192.168.1.11 for about 7 minutes. (yes, i clicked apply, and got the "settings are successful" screen.) this same symptom occurs when setting the DMZ. after that time, the router will begin forwarding to the new ip address (or stop forwarding altogether, if i have disabled it.)
ports ip address
router forwarding 5631/5632 to 192.168.1.255 (or any ip that doesn't exist on the LAN.)
change to 192.168.1.13
router immediately begins forwarding to 192.168.1.13.
as i said, i have 3 befsr41's at different locations, and they do not suffer from this delay.