The IP has changed a couple of times today as I have re booted the N5.
It was 31, but since the re boot it’s 33. I sent you the wrong screenshot.
The IP displayed on the N5 is 192.168.0.33
I tried the Chrome browser and got the same.
The browser shouldn’t make any difference.
What is the IP address of the Mac you are trying to access the N5 from? (Settings/Wifi/Details/TCP/IP or take a screenshot with Shift-Option-4)
1 Like
Needless to say that is a bit strange. Your router is 192.168.0.1, your Mac is 192.168.0.32 and your N5 is 192.168.0.33. You are on the same subnet and nothing should stop your Mac connecting as long as you enter the right address in your browser (in the address bar not the search bar).
There is a three keys icon on your menu bar (top right) that I don’t recognize. That isn’t some security or firewall software by any chance??
It might be worth restarting your Mac but other than that I am running out of ideas. If you have a smartphone with a browser you could try entering the address for the Melco in the browser there and see if that works. It might help you determine if the source of the problem is the Mac (works from phone) or the network (also fails intermittently from phone). Otherwise you may need to contact the dealer who sold you the Melco.
Thanks for your help Andrew,
The 3 keys at the top is the apple Password Key Chain. So I don’t think that it would affect an IP search.
I don’t suppose it’s anything to do with Private WI Address or Limit WiFi Tracking?
No, I very much doubt it. I have those same settings on my own Mac in my home network and don’t have any problem accessing my own devices.
I forgot to mention…
I have had no problems in accessing the N5 Internal drive and Music Library.
Finder > Go > Connect to Server > Internal > Music.
I can also access Minimserver without issue from the Mac.
I have obviously managed to do it at some point as I included a screen shot earlier in the post.
OK, one last thing to try (and I have no experience with Melco so this may be spurious). There is a setting in the Melco called WebRemote that “allows you to remotely operate the Digital Music Library from a web browser…”. You do have that set to “On”??
1 Like
I have had it on and off throughout the day. Testing various settings.
It obviously work some of the time at the attached screenshot shows.
Web Remote is set to On.
Understand. Sorry David, I’m clean out of ideas. 
1 Like
Thank you for your kind help Andrew. Much appreciated👍
Hi Dunc
I have searched high and low in settings I cannot find this option? Did you mean Web Remote? If so, it is switched on.
Settings
Smb file sharing
Switch on
1 Like
Good morning Andrew
The technical issue I’m having is with the Melco N5, which maybe a bit off topic to my original post. Did you want me to start a different topic?
I do appreciate that this mostly about the Melco N5, but my Bartók is connected directly to the Melco N5, which could be causing an issue? 
Before you give me an answer to that, please let me tell you what I have done and what I’m doing.
Last night the IP Address (192.168.0.34) for the Melco worked perfectly for about a hour. I closed down Safari on my Mac, went back in to Safari, entered 192.168.0.34 (Address bar, not Google search) and got the results shown in the attached screen shots!
I appreciate that the IP address in these screenshots is 192.168.0.31, that’s because the IP address changes now and again.
So, this morning I have attached a cheap Switch to the Sky Hub (Router) and connected all non audio devices to that Switch. The Melco N5 is the only device connected directly to the Sky Hub.
I then re booted the Hub.
I will do a process of elimination. Next will be the Bartók and Melco N5 connections, which includes an 'ADOT fibre converter’, connected to the Melco’s SFP Port.
I must add, that before I got the Melco N5 and ADOT, I was using the Bartók with Roon and Roon Nucleus, Mosaic was flawless.
Since adding the Melco N5 and the ADOT Fibre converter, I have been getting connection issues between the Bartók and Mosaic. Please see screenshot.
Would Phil be able to get involved in this?
Alan Ainslie from Melo (Ex Naim and Technics) is a Wizard and will know Phil very well.
However, Alan is in hospital at the moment, so I didn’t want to bother him.
I have included a drawing of my current setup.
Audio System Diagram copy.pdf (13.4 KB)
Kind regards
David
Hi David,
Yep, I know Alan and we go back a long way - almost 20 years! 
I think realistically this is a problem for ADMM to solve with you because I’m not completely sure of what port numbers they are currently using, I just googled and those came up so it could be that I’m using old / incorrect port numbers and that wouldn’t work.
Melco have done a complete new set of products since I was last with them four years ago and I would presume a new set of firmware to go along with those new units so they should be able to help you better than we can.
My concern from reading above is that you say you are getting hit-and-miss connectivity to the Melco so what I’d probably do if this were an issue that I was facing I’d reserve an IP address for the Melco (and the Bartok) in my routers DHCP settings so that they are always given consistent IP addresses - at least then you know that they won’t move around.
Cheers
Phil
1 Like
David, it’ll probably help if you don’t miss out the " : " - it won’t work without it 
Phil, if I’m not mistaken, the newer Melco machines have a Web control interface which is separate from the running UPnP Server. That Web control interface is the one that David seems to be having problems with, it’s likely on standard HTTP TCP port 80 (unlike MinimServer which is on 9790, or Twonky which uses 9050).
1 Like
Hi Anup!
The old ones also used to have that control interface too (if you enabled it). As you say, it SHOULD just come up as the default web interface.
I’m somewhat reluctant to delve into this too deeply from our end as (as David has said) until he slotted the Melco and the ADOT fibre converter into the setup then the Bartok (and Mosaic) were working well so it would seem that there is an issue there.
Myself I’d set up a couple of reserved IP addresses for the Bartok and Melco and run a small switch in the HiFi stack with one port connected back to the router, one port connected to the Melco and one port connected to the Bartok and check that for stability but ADMM would realistically be the best placed to advise.
Cheers
Phil
1 Like
That is correct @Anupc The Web Control is Enabled.
As I type, the Melco N5 (192.168.0.35) is displaying the control panel correctly, as is MinimServer. 
Probably nothing to do with it, but since connecting the N5 directly to the Router, without the other non audio devices, the Bartók and Melco N5 names now appear correctly in the ‘Attached Devices’ in the Sky Hub.
Hi Phil
As I recall, about 10 years ago when I had the ND5 XS, I was advised by Steve Hopkins to give it a separate IP Address. Not too many people mention them recently?
Re Alan, I’ve sent you PM.
Cheers David
Absolutely - it shouldn’t be necessary but if your router is changing the units IP address over the day (even if you are simply rebooting it) then the router itself is generally not being very intelligent.
Most routers nowadays will temporarily retain a units IP address even if it isn’t reserved and reissue it if that device then asks for an IP address again within a short period of time which allows for units to be rebooted and them still stay at the same address without reserving an IP address in the router settings but if your router is changing the IP address each time the unit reboots then that is a total pain and reserving an IP address in the router DHCP settings just so that it does keep its IP address will just make things easier (as you’ll be able to bookmark the various Melco web interface pages).
Just NEVER be tempted to allocate a static IP address on a piece of kit directly unless you are really sure of what you are doing - down that path lies pain when in three years time you replace your router when you change ISP and you can no longer get to the units web interface to change it’s IP address to something that is on your new routers subnet. 
Cheers
Phil