Print

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

[JustAnotherUser]

DIR645, DNS323 and DNS345 on a home network, Win10

Initially, everything was working well: ISP-supplied modem supported my DNS345, a desktop and a 4-port switch, the switch connected another desktop, a printer and the DNS323.

My ISP upgraded my service and moved their modem, so after the installation, I had to reinstall a DIR645 to replace the functionality previously provided by the ISP modem to provide the 6 ports I needed.  However, now the DNS345 is not visible on the network.  Internet connectivity to the desktops is good, I can access the DIR645 (192.168.0.1), and the DNS323 is visible and accessible (in Windows but not in a browser).  The DNS345 is not and I cannot get to the UI page despite using the IP address displayed on the DNS345 front panel display (which has not changed).

I figure somehow I"m not using the correct IP addresses but I don't know how to discover them since the DIR 645 is not reporting them on the Network Settings page.  The DIR645's DHCP Server is enabled, the Host Address is 192.168.0.1, SNM 255.255.255.0 and 3 devices are reported on the Status Page but two of them are inaccessible (the 3rd appears to be the printer).  WiFi is disabled.  When I used this setup a few months ago, all of the network devices were visible on the Network Settings page.

The odd thing for me is why the DNS323 is working but the DNS345 isn't.  I can use the devices connected via the switch but not directly to the DIR645.  I've checked and reconnected the device, and power cycled the DNS345 and DIR645.

I'm stuck and don't know where to go from here.

[JustAnotherUser]

I found the answer to my problem.  I used the D-Link Storage Utility (and I'm surprised it still works under Windows10, BTW) to discover the IP address.  The utility immediately recognized both DNS drives.  I noted that the DNS345's IP address was considerably different than the 323's and that the device was not configured to accept a DHCP assignment from the router.  I enabled the "Receive DHCP" setting, the IP address was updated and the device was almost instantly recognized by Windows.

Why it was set this way will have to remain a mystery.  I'm certainly not going to look for it 

[FurryNutz]

I recommend setting a static IP address on the DNS so you know what the IP address is. As long as you maintain the same IP address pool string on the host router, you'll be able to access the DNS web page. Mines set for 192.168.0.34 and 35 for my 2nd DNS. I just have to be sure to maintain the 192.168.0.1 IP address sting on the host router.

Glad you got it fixed.

Enjoy. 

[JustAnotherUser]

Thanks for the advice.  The hard part is figuring out how to do what you suggest since I'm not a network engineer by trade or education - pure amateur.  I hope you have time for some more questions.

By "DNS" you mean the DNS345 and DNS323, not the Domain Name Server, right?  Or do you mean the DNS1 and DNS2 settings on the networking setup pages of the DNS323 & 345?

And once I figure out which static addresses we're talking about, where would I go to set one.

I'm still, therefore, confused 

[FurryNutz]

Yes, DNS=DNS345.

[JustAnotherUser]

Ok, makes sense now.

• I found the Network Management > LAN Setup > LAN Settings dialog and the current mode for the DNS345 is DHCP Client.  If I understand you correctly, I should be changing this to Static IP with IP address, SNM (2FF.FF.FF.0) and Gateway IP address (the ISP's router) left as is since these values appear to be correct for the current setup.
  
• The two DNS addresses displayed are significantly different. DNS1 is the IP address of the router.  The other is a 75.x.x.x address.  Is this significant?
• The last option on this dialog is set to "Obtain DNS server address automatically which I believe also remains unchanged.
  
• On the same LAN Setup page of the UI, IPV6 Settings are currently disabled.  Is there a reason to enable this function?  Based on the help, I don't see a need to expand the address pool.
  

Thanks for your continued help.