Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Very Poor Ethernet Performance
#11
Hi Arjayh, that’s a nasty issue you have with your Devialet. You’ve tried almost anything that I also thought of but I think it’s a good idea to check if the ethernet connection is indeed ‘flapping’ so going up and down. Thumb5 mentioned it too. Most switches have two LED’s per port, one that indicates if the link is up and at which speed and the other one blinks if there’s traffic.

If the links goes up and down this could indicate a hardware or cable issue and since you swapped ethernet cables and switches it could indeed be the Devialet. You could check if all pins of the ethernet port are straight and give them a clean with some rubbing alcohol.

You’ve also tried and disabled WiFi with ethernet active so that’s a good thing so no potential ‘loops’ can exist.

Another issue that’s rare is that there’s two devices on your network using the same IP address which you in effect ruled out by giving the Devialet a fixed IP address. Even rarer is two devices on the network using the same MAC address so this probably isn’t worth checking up on though you could try to (temporarily) disconnect all devices on your network not needed for streaming.

Good luck in resolving the issue!
PS Audio P3, Shunyata ΞTRON Alpha Digital and HC/Furutech power cables, Paul Hynes SR7EHD-MR4, DIY Roon Server & Roon Endpoint running AudioLinux Headless, Phasure Lush^2 USB cable, Audioquest Diamond RJ/E ethernet, Uptone Audio etherREGEN, Mutec MC-3+ USB, Shunyata ΞTRON Anaconda Digital XLR AES/EBU, Devialet Expert 250 Pro CI, Nordost Tyr Reference LS cables, Von Schweikert VR-5 SE Anniversary Edition, Anti-Mode Dual Core 2.0, JL Audio Fathom F112. More detail here.

The Netherlands
Reply
#12
Hi Antoine,

Sincere thanks for your reply. It is much appreciated. I found a solution to my problem. I'm not sure of the exact solution, but somewhere in amongst three or four commands in windows I managed to clear up whatever was fouling my network. In short I reset my TCP/IP to default, reset my network adaptor and cleaned up my DNS cache. The trouble is, in frustration, I did all three in one fell swoop, so I don't know which one solved the problem. I really don't understand networks, but I'm sure someone better qualified than I am could point to what likely worked. It was odd, because I could browse the web at normal speeds, and other devices were connected to my network and working okay. Whatever was happening seemed only to affect the Devialet.

All good now, and I'm back to doing what I wish for: listening to music.

Best wishes and thank you once again

Bob

netsh int ip reset
netsh winsock reset
ipconfig /flushdns
ipconfig /renew
Reply
#13
Hi
Sincere thanks for your reply. It is much appreciated. I found a solution to my problem. I'm not sure of the exact solution, but somewhere in amongst three or four commands in windows I managed to clear up whatever was fouling my network. In short I reset my TCP/IP to default, reset my network adaptor and cleaned up my DNS cache. The trouble is, in frustration, I did all three in one fell swoop, so I don't know which one solved the problem. I really don't understand networks, but I'm sure someone better qualified than I am could point to what likely worked. It was odd, because I could browse the web at normal speeds, and other devices were connected to my network and working okay. Whatever was happening seemed only to affect the Devialet.

Sincere thanks and best wishes

The commands I did (Using CMD in Admin mode in Windows) were:

netsh int ip reset
netsh winsock reset
ipconfig /flushdns
ipconfig /renew
Reply
#14
Hi Bob,

You’re very welcome. For someone who says he doesn’t ‘understand networks’ you’ve really done a lot to troubleshoot the issue. Most people would not have come up or found all these steps you took so well done! Smile

I myself am a networking/network security specialist by trade and I’d say it’s probably impossible to say which of the four commands did the trick. The ipconfig /flushdns is least likely to have resolved the issue, it just clears a dynamic cache of resolved hostnames, a reboot would do the same. With the ipconfig /renew command your PC renews the IP address lease you get from the DHCP server in your network, most likely your router. This may have resolved the issue if your PC was using the same address as another machine in your network but rebooting your PC does exactly the same thing too.

The netsh int ip reset does indeed as you wrote, reset the the TCP/IP settings of your network adapter. This could resolve issues if you’ve made manual changes before or if there was some corruption. The winsock reset isn’t very common but restores possibly corrupt winsock installation files. I had to look it up to see what it does. Smile https://livefortech.net/netsh-winsock-reset/

It works again so great, probably won’t happen again anytime soon. Enjoy!
PS Audio P3, Shunyata ΞTRON Alpha Digital and HC/Furutech power cables, Paul Hynes SR7EHD-MR4, DIY Roon Server & Roon Endpoint running AudioLinux Headless, Phasure Lush^2 USB cable, Audioquest Diamond RJ/E ethernet, Uptone Audio etherREGEN, Mutec MC-3+ USB, Shunyata ΞTRON Anaconda Digital XLR AES/EBU, Devialet Expert 250 Pro CI, Nordost Tyr Reference LS cables, Von Schweikert VR-5 SE Anniversary Edition, Anti-Mode Dual Core 2.0, JL Audio Fathom F112. More detail here.

The Netherlands
Reply
#15
If you assign static ip addresses to some devices in your home network, then be sure that your router does assign new ip addresses to new connected devices from a non-conflicting , different ip address range. If ip conflict occurs, then you may experience such problems.
I have about 6 different devices connected to my switch some of which have static assigned ip addresses. I use the range (192.168.1.2 -192.168.1.30) for static ip-address assignments(total of 29 different device). Therefore I changed the setting on the router so that it assigns new ip addresses starting from 192.168.1.31 in order to prevent any ip conflict.
Probably, executing "ipconfig /renew" command totally solved your issue.
Stereo Setup: Synology DS214Play NAS/Internet sources>> Supra CAT8 >> Ubiquiti Edge10X Switch>> Fiberoptical Cable >> SOTM SNH-10G Switch(S-Booster LPS) >> Supra CAT8 >> Euphony v4(Stylus with Qobuz, Tidal) running on RAM >> SOTM SNH-10G >> Supra CAT8 >> Mercury Streamer (GentooPlayer, MPD+UpMpdCli  running on RAM) + Fiio PL50 LPS >>  Mogami Gold AES XLR >> Devialet 220 Pro >> Echole Omnia Speaker/Jumper Cables >> B&W 804D3 Speakers on IsoAcoustics GAIA-II

Headphone Setup: Synology DS214Play NAS(CAT8) >> Ubiquiti Edge10X Switch>> Fiberoptical Cable >> SOTM SNH-10G Switch(S-Booster LPS) >> Supra CAT8 >> Euphony v4( Stylus with Qobuz, Tidal) running on RAM >> SOTM SNH-10G >> Supra CAT8 >>  Mercury Streamer(GentooPlayer , Mpd/UpMpdCli ) + Fiio PL50 LPS >>  RCA Coax >> Chord Hugo >> Fostex TH900 MK2
Reply
#16
If you use a managed switch, then I advise you to prioritize the ports on the switch by changing QoS settings of the ports. By this way, you can give high priority to audio streaming easily.
Stereo Setup: Synology DS214Play NAS/Internet sources>> Supra CAT8 >> Ubiquiti Edge10X Switch>> Fiberoptical Cable >> SOTM SNH-10G Switch(S-Booster LPS) >> Supra CAT8 >> Euphony v4(Stylus with Qobuz, Tidal) running on RAM >> SOTM SNH-10G >> Supra CAT8 >> Mercury Streamer (GentooPlayer, MPD+UpMpdCli  running on RAM) + Fiio PL50 LPS >>  Mogami Gold AES XLR >> Devialet 220 Pro >> Echole Omnia Speaker/Jumper Cables >> B&W 804D3 Speakers on IsoAcoustics GAIA-II

Headphone Setup: Synology DS214Play NAS(CAT8) >> Ubiquiti Edge10X Switch>> Fiberoptical Cable >> SOTM SNH-10G Switch(S-Booster LPS) >> Supra CAT8 >> Euphony v4( Stylus with Qobuz, Tidal) running on RAM >> SOTM SNH-10G >> Supra CAT8 >>  Mercury Streamer(GentooPlayer , Mpd/UpMpdCli ) + Fiio PL50 LPS >>  RCA Coax >> Chord Hugo >> Fostex TH900 MK2
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)