Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[bdevoe3]

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!

[bdevoe3]

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.

[bdevoe3]

OK...I did a Reset and a hard reboot and at least now I can access the NAS web interface.

[bdevoe3]

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.

[ivan]

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).

[bdevoe3]

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!

[bdevoe3]

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.