This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
I've had a WNR2000v2 working for some time. I recently decided to do a firmware upgrade and went from firmware version 1.0.0.40_32.0.54 to the current version 1.2.0.8_36.0.60.
During the firmware update, it stopped reflecting my Port Forward rules, so I attempted to re-create them. The firmware then told me the ports were already in use, so I paper-clip fixed it and brought it back to default settings.
Now however, it does not forward TCP types. If I create a new custom service, select TCP/UDP, select the destination IP address and click save, it shows it worked. However if I then select the very same custom service and edit it, it only displays "UDP". TCP only things, such as port 3389 (RDP) do not resolve externally.
> rolled back to version WNR2000v2_V1.2.0.6_36.0.58NA and everything > just magically worked. [...]
Thanks for the report. Welcome to the wonderful world of Netgear firmware quality control. (It's under such tight control that hardly any of it escapes?)
> [...] However if I then select the very same custom service and edit > it, it only displays "UDP". [...]
Either the report is wrong, or the underlying setting is wrong.
> [...] TCP only things, such as port 3389 (RDP) do not resolve > externally.
Sounds as if the underlying setting is wrong. I can't see your actual port-forwarding rule. Did you do everything else right? External and internal ports? Target IP (static or reserved dynamic)? If all should be well, then I'd try some older firmware version(s), and see if I could find one which works.
Visit http://netgear.com/support , put in your model number, and look for Downloads. (For older versions, under Firmware and Software Downloads, look for "View Previous Versions".) Find the kit(s). Download the kit(s) you want. Read the "Release Notes" file for instructions.
Thanks for the reply, and sorry for the delay as I wanted to actually try your suggestion. But with holidays and traveling, pushed it off until I was home and I didn't want to answer "Did you do everything else right?" the way the average internet person would. But they were entered correctly, just wasn't accepting the change.
One odd thing I noticed later, is it could be set to TCP or UDP, just not TCP/UDP. Which would have been a temporary viable work around.
Thanks for suggesting rolling back the firmware. The hardware I work on actually can not go backwards, so I completely forgot about this as an option.
I rolled back to version WNR2000v2_V1.2.0.6_36.0.58NA and everything just magically worked. I could edit the old rules to be TCP/UDP, save and they properly got forwarded. And fortunately all the settings were preserved.
> rolled back to version WNR2000v2_V1.2.0.6_36.0.58NA and everything > just magically worked. [...]
Thanks for the report. Welcome to the wonderful world of Netgear firmware quality control. (It's under such tight control that hardly any of it escapes?)
