URL is blocked on 2008 SBS Network - How?

Hi all,

Have a client running a single 2008 SBS server on a network protected by a Watchguard firewall and Trend Worry Free Business.  

A client has reported that they cannot access a particular .co.uk url that quite innocently has the word child in itl. When anyone on the internal network regardless of browser choice (including on the server itself) goes to that URL you just get a white screen.  IF they take same PC out of the network the URL works fine.

I've gone into the Watchguard config and added the IP address of the website to the whitelist (you can't add url's) and confirmed that WebBlocker is actually switched off.

I've also gone into Trend and added the URL to the allowed list under Web Blocking and Web Behaviour but nothing seems to work.

Was wondering if there might be something on the 2008 SBS server itself blocking the URL?

Any suggestions gratefully received.


Who is Participating?
Don ThomsonConnect With a Mentor Commented:
If you get 4 replies from both in the network and outside the network - try running a tracert cmd from both locations - Look at the response times and see if any point along the path is excessive.

If you have access to the raw connection from your ISP - Try going on the connection directly with a laptop and see if the problem is then on the Wan side or the LAN side. If it failes go back one step at a time towards the Workstation
Don ThomsonConnect With a Mentor Commented:
If the word "Child" is being blocked - try some other sites with the same word.

IF you get blocked on those or some of those - start looking for a parental control that has the word "Child" in it and remove it from the list.

Also check all Blacklists as well. Typically a Blacklist entry will overwrite a Whitelist entry every time.

Also check you DNS records on the Server
amlydiateAuthor Commented:

No other websites I tested with child in the title were blocked. Nothing in server DNS relating to it, there are no entries in blacklists on both the watchguard and Trend. Am really really stumped
Simple Misconfiguration =Network Vulnerability

In this technical webinar, AlgoSec will present several examples of common misconfigurations; including a basic device change, business application connectivity changes, and data center migrations. Learn best practices to protect your business from attack.

Don ThomsonConnect With a Mentor Commented:
Try this

From a system outside your network - Ping  the web site and record the IP

Then from within your network - do the same  and see if the IPs are the same
Also make sure you get replys from both pings \.
If no reply then try tracert  to see where it's stopping

We recently had a client who moved their web site to a different host and the local ISP that they went through had both of the IPs on their DNS server - took months to figure that one out
amlydiateAuthor Commented:
Many thanks for your suggestion, it sounded very plausible but unfortunately tried a ping of the url from inside and outside of the network and the IP address was the same...
amlydiateAuthor Commented:
Thanks all for your suggestions, turned out there was a baffling hidden area within the Watchguard where you had to enter the url into yet another whitelist for it to then allow the site to be accessed!
Where was the hidden area for you to white list the URL?
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.