Forum Moderators: phranque

Message Too Old, No Replies

I can surf all over, but I can't get into our sites

Help, I'm stuck in hotel on business!

         

eelhandroll

11:27 am on May 2, 2006 (gmt 0)

10+ Year Member



Hello,

I'm stuck in a NJ hotel and since last night, I've been able to surf all over the web EXCEPT when I go to one of our sites on our server.

When I go (using IE and Firefox) to one of our sites, none of our sites load up. I get the error message, "Cannot find server/The page cannot be displayed"

I called my wife in NY and she can get into all of our sites. I called our hosting company in Texas and they can also see all of our sites.

I also went to the hotel's "business center" and our sites do not come up on their PCs either.

The hosting services says to call the ISP...I just can't understand how the ISP's service can only affect our sites.

I did a tracert and ping and I get the messages, "request timed out"

Any clues?

Thanks!

kaled

1:31 pm on May 2, 2006 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



There's probably a duff server somewhere. Use a proxy-server - that'll get around the problem.

You'll need to locate the IP address (and port info) for a proxy - use Google. You'll then have to enter these values in the "connection settings" for your browser.

Kaled.

Cakkie

3:08 pm on May 2, 2006 (gmt 0)

10+ Year Member



Is that site running on a specific port?
A lot of public hotspots of internet access locations have their firewall shut to only allow traffic on the standard http and https ports. I have the same problem with a timesheet application we use at work, and runs on port 10000 instead of 80.

Another problem could be that the domainname isn't resolving correct. Try pinging the hostname and see if it resolves to the correct IP address. If not, check you hosts and lmhost files to see if there's an IP address set for that hostname.

chasing something

7:46 pm on May 2, 2006 (gmt 0)

10+ Year Member



i had the same problem recently. my ISP recommended doing a traceroute to see where the problem is.
in my case it showed a routing problem on my hosts server.
here's the instructions if you need it...

:: On Windows 95/98/Millennium Edition/2000/XP:
::
:: click Start
:: click run
:: type command and click Ok
:: type tracert [insert address of your website here]>c:\trace.txt and
:: press enter
:: when you can type another command, type exit and press enter
:: this should create a document on your hard drive called
:: "trace.txt" that
:: will contain information that looks like this (tracerouting
:: to Yahoo, in
:: this case):
::
:: C:\WINDOWS\Desktop>tracert www.yahoo.com>c:\trace.txt
::
:: Tracing route to www.yahoo.akadns.net [204.71.200.75]
:: over a maximum of 30 hops:
::
:: 1 1 ms 1 ms 1 ms 10.12.14.1
:: 2 21 ms 21 ms 21 ms 10.0.244.1
:: 3 22 ms 41 ms 34 ms rd1so-fe2-0-0.cg.shawcable.net
:: [204.209.215.89]
:: 4 21 ms 21 ms 21 ms rc2so-fe5-1.cg.shawcable.net
:: [204.209.215.77]
:: 5 40 ms 40 ms 40 ms rc2wh-atm1-0-1.vc.shawcable.net
:: [204.209.214.69]
:: 6 43 ms 43 ms 44 ms rc1wt-atm1-0-1.wa.shawcable.net
:: [204.209.214.114]
:: 7 45 ms 44 ms 44 ms ibr01-p1-2.tkwl01.exodus.net
:: [209.1.169.221]
:: 8 44 ms 44 ms 44 ms bbr01-g4-0.tkwl01.exodus.net
:: [216.34.64.163]
:: 9 62 ms 62 ms 64 ms bbr01-p4-0.sntc05.exodus.net
:: [216.32.173.229]
:: 10 64 ms 63 ms 63 ms bbr02-p2-2.sntc03.exodus.net
:: [216.32.132.138]
:: 11 63 ms 64 ms 63 ms bbr01-g4-0.sntc03.exodus.net
:: [216.33.153.1]
:: 12 63 ms 63 ms 65 ms bbr02-p1-0.snva02.exodus.net
:: [206.79.9.138]
:: 13 63 ms 63 ms 63 ms dcr01-g9-0.snva01.exodus.net
:: [64.15.160.134]
:: 14 63 ms 63 ms 63 ms bas1r-ge3-0-hr8.snv.yahoo.com
:: [208.178.103.62]
:: 15 64 ms 63 ms 63 ms www.yahoo.akadns.net [204.71.200.75]
::
:: Trace complete.
::
:: Then follow these steps:
::
:: click Start
:: click run
:: type c:\trace.txt and click Ok