D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-320 => Topic started by: boyshawn on May 29, 2014, 08:40:33 AM
-
I just disconnect my NAS from my router. When I run the ShareCenter Setup Wizard, I was stuck at the page where it prompt me to create a new password for my NAS. No matter if I leave the field for the password blanks or not, there is an error message which write, "set password fail!"
Is there any restriction that that we need to set a password that's not blank. And beside that the password must contain at least 5 - 16 characters, is there any other restriction?
Anyone encounter the problem before?
-
You disconnected your NAS from your router so how is it connected to your network?
If you are using a direct cable connection to your PC have you set the networking of your PC to fixed IP address in the same subnet as the default IP address of the NAS?
-
You disconnected your NAS from your router so how is it connected to your network?
Sorry I mean I disconnected and reconnected it back to the router.
If you are using a direct cable connection to your PC have you set the networking of your PC to fixed IP address in the same subnet as the default IP address of the NAS?
What do you same IP address in the same subnet as the default IP address of NAS? My NAS current netmask is 255.255.255.0 and my IPV4 is automatically detected.
-
Assuming you are using windows on your PC download a copy of Netscan (google for it), unzip it and double click on either the 32 bit version or 64bit version depending on your OS 32 or 64 bit. Fill in the range of IP addresses (example: 192.168.0.1 192.168.0.254) click on scan. It will then scan your network and list the IP addresses of everything there.
Once you know the IP address of your NAS start your browser with http://nas-ip-address/ (example http://193.168.0.32/) this should bring up the login screen. Go to 'Management' -> Account Management -> Admin Password and fill in what you want as password (it is case sensitive) and don't forget to Save Settings when you have finished.
By going directly to the web interface you bypass the wizard that can be problematic in some circumstances.
-
I have use Netscan by CreaSoftware, which I have scan from 192.168.0.0 to 192.168.1.254 and there is no response.
When I have use DNS-320_A1_FW_v1.00_D-Link_Storage_Utility_v5.0.0.0, the NAS detected was 192.168.1.44. But when I enter it on my browser, I was not able to enter the Web-based configuration page. The response from my browser is "The connection has timed out"
-
For a start why are you trying to mix two subnets (192.168.0.xxx and 192.168.1.xxx)? This will NEVER work.
To find out what subnet your network is on check in your router manual (it is usually 192.168.0.xxx or 192.168.1.xxx) when you know this put in to Netscan 192.168.xxx.1 and 192.168.xxx.254 (the xxx is the subnet) and click on scan. This should find your NAS.
Once you know the IP address put it into your browser and you should get the login screen. If you switch the NAS off at any time you will most probably find it has a different IP address when you switch it on again because you are allowing the DHCP server to set the IP addresses on your network.
-
Sorry for the mistake. This is my first time using Net Scan. I have scanned the first few subnet of the IP range, and manage to find the NAS.
(http://i62.tinypic.com/m7rozk.png)
But when I key in the IP address into the browser, the browser response is "Unable to connect". However, there is response when I ping 192.168.2.44 in my command prompt.
-
OK, we are getting a bit further along and nearer to solving the problem.
The fact you can ping the NAS and get a response indicates that we need to find out what is blocking the browser. Do you have a firewall on your PC or router that could be doing that? I know of several that block access to the local network unless a specific IP address or a range of addresses are opened.
The other thing is to try using another browser as that sometimes works - not all browsers are created equal and/or respond the same way to standard HTTP output.
-
The fact you can ping the NAS and get a response indicates that we need to find out what is blocking the browser. Do you have a firewall on your PC or router that could be doing that?
Beside the default Windows Firewall, I have used COMODO Internet Security Premium. I have tried to access the NAS after I disabled all the component of COMODO Internet Security, I still get back the same response from Firefox browser.
The other thing is to try using another browser as that sometimes works - not all browsers are created equal and/or respond the same way to standard HTTP output.
I have tried with both Chrome and Internet Explorer. Both do not work. Then I run the Windows Network Diagnostics
Problems found:
"The remote device or resource won't accept the connection."
(http://i59.tinypic.com/v5g6kx.png)
-
(scratches head) That appears rather odd.
If you run Netscan with 192.168.2.0 to 192.168.2.254 does it show the IP of your PC? Also what is the DHCP range as set by your DHCP server (usually the router)?
Reading through the complete thread I find it strange that the find utility sees the NAS as 192.168.1.44 yet Netscan finds it as 192.168.2.44 which leads me towards thinking there is something strange going on with your network.
Could you list the make and model of your router (I assume it is an Asus from Netscan results) and I will check our documents files to get the specifications of it.
-
If you run Netscan with 192.168.2.0 to 192.168.2.254 does it show the IP of your PC? Also what is the DHCP range as set by your DHCP server (usually the router)?
Yes, IP of my PC show up as 192.168.2.147. How do I check the DHCP range of my DHCP server?
Could you list the make and model of your router (I assume it is an Asus from Netscan results) and I will check our documents files to get the specifications of it.
I am using ASUS RT-N56U.
This is my D-Link Storage Utility screen:
(http://i60.tinypic.com/1zfhrmq.png)
-
OK, next thing.
As far as I can see the Asus router is just that a wireless router that needs a modem of some sort that connects it to the internet. If that is the case then therein will be the problem. Both the modem and router are acting as DHCP servers and you can have only one on a network subnet.
Since the default IP for the router is 192.168.1.1 and you are seeing 192.168.2.xxx it would appear that the internet modem is on the 192.168.2.xxx subnet. With that setup you take pot luck in trying to get anything to work.
If that is in fact the case you need to switch off one of the DHCP servers. Which one you do depends on how easy it is to do (with the Asus router it is, after you have logged in, Advanced Setting -> Lan -> DHCP Server -> Enable = No).
-
Okay I do not quite get what you mean here, but I have tried the method you recommended: to disable the DHCP Server on my ASUS router. The result is that now the NAS cannot be detected at all, by both the D-Link storage Utility and Net Scan.
Some additional information, I did have a modem in use, which is provided by my internet service provider, Pace 2Wire 5012NV-002.
My router was reset recently, and in its latest firmware. The only configurations were setting password for WIFI and turning on some basic security features.
As for the NAS, nothing was changed ever since it has been out of power and back in use.
-
This is getting more puzzling by every post.
According to the information I have been able to find the default IP address for your modem is 192.168.1.254 which puts it in the same subnet as your router (192.168.1.1 default). As an aside it is the first three sets of numbers in the IP address that must be the same (192.168.1 in the default case) otherwise the network stops working.
Your basic setup should look something like this:
Internet -> Modem -> Router -> NAS
¦-> PC
¦ -> PC
Now either the Modem or Router should be the DHCP server and if you use the defaults your subnet will be 192.168.1.xxx that is assuming a wired connection between the Router and NAS and Router and PC. If you are using a wireless connection to the PC then there are other factors to consider like your PC could be picking up an IP address from someone else wireless, something I have seen happen in a block of apartments (it was OK for getting on to the internet but no way could they see other PCs on their network).
Another thing you might like to download the SoftPrefect version of Netscan as it is the most up to date (updated a few weeks ago) and see what you get on both the 192.168.1.xxx and 192.168.2.xxx subnets.
If this isn't solved by Monday I will ask my guys in the service section if they have any other ideas.
-
If you were to refer to the setting from the modem, it look like that:
(http://i57.tinypic.com/vxhsfa.png)
Physically, it's as such:
Internet -> Modem -> 1st Router -> Terminals
-> 2nd Router -> NAS
-> Desktop
-> Printer
Given my limited knowledge, the NAS will be limited to the network of the 2nd router.
Update 1:
Miraculously, I am now able to access the NAS via my Windows Explorer, when I click SoftPerfect Network Scanner, and entering my credential (user and password). But I am still not able to access the web interface when I key in the IP address.
-
This appears to get more complicated as we go on.
Please confirm the following:
1) Modem to internet is Pace 2Wire 5012NV-002.
2) One router is ASUS RT-N56U.
3) One router is TL-WR1043ND.
4) Both routers are connected to the Modem.
5) The Modem is the DHCP server and is serving IP addresses in the 192.168.1.xxx subnet range (if not what set of IP is it serving?).
6) The DHCP servers on both the routers are switched off.
7) The NAS is connected to one of the routers.
That may look complicated but it is in fact a fairly simple arrangement. The only thing that can make it complicated is if there is more than one DHCP server or a wireless connected computer is getting its IP address from a wireless router or access point on a different network.
The fact you are able to see the NAS shows it is working, we just need to find out why parts of it are being blocked.
-
Hi guys,
I just looked up the Pace 2Wire 5012NV-002. Unless I am missing something, this is an ADSL modem /router combo unit. So, that means there are in fact 3 routers on this system, apparently with at least 2 of them, possibly all three enabled as routers. If that is the case, it is a wonder that you can connect to anything.
If I were trying to sort this out, I would try just using the Pace as the main router and using the ASUS as an AP. There are directions on the net for this, basically, you turn off DHCP on the ASUS, UPNP, and most everything else but leave the wireless enabled with whatever settings and most importantly, you have to assign the ASUS an IP that is on the Pace's routing table but is currently unused. When done run an ethernet cord from the PACE'S LAN to an ASUS LAN. I would also just disable any wireless on the PACE unit. You could leave it enabled by using the same SSID but different channels. If you can get this working, you could add the third router as an AP also in a similiar fashion. Good luck
-
Hi Cable2,
That is what I was leading up to once it is confirmed that what I listed is correct. Since they all default to either the 0 or 1 subnet but a 2 subnet appears I think there are outside influences at work as well.
-
Please confirm the following:
1) Modem to internet is Pace 2Wire 5012NV-002.
2) One router is ASUS RT-N56U.
3) One router is TL-WR1043ND.
Yes
4) Both routers are connected to the Modem.
Yes, both routers are connected to the Modem
5) The Modem is the DHCP server and is serving IP addresses in the 192.168.1.xxx subnet range (if not what set of IP is it serving?).
How do I check that?
6) The DHCP servers on both the routers are switched off.
I do not have access to the DHCP servers to TL-WR1043ND configuration setting. Is there a way to check that that if I am not access the configuration page?
7) The NAS is connected to one of the routers.
Yes, It is connected to ASUS RT-N56U.
-
Hi boyshawn,
To sort this out, the first thing to do is get the default ip address and password for each of your routers. The TL-WR1043ND, is 192.168.1.1, user: admin pw: admin, it is the same for the ASUS. The ip address for the 2 Wire is 192.168.1.254 and you already know the user and password. First check the IP range on the 2 Wire, it will tell you this somewhere in the settings. Then write that down and try to make note of a couple of the IP addresses in that range that are not used. You will give these unused addresses to the other 2 routers. The problem is that with them wired together as you have them, you may not be able to reach each of the other routers. The temporary solution is to connect them one at a time directly to your pc with an ethernet cable and then use the browser to log in. My best guess, unless you did something very unusual on setup the 2 Wire is set to do the DHCP assignments so work on the TL-WR1043ND first, connect from your pc to one on the LAN ports not the WAN port and login, if necessary, do a reset on this and it will go back to the defaults. Once in, you basically want to assign one of those free ip addresses from the 2 Wire to the router then basically turn off almost everything else except the WIFI. Here is a link for an example of how to do that
http://www.smallnetbuilder.com/wireless/wireless-basics/30338-how-to-convert-a-wireless-router-into-an-access-point. You may find more specific directions by googling turning xxx router into an AP.
Then do the same thing with ASUS.
You really only need one of these routers using WIFI especially if they are physically close. If that is the case, I would use the ASUS as the single WIFI source as it is dual band and turn off the WIFI on the other 2.
I still have no clue as to why you have 3 routers, it's kind of like having a car with 3 steering wheels and at least 2 drivers...it's not going to work very well. If not doing something extraordinary, you would be better off with one router and an 8 port switch. I hope this might help but I am afraid it might be a bit complex for you. Good luck
-
Cable2 has pointed out almost everything I was going to.
Just make your 2Wire modem the DHCP server and give the other two wireless routers fixed IP addresses that are outside the DHCP range (they can be in the DHCP range but that can cause some problems so it is better to give fixed IPs that are outside the DHCP range).
If you MUST have both WiFi units working (maybe like us where we have a WiFi access point on each of our three floors because of the construction of the building) use a different channel for each unit to reduce interference.
Like Cable2 I would question the use of wireless routers rather than switches and an access point.