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!
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. https://livefortech.net/netsh-winsock-reset/
It works again so great, probably won’t happen again anytime soon. Enjoy!
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!
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.
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
The Netherlands
