Re: Cannot access a web page
From: Vicky (vickyjackson_at_softhome.net)
Date: 07/16/04
- Next message: Blgibson: "IE6 Check Boxes Don't Display"
- Previous message: Bunta: "/?%20 added to typed urls"
- In reply to: Robert Aldwinckle: "Re: Cannot access a web page"
- Next in thread: Vicky: "Re: Cannot access a web page"
- Reply: Vicky: "Re: Cannot access a web page"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 16 Jul 2004 18:38:00 +0200
Hi Robert
Resaults of nslookup
Non-Authoritive answer Name www.skype.com Address 80.160.91.13. (No it
didn't seem to pause)
Resaults of telnet
Could not open connection to the host on port 80 connect failed.
I did a pathping but to data that was displayed was just to much to write
down.
I didn't understand the rest of your reply about GET.
Thanks
Vicky
"Robert Aldwinckle" <robald@techemail.com> wrote in message
news:O$MKj9zaEHA.2840@TK2MSFTNGP11.phx.gbl...
> "Vicky" <vickyjackson@softhome.net> wrote in message
> news:u7BlvOxaEHA.2892@TK2MSFTNGP10.phx.gbl...
> >I have done as you suggested and here is the result after inserting
> > 80.160.91.13 www.skype.com in host file and pinging -n 1 www.skype.com
> > "Pinging www.skype .com (80.190.91.13) with 32 bytes of data. Request
timed
> > out. Ping statistics for 80.160.91.13. Packets sent =1 received=0
> > lost=1(100% loss)" I didn't insert any blank lines or comments as I was
> > unsure what you meant. Still no luck accessing skype. By the way my
> > operating system is Wndows XP Pro
>
> Great. Then you can use telnet to test with.
> You can also use nslookup to check on your DNS.
> I should warn you though that things are not looking good.
>
> First let's find out what your DNS is really telling you. Enter:
>
> nslookup www.skype.com
>
> Does the lookup give you the same IP address that your HOSTS file
> is now using? Did it seem to pause when it was doing that?
>
> Next, you could find out where that ping is failing. It's not
necessarily bad
> but it might give some clues that there are some general problems with
> the routing. To do that use tracert or pathping. (The latter is an
XP
> only command, probably not available in the Home version.)
>
> But more significantly we can use telnet to find out if we can access
> that site's port 80, testing more closely the access that IE requires.
>
> Hmm... there's a surprise here.
>
> First of all simply entering
>
> telnet www.skype.com 80
>
> can prove if you can reach that site and if there is a server there
> which is "listening" on port 80. The sign that both of those things
> are true is that the screen will clear and the cursor will move to
> the top left corner ready to accept your typing.
>
> Normally when I want to find out what is being sent from that port
> I just type:
> GET /
> (That's GET<space><slash><Enter>. By default you won't be
> able to see your typing.)
>
> However, in this case that turns out to contain:
>
> <example>
> <h2>Welcome to Joltid</h2>
> </example>
>
> and
>
> <quote>
> Joltid consists of the original management and development team
> behind KaZaA and the FastTrack peer-to-peer network.
> </quote>
>
> More importantly that page contains absolutely no reference to Skype
> nor any sign that it might do a redirect to it.
>
> So if you can get that far we will have to do something more
> to simulate better what IE would actually send. I won't bother
> complicating things now to give examples of what else you
> could type because I doubt that you are going to be able to get
> even as far as that Joltid page.
>
> BTW in order to capture whatever it is that you get from
> the GET request you can modify the telnet command
> to be:
>
> telnet -f telnet.txt www.skype.com 80
>
> where telnet.txt is just an arbitrary filename (and presumably
> not one which already exists or which contains data that you
> wanted to keep.)
>
>
> Good luck
>
> Robert
> ---
>
>
> > Thanks
> > Vicky
> >
> >
> >
> >
> > "Robert Aldwinckle" <robald@techemail.com> wrote in message
> > news:eSzLeDsaEHA.1732@TK2MSFTNGP09.phx.gbl...
> >> "Vicky" <vickyjackson@softhome.net> wrote in message
> >> news:%233%23hb8oaEHA.2016@TK2MSFTNGP09.phx.gbl...
> >> > Hi Robert
> >> >
> >> > I have checked all promptable settings in all zones of security and
> > tried to
> >> > access skype again, the only prompt I got was scripts to which I
> > answered No
> >> > and it went straight to the MSN search page which said "We cannot
find
> >> > www.skype.com" and gave a few surggestions none of which were related
to
> >> > skype. I no longer get " Page cannot be displayed" and I do not get
a
> >> > partial page or blank page. I have tried other links relating to
skype
> > but I
> >> > just get the MSN search page with the same message.
> >>
> >> Oh. That means we have to step back quite a bit.
> >> Now we have no proof after all that your DNS or HOSTS is working.
> >> Before when you got a prompt for scripting I assumed that
> >> you were entering a complete URL in the Address bar.
> >> I didn't consider the possibility that you weren't entering the
protocol
> >> prefix with it. Without the protocol prefix the "URL" becomes just
data
> >> to be passed to your AutoSearch if a DNS lookup for it fails.
> >> That, I suspect is what you are seeing. Unfortunately, the
diagnostics
> >> in IE and in Windows generally are very weak; otherwise you would have
> >> known that the prompt you were getting was for the MSN site instead
> >> of for the site you were hoping to reach.
> >>
> >> Rather than mess around trying to diagnose why this is happening
> >> I suggest you modify your HOSTS file to override whatever lookup
> >> your are getting. I don't know your OS and although you mentioned
> >> that ping timed out I'm not sure if that means the lookup timed out
> >> or the ping itself timed out. If the ping had included the IP
address
> >> it would mean that the lookup worked, though it might be too slow for
> >> IE's liking anyway. That's another reason for overriding the lookup.
> >>
> >> Here's how to do that using the output from my nslookup that I gave
> >> you previously. Insert the following line into your HOSTS file.
> >>
> >> 80.160.91.13 www.skype.com
> >>
> >>
> >> I think you should try to avoid inserting blank lines with it but I
don't
> > know
> >> for sure if that would cause a problem with it. However, it should be
> > safe
> >> to insert comment lines if you wish. Comment lines are lines which
> >> have the # charcter in column 1.
> >>
> >> Since I don't know your OS I suggest you reboot after making this
> >> change. After the reboot test your change by opening a command
> >> window and entering:
> >>
> >> ping -n 1 www.skype.com
> >>
> >> Rather than worrying about whether it times out what is important
> >> is whether the command displays the IP address with it.
> >>
> >> If your OS is NTx you could do a better test with telnet.
> >> In fact with some OS you may be able to do a similar test
> >> using a tool such as HyperTerminal. Hopefully these won't be needed
> >> if your HOSTS override works for you.
> >>
> >> If the HOSTS override works it indicates that there is a problem
which
> >> your ISP should be made aware of. E.g. they should find out whether
> >> their DNS is not caching records for that domain or whether there is
> >> simply a performance problem with their DNS lookup service.
>
> ...
>
>
- Next message: Blgibson: "IE6 Check Boxes Don't Display"
- Previous message: Bunta: "/?%20 added to typed urls"
- In reply to: Robert Aldwinckle: "Re: Cannot access a web page"
- Next in thread: Vicky: "Re: Cannot access a web page"
- Reply: Vicky: "Re: Cannot access a web page"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
