The W
June 7, 2009 - birthdaybritney.jpg
Views: 179004685
Main | FAQ | Search: Y! / G | Calendar | Color chart | Log in for more!
28.3.24 0853
The W - Internet & Computers - taking the wrong route to a website
This thread has 11 referrals leading to it
Register and log in to post!
Thread rated: 8.04
Pages: 1
(310 newer) Next thread | Previous thread
User
Post (7 total)
thecubsfan
Scrapple
Moderator








Since: 10.12.01
From: Aurora, IL

Since last post: 947 days
Last activity: 327 days
#1 Posted on | Instant Rating: 10.00
I have no problem getting to http://luchawiki.org at home, but when I try to check in from work, I can't get to the website.

I know
- it's not a blocking/filtering issue
- it's not the site just going down while I'm at work. I get RSS messages about site updates, and I can use LogMeIn to go on to my home computer from work and get to the site without a problem.
- it's not a DNS issue; it's pinging the same IP on either computer
- at home, I'm on a cable connection. At work, I'm on DSL, and it's a different provider.

Using tracert, I've noticed both the work and home computers get to the network that hosts the site, but to different computers on that network. I'd think all the computers inside the same network would share a routing table, but apparently not.

This is one of those questions where I'm sure there's some phrase to google me an answer, but I've only had luck finding unrelated stuff. I'm stumbling for an answer.

Is there a way to force your computer to use a intermediate to get to a website - when you go from A to C, you've got to go via B? Is this something I might be able to get around with a (free?) proxy server? I'd just go to my hosting company, but the bad routing appears to be happening on whomever hosts them, not their own computers, so I don't know if it's worth asking.



thecubsfan.com - luchablog
Promote this thread!
CRZ
Big Brother
Administrator








Since: 9.12.01
From: ミネアポリス

Since last post: 8 days
Last activity: 3 days
ICQ:  
#2 Posted on | Instant Rating: 9.20
    Originally posted by thecubsfan
    - it's not a DNS issue; it's pinging the same IP on either computer
Are you sure? Instead of ping, use nslookup. (Like, for me, it's 72.52.202.22 - do you get that in both places?)

You could try a direct telnet and see what happens...something like this:

>telnet 72.52.202.22 80
Trying 72.52.202.22...
Connected to 72.52.202.22.
Escape character is '^]'.
GET / HTTP/1.1
host: luchawiki.org


HTTP/1.1 301 Moved Permanently
Date: Tue, 19 Aug 2008 20:17:03 GMT
Server: Apache/1.3.41 (Unix) PHP/5.2.5 mod_log_bytes/1.2 mod_bwlimited/1.4 mod_auth_passthrough/1.8 FrontPage/5.0.2.2635 DAV/1.0.3 mod_ssl/2.8.30 OpenSSL/0.9.7a
X-Powered-By: PHP/5.2.5
Vary: Accept-Encoding,Cookie
X-Vary-Options: Accept-Encoding;list-contains=gzip,Cookie;string-contains=luchawi_dbToken;string-contains=luchawi_dbLoggedOut;string-contains=luchawi_db_session
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Cache-Control: private, must-revalidate, max-age=0
Last-modified: Tue, 19 Aug 2008 20:17:09 GMT
Location: http://www.luchawiki.org/index.php?title=Main_Page
Transfer-Encoding: chunked
Content-Type: text/html; charset=utf-8







thecubsfan
Scrapple
Moderator








Since: 10.12.01
From: Aurora, IL

Since last post: 947 days
Last activity: 327 days
#3 Posted on | Instant Rating: 10.00
nslookup gives me the same address in both problems.

Telnet actually doesn't work for me from either place.



thecubsfan.com - luchablog
tarnish
Landjager








Since: 13.2.02
From: Back in the Heart of Hali

Since last post: 578 days
Last activity: 1 day
#4 Posted on | Instant Rating: 6.15

Traceroute isn't that useful over the internet. Usually at some point you get to an edge device and then don't get anymore results past it because ICMP packets aren't allowed out of whatever network you're trying to reach. "pathping" is allegedly available on Windows since NT came out, and it uses TCP packets, which might return more results. "tcptraceroute" will do the same under Linux.

Did you put in the extra when you did the telnet? You need to hit Enter twice after typing "host: luchawiki.org". The empty line tells the server it's the end of the query.

What actually happens when you try to go to the site from work? Have you tried multiple browsers/safe mode?
thecubsfan
Scrapple
Moderator








Since: 10.12.01
From: Aurora, IL

Since last post: 947 days
Last activity: 327 days
#5 Posted on | Instant Rating: 10.00
pathping travels the same path as tracert before hitting the dead spot.

telnet gives me


    Connecting To luchawiki.org...Could not open connection to the host, on port 23:
    Connect failed


When going to the webpage, it looks for a while, times out, and goes to a google search list for luchawiki.org. When I click on the link for the site, it gives me the ol'


    Internet Explorer cannot display the webpage


Firefox goes direct to the cannot display message.



thecubsfan.com - luchablog
tarnish
Landjager








Since: 13.2.02
From: Back in the Heart of Hali

Since last post: 578 days
Last activity: 1 day
#6 Posted on | Instant Rating: 6.15
    Originally posted by thecubsfan

    Connecting To luchawiki.org...Could not open connection to the host, on port 23:
    Connect failed



There's the problem. Port 23 is the standard telnet port, which is blocked everywhere (or should be). You need to tell it to connect on port 80 by adding the port number to the telnet command:

telnet www.luchawiki.org 80
Connected to 72.52.202.22.
Escape character is '^]'.
GET / HTTP/1.1

Be sure to hit enter twice after "GET / HTTP/1.1"

The linux tcptraceroute defaults to port 80. Further research shows that pathping still uses ICMP, which means it's going to stop the same place tracert does. Wikipedia says a Windows binary of tcptraceroute can be found here (recommend you scan that file before installing it, for obvious reasons). Run it using port 80 as an argument so you're hitting the HTTP port. Also, running it with "-n" will prevent DNS lookups, which should speed things up significantly.

thecubsfan
Scrapple
Moderator








Since: 10.12.01
From: Aurora, IL

Since last post: 947 days
Last activity: 327 days
#7 Posted on | Instant Rating: 10.00
tcptraceroute was giving me a strange error; not sure if it was the download or if I just didn't have the syntax correct. Either way, I didn't have chance to mess with a couple days, and now the site is back to coming up naturally on my work computer. I presume someone upstream fixed a routing table or something.

Thanks for all your help!



thecubsfan.com - luchablog
Thread rated: 8.04
Pages: 1
Thread ahead: Google enters the browser market
Next thread: DVDVRMB
Previous thread: Need help finding a domain owner...
(310 newer) Next thread | Previous thread
It could have just been a way of catching up to Chrome, which is already on version 14. I wouldn't put much stock in the release numbers anyway, but whatever they want to do, fine with me.
- drjayphd, Firefox updated again!? (2011)
The W - Internet & Computers - taking the wrong route to a websiteRegister and log in to post!

The W™ message board

ZimBoard
©2001-2024 Brothers Zim

This old hunk of junk rendered your page in 0.205 seconds.