slunat
commented
4 years ago Nevermind, found a previous issue that detailed the -b command and have now got it working again
Closed slunat closed 4 years ago
slunat
commented
4 years ago Nevermind, found a previous issue that detailed the -b command and have now got it working again
I installed Docker last night for another server I am running on this machine and it created a new network adapter which is on its own different subnet to my actual network. I have noticed that today my aircast and airupnp would not detect any of my devices and it is because they are using the network adapter that Docker uses, rather than the primary network adapter for my PC, so its not detecting any of my speakers as its technically on a different subnet. Is there anyway I can specify what network adapter needs to use so I can make it use my primary network adapter? I am using the latest version of AirConnect on Windows 10.