Upvote Upvoted 6 Downvote Downvoted
Weird TF2Center issue
posted in Q/A Help
1
#1
0 Frags +

When I try to access tf2center.com I'm greeted with this:

http://puu.sh/mDLOa/e722ee65b6.png

The problem goes away if I use a browser based VPN but it's a hassle because it throttles my connection. The only other thing I've tried is changing my DNS server with this guide: https://developers.google.com/speed/public-dns/docs/using?hl=en

Help would be greatly appreciated

translated text if it matters: http://puu.sh/mDLTL/845e6e5a3b.png

When I try to access tf2center.com I'm greeted with this:[img]http://puu.sh/mDLOa/e722ee65b6.png[/img]

The problem goes away if I use a browser based VPN but it's a hassle because it throttles my connection. The only other thing I've tried is changing my DNS server with this guide: https://developers.google.com/speed/public-dns/docs/using?hl=en

Help would be greatly appreciated

translated text if it matters: http://puu.sh/mDLTL/845e6e5a3b.png
2
#2
0 Frags +

http://i.imgur.com/bL8YVJg.png

I seem to be getting this error. Not sure what the issue seems to be.

Edit: It doesn't even load anymore.

[img]http://i.imgur.com/bL8YVJg.png[/img]

I seem to be getting this error. Not sure what the issue seems to be.

Edit: It doesn't even load anymore.
3
#3
2 Frags +

Rhydon and I are both on Comcast, can anyone else on comcast confirm/deny if they are getting it too?

Rhydon and I are both on Comcast, can anyone else on comcast confirm/deny if they are getting it too?
4
#4
0 Frags +

have comcast no work

have comcast no work
5
#5
2 Frags +

I can connect on verizon

I can connect on verizon
6
#6
-1 Frags +

that loooks complicated and scary and woah

I'm sorry you have to deal with that, bummer.

that loooks complicated and scary and woah

I'm sorry you have to deal with that, bummer.
7
#7
0 Frags +

Confirmed, Comcast DNS resolves tf2center.com to http://[2a00:1d20:2:13::2]

The correct IPv4 address is 151.80.195.184. Unfortunately, you cannot connect directly, as the IP doesn't match the domain on the HTTPS certificate.

Confirmed, Comcast DNS resolves tf2center.com to http://[2a00:1d20:2:13::2]

The correct IPv4 address is 151.80.195.184. Unfortunately, you cannot connect directly, as the IP doesn't match the domain on the HTTPS certificate.
8
#8
0 Frags +

Is there a fix for that or do I have to call Comcast?

Is there a fix for that or do I have to call Comcast?
9
#9
0 Frags +

I think it's fixed now, pop open a windows command prompt and type "ipconfig /flushdns". This will flush your DNS cache and allow you to correctly resolve the host.

EDIT: Just kidding it's still messing up.

[s]I think it's fixed now, pop open a windows command prompt and type "ipconfig /flushdns". This will flush your DNS cache and allow you to correctly resolve the host.
[/s]

EDIT: Just kidding it's still messing up.
10
#10
4 Frags +

I think I came up with a fix. The problem appears to be that for some reason Comcast's DNS is preferring the IPv6 address resolution which leads to the broken page, as opposed to the IPv4 address which works fine. Thus, the fix is to force your machine to use the IPv4 address (by lowering the IPv6 in priority so it isn't chosen).

To do this, click start, type cmd in the search box, right click on cmd.exe and run as administrator. In the prompt, type the following:

netsh interface ipv6 add prefixpolicy 2a00:1d20:2:13::2/128 0 6

You might need to type ipconfig /flushdns after this. I just tested this and it works on my machine.

I think I came up with a fix. The problem appears to be that for some reason Comcast's DNS is preferring the IPv6 address resolution which leads to the broken page, as opposed to the IPv4 address which works fine. Thus, the fix is to force your machine to use the IPv4 address (by lowering the IPv6 in priority so it isn't chosen).

To do this, click start, type cmd in the search box, right click on cmd.exe and run as administrator. In the prompt, type the following:

netsh interface ipv6 add prefixpolicy 2a00:1d20:2:13::2/128 0 6

You might need to type ipconfig /flushdns after this. I just tested this and it works on my machine.
11
#11
0 Frags +
MasterKuniI think I came up with a fix. The problem appears to be that for some reason Comcast's DNS is preferring the IPv6 address resolution which leads to the broken page, as opposed to the IPv4 address which works fine. Thus, the fix is to force your browser to use the IPv4 address (by lowering the IPv6 in priority so it isn't chosen).

To do this, click start, type cmd in the search box, right click on cmd.exe and run as administrator. In the prompt, type the following:

netsh interface ipv6 add prefixpolicy 2a00:1d20:2:13::2/128 0 6

You might need to type ipconfig /flushdns after this. I just tested this and it works on my machine.

It worked, thanks a lot!

[quote=MasterKuni]I think I came up with a fix. The problem appears to be that for some reason Comcast's DNS is preferring the IPv6 address resolution which leads to the broken page, as opposed to the IPv4 address which works fine. Thus, the fix is to force your browser to use the IPv4 address (by lowering the IPv6 in priority so it isn't chosen).

To do this, click start, type cmd in the search box, right click on cmd.exe and run as administrator. In the prompt, type the following:

netsh interface ipv6 add prefixpolicy 2a00:1d20:2:13::2/128 0 6

You might need to type ipconfig /flushdns after this. I just tested this and it works on my machine.[/quote]
It worked, thanks a lot!
12
#12
0 Frags +

I am on comcast and get it too http://prntscr.com/9stpm9

I could be wrong but comcast DNS servers might be connecting to an older nameserver?

Edit: I did what MasterKuni suggested it works now. The only problem is that my page refreshes constantly..

I am on comcast and get it too http://prntscr.com/9stpm9


I could be wrong but comcast DNS servers might be connecting to an older nameserver?

Edit: I did what MasterKuni suggested it works now. The only problem is that my page refreshes constantly..
13
#13
1 Frags +

Just change your dns server?

Just change your dns server?
14
#14
0 Frags +

Yeah this happened to me too. What the h comcast

Yeah this happened to me too. What the h comcast
15
#15
0 Frags +

I have comcast but it loads up fine for me

I have comcast but it loads up fine for me
16
#16
0 Frags +

fellow comcast consumer here and I also get this problem

fellow comcast consumer here and I also get this problem
17
#17
0 Frags +

have u tried beginnen met uw hosten pakket

have u tried beginnen met uw hosten pakket
Please sign in through STEAM to post a comment.