D-Link Forums

The Graveyard - Products No Longer Supported => DIR-655 => Routers / COVR => Beta Code! => Topic started by: painless on April 02, 2009, 03:05:37 PM

Title: BUG - 1.22B05 Port Forward Settings Dissapear
Post by: painless on April 02, 2009, 03:05:37 PM
When I set the port forwarding settings, and reboot the router.... they are gone. They seem to work for a while, but eventually they stop working.

eg. set port 11111 in tcp/udp for bittorrent, then reboot router as it asks....

then check utorrent for proper port forwarding.... good.... but not listed in port forwarding area of router settings

a day or two later, and the forwarding doesn't work anymore.

Title: Re: BUG - 1.22B05 Port Forward Settings Dissapear
Post by: lotacus on April 03, 2009, 02:41:34 PM
and who are all the people that have access to the router?

My port forwarding have not ever "disappeared".
Title: Re: BUG - 1.22B05 Port Forward Settings Dissapear
Post by: HazardX on April 05, 2009, 08:47:19 PM
Maybe you're system's IP changes in those few days?

Try either using a static address on your PC, or static in the router.

Might help, or you aren't being clear about what exactly isn't working anymore beyond "it no-worky but did before!"
Title: Re: BUG - 1.22B05 Port Forward Settings Dissapear
Post by: painless on April 06, 2009, 09:15:59 AM
I am the only person with access to the router. All private IP's are set with DHCP reservations on my network; so all machines keep their IP's. My network consists of 2 laptops, 2 desktops, XBOX 360, PS3, and an iphone. The port forwarding is set for the desktops for certain applications, and for XBOX live on the 360.

The problem is that the router isn't keeping any of the port forwarding settings, I set them, reboot router, and they are gone.... every time. When I check to see if the ports are forwarded, they usually are (yet don't say so on the router)... but this only lasts for a little while, and then the forwarding doesn't work anymore.

I am going to try going back to 1.21 tonight if I find time, or possibly re-do the 1.22B05 upload to the router to see if it solves anything.