cannot access certain websites, its as if it times out or can't find the page, but this happens on whole network
Hi, a user reported they couldn't access bbrcc.org.uk and other random websites on a business network, running windows 2011 sbs and a watchguard xtm-25 router on ADSL.
from IE11 I get
this page can't be displayed
make sure the web address http://bbrcc.co.uk is correct.
I also get the same sort of error on a 2003 and 2008 server using different IE's. this would suggest a network or DNS issue. I have restart the DNS server on the SBS, even rebooted the SBS. I've rebooted the watchguard.
I have now got home and can access the website quite happily.
heres a tracert from the business network, what else can I look at ?
C:\Users\username>tracert bbrcc.org.uk
Tracing route to bbrcc.org.uk [72.1.201.152]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms 192.168.100.1
2 30 ms 31 ms 30 ms lo0-central10.pcl-ag03.plu
]
3 31 ms 31 ms 30 ms link-b-central10.pcl-gw02.
0]
4 30 ms 29 ms 30 ms xe-10-2-0.pcl-cr02.plus.ne
5 31 ms 33 ms 31 ms ae2.pcl-cr01.plus.net [195.166.129.6]
6 30 ms 33 ms 30 ms ae1.ptw-cr01.plus.net [195.166.129.0]
7 30 ms 30 ms 30 ms 195.99.126.138
8 32 ms 31 ms 31 ms core1-te0-8-0-0.faraday.uk
54.172]
9 33 ms 32 ms 31 ms peer1-xe-11-1-0.faraday.uk
93.181]
10 44 ms 34 ms 45 ms 213.137.183.22
11 116 ms 112 ms 112 ms ixp1-xe-0-0-0-0.us-ash.eu.
12 * * * Request timed out.
13 130 ms 282 ms 175 ms 69.63.249.25
14 134 ms 131 ms 130 ms 24.156.144.129
15 137 ms 136 ms 139 ms gw01.ktchnr.phub.net.cable
.78]
16 132 ms 131 ms 131 ms 69.63.253.173
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
from IE11 I get
this page can't be displayed
make sure the web address http://bbrcc.co.uk is correct.
I also get the same sort of error on a 2003 and 2008 server using different IE's. this would suggest a network or DNS issue. I have restart the DNS server on the SBS, even rebooted the SBS. I've rebooted the watchguard.
I have now got home and can access the website quite happily.
heres a tracert from the business network, what else can I look at ?
C:\Users\username>tracert bbrcc.org.uk
Tracing route to bbrcc.org.uk [72.1.201.152]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms 192.168.100.1
2 30 ms 31 ms 30 ms lo0-central10.pcl-ag03.plu
]
3 31 ms 31 ms 30 ms link-b-central10.pcl-gw02.
0]
4 30 ms 29 ms 30 ms xe-10-2-0.pcl-cr02.plus.ne
5 31 ms 33 ms 31 ms ae2.pcl-cr01.plus.net [195.166.129.6]
6 30 ms 33 ms 30 ms ae1.ptw-cr01.plus.net [195.166.129.0]
7 30 ms 30 ms 30 ms 195.99.126.138
8 32 ms 31 ms 31 ms core1-te0-8-0-0.faraday.uk
54.172]
9 33 ms 32 ms 31 ms peer1-xe-11-1-0.faraday.uk
93.181]
10 44 ms 34 ms 45 ms 213.137.183.22
11 116 ms 112 ms 112 ms ixp1-xe-0-0-0-0.us-ash.eu.
12 * * * Request timed out.
13 130 ms 282 ms 175 ms 69.63.249.25
14 134 ms 131 ms 130 ms 24.156.144.129
15 137 ms 136 ms 139 ms gw01.ktchnr.phub.net.cable
.78]
16 132 ms 131 ms 131 ms 69.63.253.173
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
ASKER
hi rob
what does the MaxCacheTTL registry value actually do.
does it reset after 2 days or some thing.
what does the MaxCacheTTL registry value actually do.
does it reset after 2 days or some thing.
No idea :-)
But it is a common problem and a common fix. The change is even part of many server build documents.
But it is a common problem and a common fix. The change is even part of many server build documents.
ASKER
that didn't resolve my issue, I've added the reg entry and rebooted server
Very odd. Your description sounds exactly like the common problem.
Do .com web sites work as they should? According to another Microsoft article/KB the problems is limited to less common domain suffixes, or at least less common to North Americans, such as .co.uk, .cn, and .br
http://support.microsoft.com/kb/968372
Do .com web sites work as they should? According to another Microsoft article/KB the problems is limited to less common domain suffixes, or at least less common to North Americans, such as .co.uk, .cn, and .br
http://support.microsoft.com/kb/968372
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Perhaps keep the question open for 3 days. If it is the KB968372 issue flushing the DNS may only be a short term fix. I know restarting DNS will resolve the problem for a couple of days, then it returns.
ASKER
will do
http://blogs.technet.com/b/sbs/archive/2009/01/29/cannot-resolve-names-in-certain-top-level-domains-like-co-uk.aspx