sheila said:
I having trouble view some websites. Mostly facebook and bebo. When I go on
these website I get a blank white page. I don't get messages or errors when
i go on the website. I downloaded firefox and when i went on the website
facebook and bebo it directed me to another site other than facebook and bebo.
I would like if some could help me with this. I am running XP.
thanks
EggHeadCafe - .NET Developer Portal of Choice
http://www.eggheadcafe.com
So you won't feel totally ignored here, let me suggest you download
a copy of "Wireshark". Wireshark is the tool also known as Ethereal,
and it is a packet sniffer. It traces packets for me, on the
Ethernet cable that goes to my router and ADSL modem.
http://www.wireshark.org/about.html or if it doesn't work, try
http://128.121.50.122/about.html
Install the package and start the program. Go to Capture:Interfaces,
and that will bring up a dialog listing whatever network interfaces
exist on the computer. Then, click the "Start" button, just before you
are ready to capture some packets. Wireshark runs continuously, until
you tell it to stop, and also displays and decodes the packets for
viewing. It allows you to examine what info is coming and going
from your computer. (Note - some malware is clever enough to know
that Wireshark is running, so it is also possible for the behavior
of your situation to change, once Wireshark is running. The best
malware is very clever.)
In View:Time_Display_Format, you can select how the time stamp will
be shown. Time probably isn't too important at this point.
In View:Name_Resolution, only two of the options will be turned on.
If you turn on the middle one, "Enable for Network Layer", that
will allow the numeric IP addresses, to be turned into symbolic
addresses in the trace. All three items in the list are enabled
on mine right now. (In the sample trace below, my 192.168.x.x
private addresses cannot be converted to names, because they
have no name equivalent.)
So, now start up Firefox. Type in
http://www.bebo.com but
don't press return quite yet. Go to Wireshark and "Start" the
capture for the network interface you are using. Then, go back to Firefox,
and press return. Firefox will now try to go to Bebo. Using Wireshark,
you should be able to see where, in fact, it is actually going.
Once the page has finished attempting to render, you can use
Capture:Stop to stop tracing packets. Either that, or note what
packet number in the Wireshark screen, corresponds to where
the networking activity has stopped.
Both Facebook and Bebo.com are not simple or small web sites. They
used complicated network setups (at least more complicated than I
can understand). You will see a number of strange addresses being
used, and those should not be anything to get alarmed about. There
will be a few which are setting cookies in your browser (so advertisers
can trace the fact you visited the site, and trace your preferences
and so on). But perhaps you'll see some strange addresses
present, which will help you figure out exactly what is
happening.
It could be you have some malware (virus, trojan) on the computer,
which has worked some magic. The kind of trace you see in Wireshark,
may help you determine whether the problem if malware, or something
lower level, like an OS problem.
I have included the trace from my computer to
http://www.bebo.com
Note 192.168.1.1 is my router, which gets consulted for network
lookups (DNS). 192.168.1.177 is the local address of my computer
(192.168.x.x is not routable, so you cannot ping me from the
Internet via that address - that address is only valid locally here)
I had to snip a lot of useful info, to make this fit. The main
value of this to you right now, is it shows what a "normal" set of
addresses for source and destination would look like.
doubleclick.net is for tracing your preferences, so the advertisers
can build a profile of you. Presumably tags.expo9.exponential.com is
part of that equation. akamai.net is a large provider of hosting
services, and what seemed to be coming from them, is images and
icons of some sort. So the trace really isn't that complicated.
If you see addresses other than these, they could be important.
Source Destination Protocol Info
192.168.1.177
www.bebo.com TCP 4808 > http [SYN]
www.bebo.com 192.168.1.177 TCP http > 4808 [SYN,
192.168.1.177
www.bebo.com TCP 4808 > http [ACK]
192.168.1.177
www.bebo.com HTTP GET / HTTP/1.1
www.bebo.com 192.168.1.177 TCP http > 4808 [ACK]
www.bebo.com 192.168.1.177 TCP [TCP segment of a
www.bebo.com 192.168.1.177 TCP [TCP segment of a
192.168.1.177
www.bebo.com TCP 4808 > http [ACK]
www.bebo.com 192.168.1.177 TCP [TCP segment of a
192.168.1.177
www.bebo.com TCP 4808 > http [ACK]
www.bebo.com 192.168.1.177 TCP [TCP Previous seg
192.168.1.177
www.bebo.com TCP [TCP Dup ACK 12#1
www.bebo.com 192.168.1.177 HTTP [TCP Retransmissi
192.168.1.177
www.bebo.com TCP 4808 > http [ACK]
192.168.1.177
www.bebo.com TCP 4808 > http [FIN,
www.bebo.com 192.168.1.177 TCP http > 4808 [ACK]
192.168.1.177 192.168.1.1 DNS Standard query A
192.168.1.1 192.168.1.177 DNS Standard query
192.168.1.177 ad.3ad.doubleclick.net TCP 4811 > http [SYN
ad.3ad.doubleclick.net 192.168.1.177 TCP http > 4811 [SYN
192.168.1.177 ad.3ad.doubleclick.net TCP 4811 > http [ACK
192.168.1.177 ad.3ad.doubleclick.net HTTP GET /adj/bebo.ho
ad.3ad.doubleclick.net 192.168.1.177 HTTP HTTP/1.0 200 OK
192.168.1.177 ad.3ad.doubleclick.net TCP 4811 > http [ACK
192.168.1.177 ad.3ad.doubleclick.net TCP 4811 > http [FIN
192.168.1.177 192.168.1.1 DNS Standard query A
ad.3ad.doubleclick.net 192.168.1.177 TCP http > 4811 [ACK
192.168.1.1 192.168.1.177 DNS Standard query
192.168.1.177 tags.expo9.exponential.com TCP 4814 > http
tags.expo9.exponential.com 192.168.1.177 TCP http > 4814
192.168.1.177 tags.expo9.exponential.com TCP 4814 > http
192.168.1.177 tags.expo9.exponential.com HTTP GET /j.ad?
tags.expo9.exponential.com 192.168.1.177 TCP http > 4814
tags.expo9.exponential.com 192.168.1.177 TCP [TCP segment
tags.expo9.exponential.com 192.168.1.177 TCP [TCP segment
192.168.1.177 tags.expo9.exponential.com TCP 4814 > http
tags.expo9.exponential.com 192.168.1.177 HTTP HTTP/1.0 200
tags.expo9.exponential.com 192.168.1.177 TCP http > 4814
192.168.1.177 tags.expo9.exponential.com TCP 4814 > http
192.168.1.177 tags.expo9.exponential.com TCP 4814 > http
192.168.1.177 192.168.1.1 DNS Standard query A
192.168.1.177 192.168.1.1 DNS Standard query A
192.168.1.177 192.168.1.1 DNS Standard query A
192.168.1.177 192.168.1.1 DNS Standard query A
192.168.1.177
www.bebo.com TCP 4820 > http [SYN
192.168.1.1 192.168.1.177 DNS Standard query
192.168.1.1 192.168.1.177 DNS Standard query
tags.expo9.exponential.com 192.168.1.177 TCP http > 4814
192.168.1.177 a200.c.akamai.net TCP 4823 > http [SYN
192.168.1.177 a500.c.akamai.net TCP 4826 > http [SYN
192.168.1.177 a500.c.akamai.net TCP 4827 > http [SYN
192.168.1.177 a200.c.akamai.net TCP 4828 > http [SYN
192.168.1.1 192.168.1.177 DNS Standard query
192.168.1.177 a889.g.akamai.net TCP 4830 > http [SYN
192.168.1.1 192.168.1.177 DNS Standard query
192.168.1.177 a300.c.akamai.net TCP 4832 > http [SYN
www.bebo.com 192.168.1.177 TCP http > 4820 [SYN
192.168.1.177
www.bebo.com TCP 4820 > http [ACK
a200.c.akamai.net 192.168.1.177 TCP http > 4823 [SYN
192.168.1.177 a200.c.akamai.net TCP 4823 > http [ACK
192.168.1.177
www.bebo.com HTTP GET /FlashFrame.
a500.c.akamai.net 192.168.1.177 TCP http > 4826 [SYN
192.168.1.177 a500.c.akamai.net TCP 4826 > http [ACK
192.168.1.177 a200.c.akamai.net HTTP GET /029b/6/smal
a500.c.akamai.net 192.168.1.177 TCP http > 4827 [SYN
192.168.1.177 a500.c.akamai.net TCP 4827 > http [ACK
a200.c.akamai.net 192.168.1.177 TCP http > 4828 [SYN
192.168.1.177 a200.c.akamai.net TCP 4828 > http [ACK
192.168.1.177 a500.c.akamai.net HTTP GET /014b/13/sma
192.168.1.177 a500.c.akamai.net HTTP GET /032b/7/smal
192.168.1.177 a200.c.akamai.net HTTP GET /037b/6/smal
a200.c.akamai.net 192.168.1.177 TCP http > 4823 [ACK
a200.c.akamai.net 192.168.1.177 TCP [TCP segment of
a200.c.akamai.net 192.168.1.177 HTTP HTTP/1.1 200 OK
192.168.1.177 a200.c.akamai.net TCP 4823 > http [ACK
a500.c.akamai.net 192.168.1.177 TCP http > 4826 [ACK
a500.c.akamai.net 192.168.1.177 TCP [TCP segment of
a500.c.akamai.net 192.168.1.177 HTTP HTTP/1.1 200 OK
192.168.1.177 a500.c.akamai.net TCP 4826 > http [ACK
a500.c.akamai.net 192.168.1.177 TCP http > 4827 [ACK
a200.c.akamai.net 192.168.1.177 TCP http > 4828 [ACK
a200.c.akamai.net 192.168.1.177 TCP [TCP segment of
a200.c.akamai.net 192.168.1.177 HTTP HTTP/1.1 200 OK
192.168.1.177 a200.c.akamai.net TCP 4828 > http [ACK
a500.c.akamai.net 192.168.1.177 TCP [TCP segment of
a500.c.akamai.net 192.168.1.177 HTTP HTTP/1.1 200 OK
192.168.1.177 a500.c.akamai.net TCP 4827 > http [ACK
a889.g.akamai.net 192.168.1.177 TCP http > 4830 [SYN
192.168.1.177 a889.g.akamai.net TCP 4830 > http [ACK
a300.c.akamai.net 192.168.1.177 TCP http > 4832 [SYN
192.168.1.177 a300.c.akamai.net TCP 4832 > http [ACK
192.168.1.177 a889.g.akamai.net HTTP GET /media/10436
192.168.1.177 a300.c.akamai.net HTTP GET /038a/15/sma
www.bebo.com 192.168.1.177 TCP http > 4820 [ACK
www.bebo.com 192.168.1.177 TCP [TCP Previous se
192.168.1.177
www.bebo.com TCP [TCP Dup ACK 63#
www.bebo.com 192.168.1.177 HTTP [TCP Out-Of-Orde
192.168.1.177
www.bebo.com TCP 4820 > http [ACK
192.168.1.177
www.bebo.com TCP 4820 > http [FIN
a889.g.akamai.net 192.168.1.177 TCP http > 4830 [ACK
a300.c.akamai.net 192.168.1.177 TCP http > 4832 [ACK
a889.g.akamai.net 192.168.1.177 TCP [TCP segment of
a889.g.akamai.net 192.168.1.177 TCP [TCP segment of
192.168.1.177 a889.g.akamai.net TCP 4830 > http [ACK
a889.g.akamai.net 192.168.1.177 TCP [TCP segment of
192.168.1.177 a889.g.akamai.net TCP 4830 > http [ACK
a889.g.akamai.net 192.168.1.177 TCP [TCP segment of
a889.g.akamai.net 192.168.1.177 TCP [TCP segment of
192.168.1.177 a889.g.akamai.net TCP 4830 > http [ACK
a889.g.akamai.net 192.168.1.177 TCP [TCP segment of
192.168.1.177 a889.g.akamai.net TCP 4830 > http [ACK
www.bebo.com 192.168.1.177 TCP http > 4820 [ACK
a300.c.akamai.net 192.168.1.177 TCP [TCP segment of
a300.c.akamai.net 192.168.1.177 HTTP HTTP/1.1 200 OK
192.168.1.177 a300.c.akamai.net TCP 4832 > http [ACK
a889.g.akamai.net 192.168.1.177 TCP [TCP segment of
a889.g.akamai.net 192.168.1.177 TCP [TCP segment of
192.168.1.177 a889.g.akamai.net TCP 4830 > http [ACK
a889.g.akamai.net 192.168.1.177 TCP [TCP segment of
a889.g.akamai.net 192.168.1.177 TCP [TCP segment of
192.168.1.177 a889.g.akamai.net TCP 4830 > http [ACK
a889.g.akamai.net 192.168.1.177 TCP [TCP segment of
a889.g.akamai.net 192.168.1.177 HTTP HTTP/1.1 200 OK
The purpose of doing this kind of trace, is to try to guess what
is happening. If the trace is virtually blank, it could be that
you have a DNS problem, but a lot of other networking stuff wouldn't
work for you if that was the case. I expect you will get an
"interesting" trace.
Hope that helps,
Paul
