Board Thread:Questions and Answers/@comment-26358988-20150722095300/@comment-26091666-20150723072344

NetLimiter is a third party software, if you don't know it then chances are you don't have it installed and therefore that can be eliminated from the list of possible culprits.

It looks like you have nominated to fix the issue yourself. Lots of reading ahead for you but that is pretty much what the ins-and-outs of computer troubleshooting is about. :v

I still insist on not paying too much focus on fixing your own computer too much as the event is coming and that the issue may lie elsewhere. If you could just get by using that other laptop for at least a good day or two then the issue is definitely coming from your own computer and that it is hardware/software problem but I am willing to gamble it will be the latter of the two.

As I was writing these I mulled about possible hardware issue and alternative ways to diagnose it, those are (but again are not limited to):
 * Trying out another NIC (Network Interface Card) that at least is known to be working - if your computer is a desktop otherwise, there are USB/PCMCIA/PC-Express to NIC devices are available.
 * Trying out another network cable if you have been using the same network cable for your computer alone. If the same said network cable was used on your other laptop which was working then you can ignore this.

Wireless NIC may also suffice here (as opposed to needing a NIC) provided that you can easily see when the radio waves are not congested due to "peak hours".

Hardware issues can probably be best easily diagnosed if you try either reinstalling (your OS) or boot off some live OS via (re)writeable storage medium.

As for software issues, I also wanted to point out that windows natively has a built-in firewall if you weren't aware. Normally that shouldn't interfere with your "application" sessions as the last I recall that it was app-based firewall. However that may also serve as yet another step to look into. Other than that it really is some malware that is controlling it.

Looking back at what Erupi said earlier on, another potentially easy fix might be is to just try Google public DNS servers. Normally DNS errors shouldn't cause issues like these but it probably doesn't hurt either way to try it out and see if the malware (for instance) is trying to set it to some other DNS server.

Anyway, TL;DR (on my part) good luck!