• May 19, 2025, 01:33:53 AM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Author Topic: Numerous problems with new DIR-655  (Read 3608 times)

Yanta

  • Level 2 Member
  • **
  • Posts: 66
Numerous problems with new DIR-655
« on: March 08, 2010, 11:07:42 PM »

I rencently purchased a DLINK DIR-655 and I am having multiple problems. I am running 1.21WW, which is apparently the latest firmware for Australia. The product is 2 weeks old.

(1). To make any changes I have to turn off syslog otherwise router crashes when saving any changes.
(2). My PS3 won't sign in to the playstation network. After mulitple attempts it will sign in, but will drop out a couple of minutes later.
(3). Every day I have to reset the router (sometime more than once a day). It appears that any client for which any access control rule exists can't access the Internet.
(4). The router appears to randomly reset during the night for everyone, including clients for which no access rules exist
(5). When defining a rule that spans AM and PM it says "invalid time format". For example, I want to block ports 20 and 21 from 6am to 6pm.
(6). The router seems to be picky about which web filters it will ignore and which it will enforce. For example, "****" will be enforced "but "sex" some times is enforced, and it ignored at others times.

I have reset everything multiple times and recreated rules from scratch. The retailer refuses to offer a refund and will only exchange a DIR-655 for a DIR-655. I suspect this is not a fault particular to this specific router, but for all DIR-655s???

Any suggestions on what I can do?

D-LINK sent me a firmware update 1.21WW Beta11. If my Firmware is 1.21WW wouldn't it be later than a beta of the same version number??

Tanya

Logged

Trypt

  • Level 1 Member
  • *
  • Posts: 13
Re: Numerous problems with new DIR-655
« Reply #1 on: March 09, 2010, 11:30:57 AM »

Try a different firmware, the problems you describe shouldn't be happening, they are most likely caused by bad programming of the device.
Logged