Discussion Locked

Problem with viewing website

0 helpful
11 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Can anyone could suggest possible reasons
for the following problem:

I recently created a site for a client. I've hosted this site on some webspace we own, but the client already owns their domain name and so
they have re-routed the domain name to our ISP space. Everyone I have spoken to
can view the site fine at www.redbridge-holdings.com

However, I cannot see the website for most of the time (I'm using IE
6, but I've also tried accessing it using netscape).
The two other people I work with, who are on the smae network as me,
but using different browsers, one a PC IE 5 another a MAC, are experiencing
the same problem. Very occasiionally the site displays but for the
most part we get the usually page cannot be displayed error:

Cannot find server or DNS Error
Internet Explorer

I also have trouble accessing the site via FTP. All our other sites on this webspace are ok.
At first we thought this could be a problem with the domain name
routing or with the Name Servers being busy, overloading etc, I ran a DNS check and one of the two DNS appears to be down,However,
everyone outside of our office can access the site fine and if I go to
a website that offers a cloaking demo, I can see the site!

Can anyone suggest what kind of things would stop our network viewing
the site?
Can everyone who reads this question see if they can see the site
ok and let me know if they just get an error page - then I'll know it
might be a routing problem!

Thanks

Vic

11 replies

by timthetoolman

You generally cant view an internal website using an external address.

My understanding is this... you access the page, you are directed out through your gateway to the nearest DNS server that can resolve the domain name and are then sent back to your own site. Thats the very first request and a webpage is made up of many such requests.

Then the problems start. Your browser now "knows" where to go directly, so it will go straight to the IP address its been told of.

That of course is your external IP address and from there, where does it go? It doesn't know...

Internally you'll need to specify a local address for the website. You may be able to add a local DNS entry (or hosts file entry) to point to the local IP address is about the best I can suggest.

by timthetoolman

OK... So can you get to the site by using the IP address directly?

...or is the ISP using host headers to stuff you up?

by vic.b

Whilst this wasn't the solution it started to point me in the right direction

by vic.b

Thanks for the reply but I don't think that's the problem as the site isn't internal - it's hosted on some webspace we own (but from an external ISP supplier) and our network isn't part of this. Also, I can view all the other sites we host on this space fine - it's just this particular site that is being a problem (which is why I'm so baffled!).

by vicb

Yeah, annoyingly the site doesn't have it's own ISP address, we just have one general address which is divided between numerous sites.

by otl

Try running a tracert to the URL, this should give you an indication of where the problem actually lies. I did notice intermittantly that time line on the several hops was over 1 ms, this would account for "page cannot be displayed" error.
12 1291 ms 275 ms 988 ms so-6-1-0.TR1.LND2.ALTER.NET [146.188.4.81]
14 975 ms 1277 ms 302 ms pos3-0.cr1.lnd5.gbb.uk.uu.net [158.43.233.241]

Specifically connectivity between Alter.net and Uu.net.

BTW - Commands are;

tracert www.redbridge-holdings.com
tracert 194.216.113.252

Can also add ">> " to be able to see/print/e-mail the results.

by vic.b

This was a helpful reply. Whilst it turned out to be a different solution to my problem (I amended my host file)
I wasn't aware of Tracert and so it was useful for me to know.

by vic.b

Thanks for that last bit of advice, I wasn't aware of this facility and it seems really useful.

I've just tried tracert on www.redbridge-holdings and all I get is:

Unable to resolve target system name

Yet if I try it on another website on the same space it runs through the whole trace, just as you said it would.

by vic.b

I perservered and managed to get the tracert to work on this website. It gets to 14 hops and then times out completely. I also tried the tracert on the other sites on this space and they seem to do the same thing, although we don't have any trouble viewing them!

This discussion is closed to new replies.