• February 26, 2025, 09:19:18 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: Can't Login to config page after update to 1.09 even after reset  (Read 3028 times)

aionee

  • Level 1 Member
  • *
  • Posts: 1
Can't Login to config page after update to 1.09 even after reset
« on: January 23, 2011, 08:32:42 AM »
Hi guys,

I've read most if not all of the topics related to this topic and most of the time it can be fix with a reset.
But I've tried that but still I can;t login to the config page. As usual when I click the config button I am
forwarded to "http://192.168.0.32/goform/formLogin" but it is an empty page.

I've tried reseting with the power unplug and with the unit still on. Both methods doesn't fix this issue.

I just started to use this unit after a long time and have just purchased 2 Hitachi 2TB hdd for this.
Before this happened, this unit is running on firmware 1.03.

Could it be the firmware is somehow corrupted? Are there any way to downgrade or reflash the firmware without accessing the WebGUI?

Any help from the gurus here is highly appreciated.



« Last Edit: January 23, 2011, 08:36:55 AM by aionee »
Logged

dosborne

  • Level 5 Member
  • *****
  • Posts: 598
Re: Can't Login to config page after update to 1.09 even after reset
« Reply #1 on: January 24, 2011, 12:57:54 PM »
What browser version are you using to access the admin page? I'd suspect something on your PC rather than something in the NAS. Firewall for instance.
Logged
3 x DNS-323 with 2 x 2TB WD Drives each for a total of 12 TB Storage and Backup. Running DLink Firmware v1.08 and Fonz Fun Plug (FFP) v0.5 for improved software support.

D-Link Multimedia

  • Poweruser
  • Level 7 Member
  • **
  • Posts: 1066
    • D-link Systems, Inc.
Re: Can't Login to config page after update to 1.09 even after reset
« Reply #2 on: January 24, 2011, 05:09:40 PM »
Why are you receiving a 192.168.0.32 address? That is the default address when no IP is detected through DHCP. Is that the same IP scheme your network is running? Is this default connected directly to your PC or through a router? If it is going to a router you should be receiving a proper IP address otherwise if it is a direct connection make sure your IP is statically set on your pc in the same subnet and IP range.

A secondary step is to make sure that you also test without the drives inserted into the device. If you can get into it that way then atleast we have a starting point.
Logged