Hi @lab1301 

I was about to look at your diagnostics when I saw this.

I agree, in part, with @Belly M - we don’t recommend you connect your NAS to a Sonos device, but it should work without issue (a Sonos device with 2 ethernet ports will act as a switch, in part). However, connecting a Sonos device to a PC via ethernet is a definite no-no.

Rather than create a bridge between WiFi and ethernet on the PC, however, I recommend you simply do not wire Sonos to your PC with an ethernet cable - both Sonos and the NAS should have their own ethernet connections directly (or via a switch) to the router. If, after doing this, you still have access issues, by all means please submit another diagnostic and I’ll take a look for you, but with the current, unsupported configuration, there’s not much point in me doing so - it’s not actually expected to work.

If the NAS stores nothing but music, connecting it to a router-connected Sonos device is acceptable. I still don’t recommend it though. If you have, for example, movies stored there too, please connect it directly to the router.

This does explain why you have a 169 IP address though - the DHCP server on the router has no idea the NAS drive exists. The PC is an effective firewall.

The OP has stated he has no physical access to the Router’s Ethernet ports which is a requirement to get the NAS working correctly.

In the current config the PC would need to be a DHCP server and some form of bridge or network sharing enabled. As it stands the the Wi-Fi card in the PC does not pass anything to the Ethernet NIC. The ZP80 has no means of routing IP back to the NAS but the PC can see the devices on the Ethernet interface due to self assigned IP addressing.

Edit, I have not done any routing on a desktop PC between interfaces for about 25 years. There must have been something configured to enable this before the updates but in all honesty as @Corry P says it’s unsupported.

Hi @Belly M 

You are correct - I forgot about that detail!

There probably is a way to bridge the connections on the PC, but I sure don’t know what it is.

@lab1301, I think it might be best to just buy a router that will provide you with your own subnet. Some routers do allow you to use another WiFi for internet access, while still creating a subnet for you.

https://appuals.com/how-to-fix-ip-address-starting-with-169-254/

Sometime yesterday I posted the following:

June to September, I bridged the WiFi with the ethernet adapter and that was when I was last able to use the NAS with  Sonos.  Now when I try and create a network bridge I get “The network bridge doesn't have a valid IP configuration" and I lose all internet connectivity and the S1.

You bridge two networks by highlighting the two adapters, right clicking and selecting the bridge option.

And the bridge is created as below:

But unlike in September, the problem is the DHCP server is timing out and that means there is no internet connectivity on the bridge.  My laptop has a valid IP and so has the ZP80 as I’m streaming radio but for some reason the NAS, connected via ethernet to my windows 11 mini, is not getting a valid IP. 

C:\Windows\System32>ipconfig /renew

Windows IP Configuration

No operation can be performed on Local Area Connection* 1 while it has its media disconnected.
No operation can be performed on Local Area Connection* 12 while it has its media disconnected.
An error occurred while renewing interface Ethernet : unable to contact your DHCP server. Request has timed out.

A 169.254.xxx.xxx IP address is intended to be a rescue space -- similar to telling the kids to go to …] in case of a large emergency (such as a major flood), phones aren’t working, etc. and then wait for adult supervision. 

@lab1301,

If the DHCP server isn’t continually working and keeps stopping/timing out, can’t you just simply set a manual IP address, subnet mask, gateway and DNS on the NAS in its configuration page, might that perhaps work for you?