I'm also having problems getting one of my 2 x 320L's registered on the mydlink site via the sharecenter setup wizard.
I originally added one of my 320l's without any problems, but since then I've purchased a 2nd box and updated the firmware on both to 1.02
Can anyone offer any suggestions where I'm going wrong based on the details below.
My network is as follows...
Cisco ADSL2+ modem (192.168.1.1)
--cable--> (192.168.1.100) ASUS RT-N56U (192.168.2.1)
--cable--> 1 x PC (192.168.2.250)
--cable--> 320L #1 (192.168.2.200)
--cable--> 320L #2 (192.168.2.205)
--Wi-Fi--> 1 x PC (192.168.2.2)
--Wi-Fi--> 1 x D-Link Bridge (192.168.2.200)
--cable--> 1 x TV (192.168.2.140)
--cable--> 1 x Raspberry Pi (192.168.2.141)
I've also got an assortment of tablet's and mobiles connected via wi-fi but each has it's own IP using DHCP, so no conflicts.
Normally I run a small webserver via Apache on my PC which is connected to my ASUS router, so I know the port forwarding on port 80 is ok from the modem to the router to the PC.
For the sake of getting 320l #2 registered I've disabled Apache, removed port fwd for port 80 from the ASUS router to my pc and replaced it with port fwd to port 80 of 320L #2
The Cisco router forwards port 80 to 192.168.1.100 which is the ASUS router
The ASUS router forwards port 80 to the 2nd NAS box I'm having problems with
I've tried to run the setup wizard from the mydlink site but when it comes to the area regarding DDNS I get stuck, if I say no i don't want to configure DDNS the app crashes, if I try to proceed with configuring DDNS it can't see my device on port 80.
But If I type in my DDNS hostname into my web browser I can access the login page of the 320L and authenticate without any issues.
Things I've tried so far.
I tried entering my dlinkddns details into the setup wizard but it keeps failing.
I tried entering the ddns details directly into the 320L via Network Management but get error - Updated Failure
I then decided to configure DDNS in the ASUS router, router appears to accept the details, but the setup wizard still fails.
I also tried configuring DDNS in my Cisco ADSL modem, again it's accepted but again this fails when running the setup wizard.
each time the error message in the setup wizard advises the same thing
Unfortunately we cannot update the DDNS account status. Please:
1. Check your internet connection to your ShareCenter.
2. Open port 80 in your router.
3. Check the DDNS account settings.
I've then attempted to update the firmware again but no joy, same issues persists.
as I mentioned earlier If I select no during the setup wizard to the question do I have a DDNS account the software asks if I want to apply for a DDNS account now, if I say no the software crashes with error below.
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ArgumentOutOfRangeException: InvalidArgument=Value of '97' is not valid for 'SelectedIndex'.
Parameter name: SelectedIndex
at System.Windows.Forms.ComboBox.set_SelectedIndex(Int32 value)
at Wizard.Form1.get_timezone(Int32 len, SByte* buf_p, SByte* rcv_buf)
at Wizard.Form1.send_get_timezone_pkt()
at Wizard.Form1.backgroundWorker_get_info_RunWorkerCompleted(Object sender, RunWorkerCompletedEventArgs e)
at System.ComponentModel.BackgroundWorker.OnRunWorkerCompleted(RunWorkerCompletedEventArgs e)
at System.ComponentModel.BackgroundWorker.AsyncOperationCompleted(Object arg)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.7905 (win9rel.050727-7900)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
Setup Wizard
Assembly Version: 1.0.4497.29888
Win32 Version: 1.0.0.0
CodeBase: file:///D:/Users/Thomas/Desktop/dlink/Setup%20Wizard.exe
----------------------------------------
msvcm90
Assembly Version: 9.0.21022.8
Win32 Version: 9.00.21022.8
CodeBase: file:///D:/Users/Thomas/Desktop/dlink/msvcm90.DLL
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.7905 (win9rel.050727-7900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.7905 (win9rel.050727-7900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.7905 (win9rel.050727-7900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.7905 (win9rel.050727-7900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Accessibility
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.7905 (win9rel.050727-7900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
I've tried various compatibility modes within windows 8.1, windows 8 and also tried from another PC running Windows 7, each time getting the same sequence of errors.
Wondering if it's worth trying to go back to the previous version of the firmware?
or for the sake of getting the 320L registered if I should just connect it directly to the cisco modem, then if successful move it back to the ASUS router
I've got the original 320L #1 up and working with no problems, it's registered with mydlink, I can access the files on it even though there is no DDNS configured for the device and it's currently connected to the ASUS router with no port forwarding etc... but that was setup on the old firmware with a slightly different network configuration.
I'm kinda at a loss but now I see there are so many others reporting difficulties it's sorta good to know I'm not alone.
Update:... I've fixed the issue I was facing. when you goto mydlink.com and select support - storage - dns320l you can see the firmware available and a note advising you need to use the latest setup wizard. the problem is the windows setup wizard located on that same page is still the old version.
If you are using 1.02 firmware and having issues with the setup wizard in any way then go here and download the latest setup wizard to complete this process.
http://www.dlink.com.au/tech/download/download.aspx?product=DNS-320L&revision=REV_A&filetype=Firmware
the file I downloaded is named DNS-320L A1 Setup Wizard v1.0.2.3(DI) 02252013.zip (69.25 MB)
appears the dorks at dlink don't know how to update their own website with the correct information... no great surprise really.