Meridian Unplugged - Powered by MrTechGuy.co.uk Forums Discussion Meridian - Streaming Control:Mac and MC200 via BT HomeHub

Please say more Ian re how to enable selection of Manual entry of IP, it sounds as if it may work for me.

I shall in the meantime see if my MacBook can connect wirelessly given an even longer waiting time... I'd be surprised, but...

Thanks to all others for their responses and explanations... it's clearly a complex issue!

PS 4 minutes and counting to fail to find MC200.

Will PM tomorrow - manic day and need to relax now. In the mean time, it would be useful to know your HomeHub version, whether you have an iPad/core control and confirm that via wifi you can actually see your core debug screen - via web browser http://[your core IP address]/debug

I tried to check the debug operation.. I can access the page fine and then I noted Ian had wanted me to check that I could do this wirelessly. (I already had Sooloos up and connected via Ethernet cable.) I disconnected the cable and found the debug screen wirelessly no problem. Out of interest I checked the Sooloos connection to MC200 ... still there. I exited Control Mac and re entered ... Still connected.... Excitedly but with low expectations I shut off the MacBook and restarted ...Instant connection to MC200. Not quite believing this and also to check stability I have repeated this MacBook switch off cycle and Sooloos instantaneously opens connected to MC200 addresss! (I have a long time previously set Home Hub not to allocate different address)

It is a long time since I tried this manoeuvre and in the past it didn't work!! Fingers crossed....

An hour later ......same manoeuvre does not work. Doesn't find MC200 wirelessly, does so immediately via Ethernet cable. Loses it again immediately
if cable removed. Any further ideas, Ian or others!

Great news. Sounds like, as expected, Control:Mac has remembered the core IP address from a previous sucessful connection so, unless core IP changes (not sure if it will get wiped by Sooloos update), it should work from now on.

Ian please see edited post above, and reason for edit!!! Temporary success only. Failure again!!

Bum...

Can you still access debug via same IP address? I.e. has IP address changed?

If you can, there will be a field which shows uptime of MC200. Can you say what it is?

I think a connection failure may knock the remembered IP address out of the cache in Control:Mac. Thus for WiFi you would be back at square one.

But in mean time, you need to find why you failed to connect via wired too. Sounds like you have multiple faults causing similar looking issue.

Do you have access to things like spare network cables and network switches?

Can you please remind us all what is plugged into what network wise.

Wired connection still 100% successful and always has been.

Uptime of MC200 is 17days 2hours 11 minutes 51 seconds

I have Netgear switch in place connecting MC200 to Home Hub via Ethernet

I have a Humax FreeSat connected Ethernet direct to Home Hub

(I have a separate network on Engenius from home hub via Netgear switcher and Ethernet.)

Wife's PC Ethernet to home hub

The wireless connection is via the Home Hub

The Home Hub is version 2.0

Thanks Ian and everyone!

Hi Brooster

Can you clarify this please?

A policy I always use when troubleshooting is to simplify the layout as much as possible and confirm everything works as expected. Then start adding additional devices you require, so BT HH2 wireless off, connect a switch and connect (wire) the MAC and MC200 and confirm all works, then unplug the Mac and enable wireless on the HH and repeat the test, keep building the network until issues occur.

Russ

+1 with Russ

Is there any chance you are running multiple DHCP servers? Possibly one in home hub and one on whatever engenius is (would be good to know exactly which product).

What netgear switches are they - dumb or smart/managed?

When you run wired, do you connect Control:Mac to switch or router?

Regarding following...

With Control:Mac iirc, if it loses network connectivity it will not recover to a different NIC without being restarted. [confirmed] - So if you restart Control:Mac, you should get connectivity again via the previously cached/remembered core IP address. I've just confirmed this with my O2 router which does not pass multicast over wifi so must have connected via previously cached core IP address.

Rhetorical questions: why does Control:Mac not connect wirelessly on all occasions? Are there duplicate IP addresses on network? Is Engenius having an effect on this - routed or switched? Is there any chance that a Engenius product is acting as a wireless access point?

Thanks everyone. Just a courtesy post to say have to travel to family funeral and will pick up your suggestions and report back following my return. Should be able to post again next week.

Bruce