Commented
Posted a Comment: Jul 5th, 2011
"
I've been wondering about just exactly this point.
Is it written anywhe"
Commented
Posted a Comment: Jul 5th, 2011
"And yes that actually did it :)!
I went into devices, chose the network card and asked for a driver rollback :) And whoop it works now!"
Commented
Posted a Comment: Jul 5th, 2011
"I've tried Chrome and FF, guess I'll see what I can find in my windows install that might do the problem. Will post if I find a solution"
Commented
Posted a Comment: Jul 5th, 2011
"Ok, so I can actually access the website through my linux :) Dont know if thats a good or a bad thing"
Commented
Posted a Comment: Jul 5th, 2011
"Wget: Able to get a tiny bit of the content of index.html down to <link rel="shortcut icon" where it doesn't write any more
wireshark: sending fine, according to you having a lost segment being fine, although never receiving anything directly from the website.
ping works
tracert "
Commented
Posted a Comment: Jul 5th, 2011
"Ok so now I've tried to make a direct connection to http://www.mobafire.com while capturing with Wireshark
The sent data are the following:
GET /js/merged.17914.js HTTP/1.1
Host: www.mobafire.com
Connection: keep-alive
Referer: http://www.mobafire.com/
User-Agent: Mozilla/5.0 (Wind"
Commented
Posted a Comment: Jul 4th, 2011
"Don't think that port forwarding would help for a website, they usually run on the same port every website.
Also my roommate is connected to the same router with the same router settings and he can enter the site fine."
Commented
Posted a Comment: Jul 4th, 2011
"I've just completed a traceroute with no timeouts.
However the wget keeps stopping at the exact same point."
Commented
Posted a Comment: Jul 4th, 2011
"ow forgot to mention that the links http://www.omekaprime.com/ and http://mobafire.criticalclicknet.netdna-cdn.com/ worked fine.
I don't know if you can use information from Wireshark? I did a recording of me trying to access mobafire:
"