I need a quick favor, site supposedly not accessable

[tatata9999]

Just talked to someone, he said he couldn't access my site (I was
'shocked'), could you people give it a try? I'm sorry it's off topic
but I'm speaking of the truth, http://www.mytata.net/
and post feedback like your location. Many thanks.

Once again, my apologies if some of you feel bad about this.

[David E. Ross]

On 10/22/2007 2:33 PM, ta********@gmail.com wrote:

Just talked to someone, he said he couldn't access my site (I was
'shocked'), could you people give it a try? I'm sorry it's off topic
but I'm speaking of the truth, http://www.mytata.net/
and post feedback like your location. Many thanks.

Once again, my apologies if some of you feel bad about this.

I can view the page in southern California. However, a trace-route dies
after the 11th hop. While the trace-route results below used a 5 second
time-out, changing to a 15 second time-out gave the same results.

TraceRoute - Monday, October 22, 2007 16:38:50
Generated by CyberKit Version 2.5
Copyright © 1996-2000 by Luc Neijens

Address: MYTATA.NET
Number of Packets: 1
Packet size: 64
Trace Hop 1 through 25
Timeout: 5
Resolve Addresses: Yes
Don't Fragment: No

#1 apx8104sys.lsan.mdsg-pacwest.com (63.93.65.84)
#2 csc6501r-vlan203.lsan.mdsg-pacwest.com (10.103.203.1)
#3 g0-10.na22.b000899-0.lax04.atlas.cogentco.com (38.99.205.85)
#4 g9-2.102-core01.lax04.atlas.cogentco.com (38.112.39.33)
#5 g9-2.102-core01.lax04.atlas.cogentco.com (38.112.39.33)
#6 t3-1.ccr01.lax04.atlas.cogentco.com (154.54.24.74)
#7 g3-0-0.core01.lax01.atlas.cogentco.com (154.54.1.33)
#8 p5-0.core01.san01.atlas.cogentco.com (66.28.4.78)
#9 v3804.na01.b006587-1.san01.atlas.cogentco.com (38.20.38.94)
#10 vitalwerks.demarc.cogentco.com (38.99.200.162)
#11 vitalwerks.demarc.cogentco.com (38.99.200.162)
#12 No response ()
#13 No response ()
#14 No response ()
#15 No response ()
#16 No response ()

Statistics: Out 17, in 11, loss 35%, times (min/avg/max) 156/157/171 ms

--
David E. Ross
<http://www.rossde.com/>

Natural foods can be harmful: Look at all the
people who die of natural causes.

[tatata9999]

On Oct 22, 7:44 pm, "David E. Ross" <[e-mail]:

On 10/22/2007 2:33 PM, [e-mail] wrote:

Just talked to someone, he said he couldn't access my site (I was
'shocked'), could you people give it a try? I'm sorry it's off topic
but I'm speaking of the truth,http://www.mytata.net/
and post feedback like your location. Many thanks.

Once again, my apologies if some of you feel bad about this.

I can view the page in southern California. However, a trace-route dies
after the 11th hop. While the trace-route results below used a 5 second
time-out, changing to a 15 second time-out gave the same results.

TraceRoute - Monday, October 22, 2007 16:38:50
Generated by CyberKit Version 2.5
Copyright © 1996-2000 by Luc Neijens

Address: MYTATA.NET
Number of Packets: 1
Packet size: 64
Trace Hop 1 through 25
Timeout: 5
Resolve Addresses: Yes
Don't Fragment: No

#1 apx8104sys.lsan.mdsg-pacwest.com (63.93.65.84)
#2 csc6501r-vlan203.lsan.mdsg-pacwest.com (10.103.203.1)
#3 g0-10.na22.b000899-0.lax04.atlas.cogentco.com (38.99.205.85)
#4 g9-2.102-core01.lax04.atlas.cogentco.com (38.112.39.33)
#5 g9-2.102-core01.lax04.atlas.cogentco.com (38.112.39.33)
#6 t3-1.ccr01.lax04.atlas.cogentco.com (154.54.24.74)
#7 g3-0-0.core01.lax01.atlas.cogentco.com (154.54.1.33)
#8 p5-0.core01.san01.atlas.cogentco.com (66.28.4.78)
#9 v3804.na01.b006587-1.san01.atlas.cogentco.com (38.20.38.94)
#10 vitalwerks.demarc.cogentco.com (38.99.200.162)
#11 vitalwerks.demarc.cogentco.com (38.99.200.162)
#12 No response ()
#13 No response ()
#14 No response ()
#15 No response ()
#16 No response ()

Statistics: Out 17, in 11, loss 35%, times (min/avg/max) 156/157/171 ms

--
David E. Ross
<http://www.rossde.com/>

Natural foods can be harmful: Look at all the
people who die of natural causes.

Thank you, David. Are you suggesting that the physical distance
between Domain Name Server and a web server machine has quite a bit to
do with data service speed and quality? The longer distance it's
more likely more hops hence more likely loss of data? With the analog
of 'weak link'?

Also, since we're at it, what command option and/or options would be
most useful in terms of server security using the NETSTAT utility?

Does that the following suggest?
prot local foreign pid
TCP [::] :135 [::]:0 listening 0
:1028

At one point, it listed googlebot as well (I thought they are running
at their site, just scanning sites...)

Would truly appreciate your enlighting.

[David E. Ross]

On 10/22/2007 7:53 PM, ta********@gmail.com wrote:

On Oct 22, 7:44 pm, "David E. Ross" <[e-mail]:

>On 10/22/2007 2:33 PM, [e-mail] wrote:

>>Just talked to someone, he said he couldn't access my site (I was
'shocked'), could you people give it a try? I'm sorry it's off topic
but I'm speaking of the truth,http://www.mytata.net/
and post feedback like your location. Many thanks.
Once again, my apologies if some of you feel bad about this.

I can view the page in southern California. However, a trace-route dies
after the 11th hop. While the trace-route results below used a 5 second
time-out, changing to a 15 second time-out gave the same results.

TraceRoute - Monday, October 22, 2007 16:38:50
Generated by CyberKit Version 2.5
Copyright © 1996-2000 by Luc Neijens

Address: MYTATA.NET
Number of Packets: 1
Packet size: 64
Trace Hop 1 through 25
Timeout: 5
Resolve Addresses: Yes
Don't Fragment: No

#1 apx8104sys.lsan.mdsg-pacwest.com (63.93.65.84)
#2 csc6501r-vlan203.lsan.mdsg-pacwest.com (10.103.203.1)
#3 g0-10.na22.b000899-0.lax04.atlas.cogentco.com (38.99.205.85)
#4 g9-2.102-core01.lax04.atlas.cogentco.com (38.112.39.33)
#5 g9-2.102-core01.lax04.atlas.cogentco.com (38.112.39.33)
#6 t3-1.ccr01.lax04.atlas.cogentco.com (154.54.24.74)
#7 g3-0-0.core01.lax01.atlas.cogentco.com (154.54.1.33)
#8 p5-0.core01.san01.atlas.cogentco.com (66.28.4.78)
#9 v3804.na01.b006587-1.san01.atlas.cogentco.com (38.20.38.94)
#10 vitalwerks.demarc.cogentco.com (38.99.200.162)
#11 vitalwerks.demarc.cogentco.com (38.99.200.162)
#12 No response ()
#13 No response ()
#14 No response ()
#15 No response ()
#16 No response ()

Statistics: Out 17, in 11, loss 35%, times (min/avg/max) 156/157/171 ms

--
David E. Ross
<http://www.rossde.com/>

Natural foods can be harmful: Look at all the
people who die of natural causes.

Thank you, David. Are you suggesting that the physical distance
between Domain Name Server and a web server machine has quite a bit to
do with data service speed and quality? The longer distance it's
more likely more hops hence more likely loss of data? With the analog
of 'weak link'?

Also, since we're at it, what command option and/or options would be
most useful in terms of server security using the NETSTAT utility?

Does that the following suggest?
prot local foreign pid
TCP [::] :135 [::]:0 listening 0
:1028

At one point, it listed googlebot as well (I thought they are running
at their site, just scanning sites...)

Would truly appreciate your enlighting.

In the Internet, "distance" is not measured physically. It's measured
by the number of routers and servers traversed along the backbone
communication lines. Go to my
<http://www.rossde.com/internet/surf.html#speedand scroll to the very
last paragraph for an explanation.

Internet distance affects speed. It may also affect the ability to
connect if a server or router along the path fails (your "weak link").
However, connectivity might still be possible with such a failure
because there are often redundant paths through the Internet. If there
is connectivity, there is rarely a loss of data. Since data travel in
packets, the low probability of data loss (the loss of a packet) would
generally affect only the transmission of exceptionally large files,
much larger than Web pages.

It's been far too long since I used Netstat, and even then I made little
use of it. I can't help you with it.

--
David E. Ross
<http://www.rossde.com/>

Natural foods can be harmful: Look at all the
people who die of natural causes.