Cant acccess broswer web interface

Posted by: ngene on 14 July 2017

Put in the last four characters from the mac address http://www.NSSR86b2 but i couldn't get the web interface. Am i doing this right?

Posted on: 14 July 2017 by ChrisH

Hi Ngene,

Im on Windows but I assume its the same with a Mac: no need to type http://www.

Just type 'NSSRxxxx/' into the address bar

Hope this helps.

Posted on: 15 July 2017 by Simon-in-Suffolk

Hi Ngene, this will be down to your router functionality and nothing to do with your browser or whether it's Windows or OSX etc.

if your router is acting as a local DNS and DNS proxy which most do for performance reasons, and it is correctly using DHCP and adding the client name into the DNS table when your router assigns the IP address to the client you should be able to simply type on your browser

http://NSSRxxxx

into the address bar. If you are getting client not found... and you have the client name correct then quite probably your router is not working correctly with or you are not using DHCP on your router. If you have Net Analyzer you should be able to see your client name (NSSRxxx) listed as the DNS name. You shouldn't need to add .localdomain to the client name, although it might be listed as part of the DNS name.

if for whatever reason your router DNS/DHCP is faulty or somehow incompatible with your Naim client... you can always revert to typing

http://x.x.x.x

where x.x.x.x is the local IP address of your client NSSRxxx, but yes this can be cumbersome and should be unnecessary

 

BTW there is another method you can use if your router has no DNS server or proxy or it's not working correctly with DHCP... and that is use multicastDNS or mDNS. Again use analyzer to see the mDNS client name, which may be different from the DNS name, and enter 

http://xxmDNSnamexx.local

Note to force your browser and OS to use mDNS as opposed to regular DNS assuming it supports it, you must add the .local to the mDNS name. mDNS simply uses local standalone discovery and is suited for small networks. The look up will be rather slower than with local DNS

 

Posted on: 15 July 2017 by ngene

Thanks Simon the IP worked.