d6jg wrote: 
> There is definitely something in the one of the latest Windows update
> that causes some issues with networking where the Red Cross status on
> drive mapping occurs post boot up but doesn’t restore when you try to
> access. If you restart it then works. I’ve not got to the bottom of it
> yet.
> Also I’ve noted that IPv6 is forced on even if not enabled in DHCP and
> you will find an entry for :: in your DNS settings unless you switch it
> off.
> There is also an SMB 1.0 auto removal process that has been inserted.
> So when we are talking about Squeezelite failing I think we need to know
> what specific build of W10 we are talking about.

Regarding Windoze10:
* This issue exists on my two windows machines, both running the latest
version 20H2, with all patches applied.
* This issue has existed for 1-2 years, so it also existed on older
windoze 10, it's not specific to the latest windows.
* By chance, I have yesterday received my new Dell XPS-15 9500, so now I
have a 3rd windoze computer I can use for testing. I set up the system,
installed all patches, and upgraded to version 20H2, like the other
machines. 
* I ran the test on the new system, and I confirmed that this issue also
exists on this new machine. The issue is identical, and repeatable
across all systems: the issue comes up after the first 5 minutes of
operation, and the outage lasts for 30 seconds, and keeps coming up
every 5, 10, 15 or 20 minutes after that. 
* On the Synology side, this happened when running LMS 7.9.7, and still
exists after upgrading to the newer LMS 8.0.1

Regarding network drive mappings:
* For years, I have been annoyed by Windoze, every time I log in, my
network drives are disconnected, and I see a message saying "some of
your network drives could no be connected". I have to click on each
drive to reactivate them. 
* With my Synology storage, (running Samba) I *never* have trouble
reconnecting. I have NOT noticed this issue you mention: that you get
the Red Cross (drive disconnected) upon bootup, but it won't reconnect,
even when you select the drive. 
* As a test, I have disconnected all my drive mappings, and rerun the
test. Outages happened 4 times over 45 minutes, at 10, 15, 30 and
40-minute marks. No change in overall behavior.

Regarding IPv6:
C:\Users\admin>ping nas
Pinging nas.local [fe80::211:32ff:fe92:9693%4] with 32 bytes of
data:
Reply from fe80::211:32ff:fe92:9693%4: time<1ms
Reply from fe80::211:32ff:fe92:9693%4: time<1ms
We can see that DNS resolves its IPv6 address, but I can also ping it
with IPv4:
C:\Users\admin>ping 192.168.0.60
Pinging 192.168.0.60 with 32 bytes of data:
Reply from 192.168.0.60: bytes=32 time<1ms TTL=64
Reply from 192.168.0.60: bytes=32 time<1ms TTL=64
My Synology is set up with both, and I verified this in the
configuration. To test whether IPv6 is causing issues, I have disabled
IPv6 on the Synology, and rerun my test. 
Now when I ping it, it resolves as IPv4:
C:\Users\admin>ping nas
Pinging nas.local [192.168.0.60] with 32 bytes of data:
Reply from 192.168.0.60: bytes=32 time<1ms TTL=64
The outage happened as usual, this time, instead of after 5 minutes, it
took 10 minutes before the first outage happened. 
Thus we can say that this issue is not affected by the presence of
IPv6.

Another test: install location.
* I have installed SqueezeLite into C:\program files (x86)\SqueezeLite
* This might be considered unusual, because it's just a command-line
program with no installer. I use admin permission to copy the files
there. This is just be consistent with where windoze puts its installed
programs. 
* What if this causes some issue? Maybe it causes confusion for windoze,
which needs things written to the registry when items are installed
there. Or maybe the fact that the path contains whitespaces causes some
issues for SqueezeLite, which also uses linux-type file systems that
don't have spaces and are case-sensitive. 
* To put my mind at ease, I reran the test with the software installed
in c:\temp\SqueezeLite
* Results: Outage at 5 minute and 20 minute mark. No difference. 

I'll post separately with my testing with the new "test3" build.


------------------------------------------------------------------------
foopydog's Profile: http://forums.slimdevices.com/member.php?userid=71156
View this thread: http://forums.slimdevices.com/showthread.php?t=113554

_______________________________________________
plugins mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/plugins

Reply via email to