Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

Resolved Question

Mac on Wireless LAN conflicting with Separate Wired router

May 16, 2016 6:30PM PDT

Slightly unusual one here I guess...

I'm using my Mac for sound editing/engineering which requires the use of Hardware Mixing controllers - these are connected to the computer via Ethernet through a Router (not connected to the internet).

While using this setup, I'd also like to connect to my other (internet connected) Router which is in a different room via Wifi.
So...

- Mac is ideally connected wirelessly to LAN.
- Hardware controllers (MC Transport & MC Mix) are connected to a router with no internet connection and then to the computer.

Both work fine when on by themselves.

Have tried changing IPs & Subnet Masks, no success.

Some details of starting setup:

WIFI - Router Netgear D6300
DHCP (auto address)
IP: 192.168.0.7
Subnet: 255.255.255.0
Router: 192.168.0.1

Ethernet - Older Netgear router with no wifi - works fine.
DHCP (auto address)
IP: 192.168.1.4
SUbnet: 255.255.255.0
Router: 192.168.1.1

What I've tried... (on both with permutations of DHCP, DHCP manual address, and Manual)

- changed router IP
- changed computer IP
- changed subnet mask

really the only three variables.
Am I missing something obvious?

Thanks
Z

Discussion is locked

zeroclip has chosen the best answer to their question. View answer

Best Answer

- Collapse -
Well both on DHCP will be problematic.
May 16, 2016 6:45PM PDT

I'd DHCP from the internet connected router and then for the other configure ONLY the adapter (Apple side) IP address, Netmask and leave the gateway and DNS blank on that adapter.

Think about your routing. That's why.

- Collapse -
Fixed!
May 16, 2016 7:24PM PDT

Thank you so much!

I guess I thought a router address had to be entered for it to be seen.

All working fine now.

Much appreciated.

- Collapse -
Advance one class.
May 16, 2016 7:37PM PDT

+1. You did well. Sometimes IP setup can lead to the dark side.

Good going.

- Collapse -
Thanks
May 16, 2016 9:10PM PDT

Haha, thanks mate.

I know networking pretty much the only tech area that I've never gotten to grips with, it's certainly a dark art.

Now I just have to find out why when I boot (camp) into Win7 the system audio constantly gives little glitches ( ... yes I'll admit to fishing for knowledge here Wink )

- Collapse -
About that Bootcamp audio
May 17, 2016 9:04AM PDT

I can't guess this one but so far those that did that report pretty flawless operation.

But there was this one where they accepted drivers from Microsoft and blammo. All sorts of pain. The only advice I had was to reinstall Apple's driver package.

- Collapse -
Drivers
May 18, 2016 4:22AM PDT

Will give that a shot, thanks, I've been looking into it, I see a lot of genuine (non-bootcamp) Win7 users solving it though device conflicts and (yes) updating drivers.

Thanks for your help.
z