epoch1970, thanks for your post.
Sorry, I should have told you up-front about my system... I run Windows
7 Pro 64-bit on a quad-core i5 CPU (name: 'PC2015').
Here is the output from ipconfig:
-----
Windows IP Configuration
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
IPv4 Address. . . . . . . . . . . : 192.168.0.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
Ethernet adapter VMware Network Adapter VMnet1:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::1c70:ca55:1b83:8755%13
IPv4 Address. . . . . . . . . . . : 192.168.88.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
Ethernet adapter VMware Network Adapter VMnet8:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::c46b:52bd:bc9d:d729%15
IPv4 Address. . . . . . . . . . . : 192.168.153.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
Tunnel adapter isatap.{C43B1E49-FBED-4270-92A5-EA27AD2325EC}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Tunnel adapter isatap.{63B9FD00-C61B-47B4-813E-6600692C521C}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Tunnel adapter isatap.{4A833E03-756B-4126-A13F-B77AEB1605E1}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
-----
and from route PRINT:
===========================================================================
Interface List
11...44 8a 5b 84 6b 6c ......Realtek PCIe GBE Family Controller
13...00 50 56 c0 00 01 ......VMware Virtual Ethernet Adapter for
VMnet1
15...00 50 56 c0 00 08 ......VMware Virtual Ethernet Adapter for
VMnet8
1...........................Software Loopback Interface 1
17...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
12...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
14...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
16...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3
===========================================================================
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface
Metric
0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.100
266
127.0.0.0 255.0.0.0 On-link 127.0.0.1
306
127.0.0.1 255.255.255.255 On-link 127.0.0.1
306
127.255.255.255 255.255.255.255 On-link 127.0.0.1
306
192.168.0.0 255.255.255.0 On-link 192.168.0.100
266
192.168.0.100 255.255.255.255 On-link 192.168.0.100
266
192.168.0.255 255.255.255.255 On-link 192.168.0.100
266
192.168.88.0 255.255.255.0 On-link 192.168.88.1
276
192.168.88.1 255.255.255.255 On-link 192.168.88.1
276
192.168.88.255 255.255.255.255 On-link 192.168.88.1
276
192.168.153.0 255.255.255.0 On-link 192.168.153.1
276
192.168.153.1 255.255.255.255 On-link 192.168.153.1
276
192.168.153.255 255.255.255.255 On-link 192.168.153.1
276
224.0.0.0 240.0.0.0 On-link 127.0.0.1
306
224.0.0.0 240.0.0.0 On-link 192.168.0.100
266
224.0.0.0 240.0.0.0 On-link 192.168.88.1
276
224.0.0.0 240.0.0.0 On-link 192.168.153.1
276
255.255.255.255 255.255.255.255 On-link 127.0.0.1
306
255.255.255.255 255.255.255.255 On-link 192.168.0.100
266
255.255.255.255 255.255.255.255 On-link 192.168.88.1
276
255.255.255.255 255.255.255.255 On-link 192.168.153.1
276
===========================================================================
Persistent Routes:
Network Address Netmask Gateway Address Metric
0.0.0.0 0.0.0.0 192.168.0.1 Default
===========================================================================
IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination Gateway
1 306 ::1/128 On-link
13 276 fe80::/64 On-link
15 276 fe80::/64 On-link
13 276 fe80::1c70:ca55:1b83:8755/128
On-link
15 276 fe80::c46b:52bd:bc9d:d729/128
On-link
1 306 ff00::/8 On-link
13 276 ff00::/8 On-link
15 276 ff00::/8 On-link
===========================================================================
Persistent Routes:
None
-----
I've also attached a screen dump from Fing on my phone (with my SSID
hidden), showing that the four SB3s are visible on the network (two, 102
and 104, are via the Edimax wi-fi extender, which has an IP address of
113, but doesn't always show in Fing).
Your 'static lease assignments' suggestion sounds like a good idea, but
I don't think my D-Link DSL-2877AL does it. I searched the user manual
for 'lease' but found no reference to static leases.
All the wireless SB3s were working through the TP-Link router before,
and I changed nothing on that router. In any event, it is not relevant
to this problem-solving - once we solve what's blocking the wired SB3, I
expect the others will be solved too.
As for the Windows 7 firewall rules, I'm not too familiar with how to
set it up. I had a look in the 'Advanced' section, and viewed an
'Inbound rules' list, which had three entries for Logitech Media Server.
The 'Public' one was disabled, but the 'Private' and 'Domain' rules
were enabled, and all addresses, protocols, ports, users and computers
were displaying 'All'. I'm guessing that means that nothing is blocked
within my network.
Thanks,
Daniel
+-------------------------------------------------------------------+
|Filename: Fing20160730.jpg |
|Download: http://forums.slimdevices.com/attachment.php?attachmentid=20835|
+-------------------------------------------------------------------+
------------------------------------------------------------------------
DanielF's Profile: http://forums.slimdevices.com/member.php?userid=64151
View this thread: http://forums.slimdevices.com/showthread.php?t=105918
_______________________________________________
Squeezecenter mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/squeezecenter
