New
#11
You can always try running the command netsh winsock reset from an administrative/elevated cmd prompt to reset the sockets layer to the out-of-box defaults. It'll break any apps with an LSP installed on the winsock stack, but the only thing in common that network apps would have would be winhttp, wininet, and winsock. IE uses wininet, Firefox is a sockets app, and MWB is a winhttp app - given a wininet app works but neither the winsock or winhttp one does not, it sounds like something's sitting at the winsock layer and causing you trouble (wininet and winhttp use winsock, but applications using wininet or winhttp don't access winsock directly - it's complicated, I'm not going to get too deep into that here ). I'd reset winsock before doing anything drastic to see if there is anything on the network stack itself that would cause it.