bpa;227752 Wrote: > TO get TCP network stats on Windows. Open a command prompt window and > run the command "netstat -s -p tcp".
Thanks for that!! Next time I get poor performance I'll do this on the laptop and see if it points to anything! The only problem is I suspect it'll show nothing and I'll still be left wondering if the router or SB (or something else) is to blame. I have another plan/option as well - A friend of mine has a Netgear DG8834G router. I could swap our routers over and live with theres for a few weeks. If I get no problems that would sure imply it's my router. The only problem is, if I do still get spuradic problems that means it could be the SB or indeed something else affecting my network :/ At least that could help!? By the way, on a test at the moment I'm getting this on the SB. Do these figures look normal/abnormal to you? (Especially that signal strength one?):- -ON A 3000 TEST from SlimServer- < 10 : 0 : 0% < 20 : 0 : 0% < 30 : 0 : 0% < 40 : 0 : 0% < 50 : 0 : 0% < 60 : 3 : 4% # < 70 : 8 : 10% ##### < 75 : 3 : 4% # < 80 : 1 : 1% < 85 : 2 : 3% # < 90 : 2 : 3% # < 95 : 1 : 1% < 100 : 1 : 1% >=100 : 59 : 74% #################################### max : 100.000000 min : 56.190476 avg : 92.709236 And then this test as well while playing a FLAC:- Home / Server & Network Health / Player Statistics The server is currently collecting performance statistics for this player. You may set warning thresholds for each measurement. This will record in the server log whenever the threshold is exceeded. The most recent log entries can be viewed here. Signal Strength This graph shows the strength of the wireless signal received by your player. Higher signal strength is better. The player reports signal strength while it is playing. < 10 : 0 : 0% < 20 : 0 : 0% < 30 : 0 : 0% < 40 : 0 : 0% < 50 : 0 : 0% < 60 : 0 : 0% < 70 : 10 : 2% < 80 : 558 : 98% ################################################# < 90 : 0 : 0% < 100 : 0 : 0% >=100 : 0 : 0% max : 78.000000 min : 66.000000 avg : 73.795775 Warning Thresholds : Low High Buffer Fullness This graph shows the fill of the player's buffer. Higher buffer fullness is better. Note the buffer is only filled while the player is playing tracks. Squeezebox1 uses a small buffer and it is expected to stay full while playing. If this value drops to 0 it will result in audio dropouts. This is likely to be due to network problems. Squeezebox2/3 uses a large buffer. This drains to 0 at the end of each track and then refills for the next track. You should only be concerned if the buffer fill is not high for the majority of the time a track is playing. Playing remote streams can lead to low buffer fill as the player needs to wait for data from the remote server. This is not a cause for concern. < 10 : 552 :100% ################################################## < 20 : 0 : 0% < 30 : 0 : 0% < 40 : 0 : 0% < 50 : 0 : 0% < 60 : 0 : 0% < 70 : 0 : 0% < 80 : 0 : 0% < 90 : 0 : 0% < 100 : 0 : 0% >=100 : 0 : 0% max : 8.346939 min : 0.000000 avg : 0.037636 Warning Thresholds : Low High Control Connection This graph shows the number of messages queued up to send to the player over the control connection. A measurement is taken every time a new message is sent to the player. Values above 1-2 indicate potential network congestion or that the player has become disconnected. < 1 : 15 : 79% ####################################### < 2 : 4 : 21% ########## < 5 : 0 : 0% < 10 : 0 : 0% < 20 : 0 : 0% >=20 : 0 : 0% max : 1.000000 min : 0.000000 avg : 0.210526 -- NeilF ------------------------------------------------------------------------ NeilF's Profile: http://forums.slimdevices.com/member.php?userid=13059 View this thread: http://forums.slimdevices.com/showthread.php?t=38451 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
