I had the same problem. I can't believe that fixed it.
I'll take it though!
http://realtek-pci-gbe-family-controller2.drivers.informer.com/ has the driver file, if you're so inclined as to take a peek.
I'll take it though!
http://realtek-pci-gbe-family-controller2.drivers.informer.com/ has the driver file, if you're so inclined as to take a peek.
szlejer wrote:
Solution is simple: uninstall latest version of software on your Network Card in device manager.
This issue is caused by optional update for Windows called Realtek - Network - Realtek PCi GBE Family Controller (in my case).
When I rolled back my Realtek driver I can access the site just fine ... so glad you found this fix. Realtek needs to get their act together on these drivers.
coz we 2gud :D
btw, funny this is a realtek issue...I haven't updated that driver since I had my computer (2 yrs almost) since when I did Rey to originally, it ****ed up my resolution on EVERYTHING...so I did a system restore and haven't touched the update since...
wat up with realtek...lol T_T
what exactly is this driver for anyway? isn't it some network card thang...
btw, funny this is a realtek issue...I haven't updated that driver since I had my computer (2 yrs almost) since when I did Rey to originally, it ****ed up my resolution on EVERYTHING...so I did a system restore and haven't touched the update since...
wat up with realtek...lol T_T
what exactly is this driver for anyway? isn't it some network card thang...

Thanks to TRUeLM, Plastictree, Scrax, Xiaowiriamu, foggy12, JahGFX, jhoijhoi, msrobinson, JEFFY40HANDS, Nyoike, MissMaw, and me :) for the sigs!
Thank you szlejer! Same damn problem and I was trying to go back through in my head what I'd done lately on my machine that could have caused this. Just ran Windows update the other day and I recalled the newer realtek driver. Rolling back the driver worked like a charm. Before I rolled back I went into the advanced settings and tried testing out each setting to see if it was a configurable setting that was causing it, but that does not appear to be the case.
You need to log in before commenting.
<Administrator>