D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-323 => Topic started by: bdevoe3 on March 01, 2014, 06:45:41 PM
-
I have DNS-323 that when I try connecting through a switch (TP-Link TL-SG1005D or a TRENDNET TEG-S8g) it will not connect to the network. The blue network light just occasionally blinks but that is it. I have tried different cables that I know work. I have verified the DNS-323 is working by connecting it directly to the router. And the switch works fine as I can connect my PC and printer through it and it works just fine. I cant leave the DNS-323 connect to the router as a permanent solution. I am at a loss and have no other ideas. There must be some setting in the DNS that I am missing. Appreciate any help. Thanks!
-
I can only give information on the TP-Link because we have used several of the TL-SG1008D with our clients.
In all cases we have not found any problems with connecting a DNS-323 to the network through that switch.
First make sure that the network cable is securely plugged into the switch. A new unit tends to have tight sockets so care is needed to ensure good contact.
With the cable plugged in what is the state of the Link/Act LED (the port LED on the front)?
Have you set the DNS-323 network speed to Auto?
Are there any other changes on the network - new router that may have changed the network IP addressing for example?
-
Partly out of curiosity, and also as a serious question - why can't you leave the NAS connected to a router - I'm pretty certain there are a few thousand (if not hundred thousand) NAS units out there connected to routers.
Depending on the NAS & the router - it's a useable configuration with no significant compromises.
To address your problem - start by ensuring the network interface on the NAS is set to auto configure the speed and has the default frame size, and also that you have the ip addressing taken care of - personally I prefer to use a static address on shared resources.
Ensure that the link lights are on at both ends - if not you may have either cable or connection issues.
-
Thanks for the responses....
I have gone through each of the connections to make sure they are good...have even tried several different cables with no difference.
IVAN:
Yes the DNS is set to auto and Jumbo Frame are disabled. I checked the IP adressing and made sure everything was set the same. When I plug the cable into the DNS the blue led just flashes intermittently and I get no light on the switch.
FORDEM:
The reason cant leave the DNS connected to the router is location of where the DNS is. Its close enough to the router that I can run a long CAT cable to it, but I cant leave the cable lying across the floor.
The NAS is set to auto and I have Jumbo Frames disabled. I have tried with both DHCP and Static IP addresses and makes no difference. I am using the default static IP address. Neither link lights are working...but like I said tried multiple cables, even the one that I use to connect directly to the router.
-
And I have firmware 1.10 loaded on the DNS.
-
FORDEM:
The reason cant leave the DNS connected to the router is location of where the DNS is. Its close enough to the router that I can run a long CAT cable to it, but I cant leave the cable lying across the floor.
Any particular reason you couldn't move the NAS?
Neither link lights are working
Let's clarify this - you get no link lights at all? What about when you connect the NAS to the router, do the link lights work then?
You haven't told us what router you have and a quick Google search shows that the switches are basic unmanaged gigabit switches - there is a possibility if the router has 10/100 ports and the switches are gigabit, that the cables that worked on 10/100 won't work on gigabit - in fact - the most common problem when moving from 10/100 to gigabit is the cables.
So - are you in fact moving from 10/100 to gigabit, and if you are, where did you get the cables?
Yes, I understand you have tried multiple cables, but the lack of link lights is pointing to a connection issue, either cables or speed/duplex negotiation.
-
As a last resort I could move the NAS to the router, but I would rather not. Plus I dont see why it shouldn't work through the switch.
Yes, when I connect the NAS directly to the router all of the lights work.
The router is an Arris TG862G. I am using CAT6 cables from the switch to the NAS and I believe CAT5e from the switch back to the router. For full disclosure the path back to the router goes through a TrendNet TEG-S8g switch. I have tried connecting directly from the Trendnet switch no better results. I have also connected the TP-Link switch directly to the router and then the NAS with no results.
-
OK - everything you have is gigabit - to do what I'm about to suggest may cause a temporary loss of connectivity, you should be able to regain connectivity by reconnecting to the router, worst case scenario, you'll need to do a reset to defaults using the pin switch on the rear.
Try manually configuring the NAS on all the network options - start with gigabit, full duplex, then half duplex, if you can't maintain a connection at gigabit, try 100mbit, again, both half & full, and eventually drop to 10 mbit.
By the way - what I asked was where did you get the cables - not what sort of cables - the reason is this. A CAT5 cable will only meet CAT5 spec if properly terminated, likewise a CAT6 cable will only meet CAT6 spec if properly terminated - there are very specific techniques required to meet those specs if you're terminating the cables yourself.
-
Tried at 1000 and 100...no option for 10....none of those worked.
And the cables are all purchased... the CAT 6 cables recently from Amazon.
-
I guess you either change the switch or move the NAS - if it's any help, I used a Netgear GS108T with mine.
-
OK, let us get down to basics.
Have you tried all the ports on the switch?
Does the link light on the switch light when you connect it to the router? If yes try each port, this will determine if the switch is functioning.
Does the link light light when you plug a computer into the switch?
What is your basic network setup? For example:
Router --> Switch --> NAS
¦--> Computer
¦--> Computer
-
Yes, I have verified the ports on the switch work and have moved the NAS to different ports with no luck. I have connected my PC through the switch and it works.
The link light on the switch does not come on when I plug the NAS in. And yes when I plug the computer or printer into any port on the switch the light comes on.
Basic setup
Router ---> Desktop PC
---> Trendnet Switch
|---> TP-Link Switch
|---> NAS DNS-323
|---> Cannon Printer
The router connects to the wired network in the house and the Trendnet Switch is at the patch panel which I use to connect the other ports throughout the house.
I have tried connecting the NAS directly through the Trendnet switch with no luck. I know in the past I had it connected to the switch and it worked.
I am going to switch the Trendnet and TP-Link switches tonight and see what happens.
This is very frustrating as I cant see any reason why this doesnt function properly.
Thanks again for all of your help!
-
OK...I took both of the switches out of the loop and just connected the NAS to the network line where the switch was and it will connect to the router. Now here is where it gets interesting...the NAS network light is blue and I can access all the files on the NAS with no problem. However when I look at the router DHCP table is doesnt show up and when I try and access the NAS configuration tool I can get to the login page but after that I am getting a "Oops! Google Chrome could not connect to 192.168.0.32" even though I can still see the NAS connected and access the files. When I Ping the NAS I also get a response. Now I am really confused. ???
-
Why should the NAS show in the router's DHCP table if you're using a static address?
-
Two things;
What does NETSCAN show as the IP address of the NAS?
Have you tried a different browser to access the NAS web interface? There have been problems reported with Chrome not being able to do that.
In your diagram, if you can access the printer there should be no reason why you can't access the NAS. Again if you can access the printer, unplug the network cable of the printer at the printer and plug that into the NAS - what is the result?
-
Why should the NAS show in the router's DHCP table if you're using a static address?
Thanks...I had it set to dynamic!
-
Two things;
What does NETSCAN show as the IP address of the NAS?
Have you tried a different browser to access the NAS web interface? There have been problems reported with Chrome not being able to do that.
In your diagram, if you can access the printer there should be no reason why you can't access the NAS. Again if you can access the printer, unplug the network cable of the printer at the printer and plug that into the NAS - what is the result?
I tried it in Explorer with no luck either.
Yeh, I can access the printer with no problem. In fact I connected my PC through the switch and it works. I did try just moving the cable from the printer to the switch and it still didn't work.
And when I run NETSCAN with it connected without the switches in the loop the DNS shows up.
At this point I am thinking that I just need to do a final backup of the NAS and look for a new NAS solution. as there must be some hard problem that I am not going to solve.
-
OK...I did a Reset and a hard reboot and at least now I can access the NAS web interface.
-
After giving up last night I left it connected to the TP-Link switch and this morning I get up to find that it has connected to the switch. However, I cannot access the DNS. I ran NETSCAN and it shows something at 192.168.0.32 IP address, but calls it unnamed.
-
OK, a little progress.
The 192.168.0.32 is the default IP address of the DNS-323 which is to be expected because you did a reset. I assume your network is on the 192.168.0.xxx subnet and 192.168.0.32 is outside the DHCP range of the DHCP server of the router - if it isn't then that needs correcting for a start.
The fact that NETSCAN does not show the default name of the DNS-323 is a concern.
One other thing you could try. Disconnect everything from the router except the first switch, then connect the PC to the switch and confirm it gets an IP address (Hoover IP is good for that). Then connect the DNS-323 to the switch and see if the Easy Search Utility (on the DNS-323 setup CD) can find the unit. If it can then you should be able to access the web interface and make any necessary adjustments. If the search utility can't find the NAS then we have to start thinking that there is either a faulty switch or the DNS-323 itself may have a fault.
As a side note, the possible reason the NAS appeared overnight is that it first looks for a DHCP assigned IP before reverting to the default IP but I don't know what the timeout is before it goes to default (we have never had cause to see this because all the NAS/switch setups we have at clients have fixed IP for the NAS).
-
The IP range on the router goes to 255...so should not be an issue.
I did set the DNS to a fixed IP address and reconnected it to the switch to see what happens. It did not connect right away so I am going to see what happens over night.
When I connect the PC through the switch it gets an IP address right away. I am pretty confident the switch is working fine and either its a problem with the DNS itself or some compatibility issue between the switch and DNS...which makes no sense. So I am really leaning towards the DNS being the problem...except it works fine connected directly to the router. I guess I am going to have to reconsider either the location of the router or the DNS or keep pulling my hair out getting this to work.
Thanks for your continued help!
-
Latest and greatest...the DNS is connected through the TP-link switch and seems to be fully operational, at least as of tonight. I wish I could explain. But thanks to IVAN and fordem for your help.