Some websites are not loading

[Lucas]

I think since the last Proxmox 3.3 patch, im not able to load some websites on vms correctly.
It's very weird because some websites like google.com are working without any problems.
But when im trying to connect to microsoft.com and other sites they only show that their loading and i can even see the header and sourcecode, but it isn't shown.
It neither can be the browser because im also having the problem with some programms that apparently also can't really connect to the sites.
My conclusion is that it's something with the built-in proxmox firewall, so i disabled it but that didn't helped.
I've noticed that the websites suddenly loaded while i was shutting down the hostnode, but that only occourred once.
So my question is did some of you guys ever had a similar problem or do you have any idea why it is happening?
I hope you can help me.
Greetings,
Lucas

 

[felipe]

doesnt sound like network problem.
you can allways check with iptables -L if something is firewalled.
maybe a more a dns problem?

 

[Lucas]

I already checked the stuff. I know it has to be something to do with networking so i made a few traceroutes of the problem sites and some of the working ones.
Heres the output, hope somebody knows what it means(www.microsoft.com is not working, chip.de is not working, google.de is working).

root@dedi1214:~# traceroute -i vmbr0 www.microsoft.comtraceroute to www.microsoft.com (65.55.57.27), 30 hops max, 60 byte packets
 1  178.251.229.225 (178.251.229.225)  0.182 ms  0.170 ms  0.158 ms
 2  core1.ffm1.cw4.me (109.230.225.133)  4.069 ms  4.104 ms  4.090 ms
 3  94.250.223.249 (94.250.223.249)  4.177 ms  4.177 ms  4.171 ms
 4  80.95.152.229 (80.95.152.229)  4.171 ms  4.156 ms  4.177 ms
 5  msft-decix-01-fra.ntwk.msn.net (80.81.194.52)  4.118 ms  4.114 ms  4.070 ms
 6  * * *
 7  xe-0-0-1-0.pra-96cbe-1a.ntwk.msn.net (207.46.42.144)  19.508 ms ae5-0.ash-96cbe-1b.ntwk.msn.net (207.46.38.211)  90.303 ms  90.307 ms
 8  ae18-0.was02-96cbe-1b.ntwk.msn.net (191.234.81.255)  91.867 ms ae4-0.pra-96cbe-1b.ntwk.msn.net (191.234.80.83)  19.356 ms ae18-0.was02-96cbe-1b.ntwk.msn.net (191.234.81.255)  91.162 ms
 9  ae0-0.was02-96cbe-1a.ntwk.msn.net (204.152.141.204)  90.991 ms ae5-0.ash-96cbe-1b.ntwk.msn.net (207.46.38.211)  95.099 ms ae0-0.was02-96cbe-1a.ntwk.msn.net (204.152.141.204)  91.055 ms
10  * ae18-0.was02-96cbe-1b.ntwk.msn.net (191.234.81.255)  91.113 ms *
11  ae1-0.was02-96cbe-1a.ntwk.msn.net (204.152.141.206)  91.018 ms  91.072 ms  91.106 ms
12  * * *
13  * * *
14  ae2-0.cys01-96cbe-1a.ntwk.msn.net (204.152.140.116)  134.027 ms *  135.822 ms
15  * ae1-0.co2-96c-1a.ntwk.msn.net (191.234.80.29)  156.086 ms *
16  ae16-0.co2-96c-2b.ntwk.msn.net (191.234.80.171)  158.238 ms ae2-0.cys01-96cbe-1a.ntwk.msn.net (204.152.140.116)  133.995 ms  134.127 ms
17  ae15-0.co1-96c-1b.ntwk.msn.net (191.234.80.156)  155.274 ms  155.996 ms ae1-0.co2-96c-1a.ntwk.msn.net (191.234.80.29)  159.966 ms
18  10.22.8.6 (10.22.8.6)  155.356 ms ae15-0.co1-96c-1a.ntwk.msn.net (191.234.80.70)  156.562 ms 10.22.8.6 (10.22.8.6)  155.672 ms
19  * * 10.22.8.2 (10.22.8.2)  155.168 ms
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
root@dedi1214:~# traceroute -i vmbr0 chip.de
traceroute to chip.de (216.146.46.10), 30 hops max, 60 byte packets
 1  178.251.229.225 (178.251.229.225)  0.209 ms  0.187 ms  0.172 ms
 2  core1.ffm1.cw4.me (109.230.225.133)  4.046 ms  4.038 ms  3.952 ms
 3  94.250.223.249 (94.250.223.249)  9.549 ms  4.150 ms  4.148 ms
 4  80.95.152.209 (80.95.152.209)  4.092 ms  4.084 ms  4.057 ms
 5  xe-4-3-0.edge7.Frankfurt1.Level3.net (195.16.162.1)  4.098 ms  4.081 ms  4.030 ms
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * ae-71-71.csw2.NewYork1.Level3.net (4.69.134.70)  81.711 ms
12  ae-13-60.car3.NewYork1.Level3.net (4.69.155.5)  81.691 ms ae-23-70.car3.NewYork1.Level3.net (4.69.155.69)  81.554 ms ae-13-60.car3.NewYork1.Level3.net (4.69.155.5)  81.794 ms
13  DYNAMIC-NET.car3.NewYork1.Level3.net (4.53.90.150)  81.658 ms  81.779 ms  81.562 ms
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
root@dedi1214:~# traceroute -i vmbr0 google.de
traceroute to google.de (173.194.113.95), 30 hops max, 60 byte packets
 1  178.251.229.225 (178.251.229.225)  0.178 ms  0.150 ms  0.137 ms
 2  core1.ffm1.cw4.me (109.230.225.133)  3.805 ms  3.801 ms  3.793 ms
 3  94.250.223.249 (94.250.223.249)  4.051 ms  4.035 ms  4.130 ms
 4  80.95.152.229 (80.95.152.229)  4.019 ms  4.015 ms  4.002 ms
 5  * * *
 6  209.85.251.150 (209.85.251.150)  4.447 ms  4.618 ms  4.506 ms
 7  209.85.242.209 (209.85.242.209)  4.618 ms  4.855 ms  4.915 ms
 8  fra02s21-in-f31.1e100.net (173.194.113.95)  4.446 ms  4.340 ms  4.428 ms

So as i can read the packages don't even reach the suppossed end. They just vanish i guess?
The Loopback Interface says:

root@dedi1214:~# traceroute -i lo google.detraceroute to google.de (173.194.113.79), 30 hops max, 60 byte packets
 1  fra02s21-in-f15.1e100.net (173.194.113.79)  0.065 ms  0.011 ms  0.010 ms
root@dedi1214:~# traceroute -i lo chip.de
traceroute to chip.de (216.146.46.11), 30 hops max, 60 byte packets
 1  redirector2.dynect.net (216.146.46.11)  0.093 ms  0.011 ms  0.011 ms
root@dedi1214:~# traceroute -i lo www.chip.de
traceroute to www.chip.de (23.74.24.139), 30 hops max, 60 byte packets
 1  a23-74-24-139.deploy.static.akamaitechnologies.com (23.74.24.139)  0.062 ms  0.011 ms  0.010 ms

So do you know what it could be? A problem with the bridge, but as i see the packages all leave the host without any problem. Could it be my provider?
I hope you can help me quick.
Greetings,
Lucas