grc.com continuously down?

  • Thread starter Thread starter fred ma
  • Start date Start date
F

fred ma

Anyone know what's the deal with grc.com? I haven't been able to
connect to that server for days.

Fred
 
Anyone know what's the deal with grc.com? I haven't been able to
connect to that server for days.

Fred


Wouldn't be the first time GRC.com was brought down.
http://www.urlbee.com?360

btw, I have no prob getting to the grc.com site. Hope the problem has
subsided for you also.

later,

tom
 
Anyone know what's the deal with grc.com? I haven't been able to
connect to that server for days.

Fred

What's so special about going to the Gibson site on a routine basis? ;-)

Duane :)
 
Wouldn't be the first time GRC.com was brought down.
http://www.urlbee.com?360

btw, I have no prob getting to the grc.com site. Hope the problem has
subsided for you also.

I think I read that before. Eye-opening.

I can get onto the grc.com website, but I can't connect to its
news server. Haven'te been able to for days.

Fred
 
fred ma said:
I can get onto the grc.com website, but I can't connect to its
news server. Haven'te been able to for days.

I'm able to connect to the news server at this moment, and haven't noticed
any problems in recent days.

Regards,
Ian.
 
Ionizer said:
I'm able to connect to the news server at this moment, and haven't noticed
any problems in recent days.

Regards,
Ian.

Thanks for the info, Ian. I'm perplexed. I tried 2 different newsreaders
from 2 different locations -- one is through a university campus LAN
(connect to the internet), and another is via an off-campus commercial
dailup service provider. Both experience the same problem. I'm trying
to access the groups grc.security, grc.security.software, and grc.security.hardware.

I'm going to have to bang my head against the wall on this a bit, when I have
a bit more time. Thanks again.

Fred
 
The voice of "fred ma" drifted in on the cyber-winds,
from the sea of virtual chaos...
Anyone know what's the deal with grc.com? I haven't been able to
connect to that server for days.


Nothing wrong with it, it's working fine here...

Have you tried to connect directly with it's IP adress?
(69.28.135.241)
 
fred ma said:
Thanks for the info, Ian. I'm perplexed. I tried 2 different newsreaders
from 2 different locations -- one is through a university campus LAN
(connect to the internet), and another is via an off-campus commercial
dailup service provider. Both experience the same problem. I'm trying
to access the groups grc.security, grc.security.software, and grc.security.hardware.

I'm going to have to bang my head against the wall on this a bit, when I have
a bit more time. Thanks again.

Hi, Fred:

grc.security.hardware is a pretty quiet group, but the security.software
shows a pretty much continuous flow of posts; 11 since 9:00PM yesterday-
the most recent at 2:51 this morning. And judging by the posting activity
in grc.security, there doesn't seem to have been any noticeable news
server downtime this week.

Best of luck with that head banging thing.

Regards,
Ian.
 
Ionizer said:
grc.security.hardware is a pretty quiet group, but the security.software
shows a pretty much continuous flow of posts; 11 since 9:00PM yesterday-
the most recent at 2:51 this morning. And judging by the posting activity
in grc.security, there doesn't seem to have been any noticeable news
server downtime this week.

Best of luck with that head banging thing.

Regards,
Ian.

Thanks, Ian, it seems to work OK if I use the IP address (69.28.135.241).

Fred
 
Tech said:
Nothing wrong with it, it's working fine here...

Have you tried to connect directly with it's IP adress?
(69.28.135.241)

Huh. That's weird. The IP address works fine. Not sure
why things would have changed lately (the name grc.com
worked fine previously). Anyway, it's fixed, thanks to
your detail above

Fred
 
fred said:
...it's fixed, thanks to your detail above

Looks like I spoke too soon. I can retrieve headers, but can't
post. Server doesn't respond and mozilla times out. Looks
like I got me some head banging some time.

Fred
 
fred ma said:
Looks like I spoke too soon. I can retrieve headers, but can't
post. Server doesn't respond and mozilla times out. Looks
like I got me some head banging some time.

Fred


When you do a traceroute to their news server, what hosts are listed in
the route? Could be you have a route from your area that results in
hitting the same host that is ****ing up. I haven't tried to use
news.grc.com (which I assume is their news server since that host exists
in my DNS). A traceroute to that host from me has the following hosts
in the route:

1 1 ms <1 ms <1 ms <mylocalIP>
2 11 ms 11 ms 11 ms <mycablemodemIP>
3 11 ms 15 ms 10 ms bar01-f1-1-0.broohe1.mn.attbb.net
[24.31.1.141]
4 11 ms 11 ms 11 ms 24.31.2.107
5 24 ms 34 ms 26 ms 12.125.74.25
6 27 ms 24 ms 25 ms gbr6-p80.sl9mo.ip.att.net
[12.123.24.238]
7 28 ms 25 ms 27 ms tbr2-p013601.sl9mo.ip.att.net
[12.122.11.125]
8 69 ms 83 ms 67 ms tbr2-cl2.la2ca.ip.att.net [12.122.10.14]
9 64 ms 64 ms 83 ms gar1-p3100.lsnca.ip.att.net
[12.123.199.229]
10 65 ms 65 ms 65 ms 12.119.138.62 <--- also AT&T
11 74 ms 74 ms 77 ms so7-5-0.jr1.phx1.llnw.net [69.28.172.62]
12 75 ms 76 ms 96 ms ge1-0-0-5.jr1.phx3.llnw.net
[69.28.139.254]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.

I'm a Comcast user that got migrated from AT&T hence the ATT.net hosts
in my route (and the unresolved 12.119.138.62 is also AT&T). Once the
trace gets to llnw.net, I get timeouts. The route to grc.com goes
through Verio.net instead of llnw.net so it could be Gibson has his news
server on a different network than for his web site, but I don't know if
his news server is hosted on the llnw.net domain or if that is just a
host in the route that I get which seems unresponsive. If Gibson's news
server is hosted by llnw.net, you bitching to them won't help as they
probably will only respond to requests for service from their customers,
so you would have to bitch to Gibson to get llnw.net to fix their
hosting service for him. I used various hosts around the USA that were
listed at www.traceroute.org to see what routes would show up from there
to news.grc.com (69.28.135.241) and they all hit llnw.net (and died
there, too).
 
_Vanguard_ said:
fred ma said:
Looks like I spoke too soon. I can retrieve headers, but can't
post. Server doesn't respond and mozilla times out. Looks
like I got me some head banging some time.

When you do a traceroute to their news server, what hosts are listed in
the route? Could be you have a route from your area that results in
hitting the same host that is ****ing up. I haven't tried to use
news.grc.com (which I assume is their news server since that host exists
in my DNS). A traceroute to that host from me has the following hosts
in the route:

1 1 ms <1 ms <1 ms <mylocalIP>
2 11 ms 11 ms 11 ms <mycablemodemIP>
3 11 ms 15 ms 10 ms bar01-f1-1-0.broohe1.mn.attbb.net
[24.31.1.141]
4 11 ms 11 ms 11 ms 24.31.2.107
5 24 ms 34 ms 26 ms 12.125.74.25
6 27 ms 24 ms 25 ms gbr6-p80.sl9mo.ip.att.net
[12.123.24.238]
7 28 ms 25 ms 27 ms tbr2-p013601.sl9mo.ip.att.net
[12.122.11.125]
8 69 ms 83 ms 67 ms tbr2-cl2.la2ca.ip.att.net [12.122.10.14]
9 64 ms 64 ms 83 ms gar1-p3100.lsnca.ip.att.net
[12.123.199.229]
10 65 ms 65 ms 65 ms 12.119.138.62 <--- also AT&T
11 74 ms 74 ms 77 ms so7-5-0.jr1.phx1.llnw.net [69.28.172.62]
12 75 ms 76 ms 96 ms ge1-0-0-5.jr1.phx3.llnw.net
[69.28.139.254]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.

I'm a Comcast user that got migrated from AT&T hence the ATT.net hosts
in my route (and the unresolved 12.119.138.62 is also AT&T). Once the
trace gets to llnw.net, I get timeouts. The route to grc.com goes
through Verio.net instead of llnw.net so it could be Gibson has his news
server on a different network than for his web site, but I don't know if
his news server is hosted on the llnw.net domain or if that is just a
host in the route that I get which seems unresponsive. If Gibson's news
server is hosted by llnw.net, you bitching to them won't help as they
probably will only respond to requests for service from their customers,
so you would have to bitch to Gibson to get llnw.net to fix their
hosting service for him. I used various hosts around the USA that were
listed at www.traceroute.org to see what routes would show up from there
to news.grc.com (69.28.135.241) and they all hit llnw.net (and died
there, too).

I also hit a wall at llnw.net:

traceroute to news.grc.com (69.28.135.241), 30 hops max, 40 byte packets
1 salvador (134.117.9.192) 1.746 ms 6.441 ms 1.533 ms
2 me172-gate.carleton.ca (134.117.172.1) 6.275 ms 1.376 ms 1.301 ms
3 134.117.7.3 (134.117.7.3) 4.889 ms 4.966 ms 1.413 ms
4 134.117.219.248 (134.117.219.248) 6.470 ms 1.177 ms 0.868 ms
5 filter-campus.carleton.ca (134.117.6.5) 9.707 ms 1.317 ms 0.947 ms
6 134.117.3.1 (134.117.3.1) 4.243 ms 2.469 ms 3.054 ms
7 AL-7304-GigE0-1978.telecomottawa.net (142.46.196.129) 3.832 ms 2.263 ms 3.393 ms
8 AL-GSR-GigE0-2.telecomottawa.net (142.46.200.2) 3.003 ms 3.599 ms 5.578 ms
9 FL-GSR-GigE0-1-100.telecomottawa.net (142.46.200.17) 4.914 ms 3.476 ms 3.832 ms
10 h209-71-218-109.gtconnect.net (209.71.218.109) 6.081 ms 5.194 ms 4.876 ms
11 h216-18-112-133.gtconnect.net (216.18.112.133) 3.658 ms 3.605 ms 5.110 ms
12 h216-18-72-129.gtcust.grouptelecom.net (216.18.72.129) 19.326 ms 26.752 ms 13.471 ms
13 66.59.191.174 (66.59.191.174) 13.844 ms 38.401 ms 13.350 ms
14 ge1-2-0.jr1.iad.llnw.net (206.223.115.123) 21.157 ms 20.140 ms 18.902 ms
15 so5-0-3.jr1.lax.llnw.net (69.28.172.18) 85.382 ms 85.078 ms 85.410 ms
16 so7-0-0.jr1.phx1.llnw.net (69.28.172.42) 137.167 ms so7-6-0.jr1.phx1.llnw.net (69.28.172.101) 110.652 ms 109.538 ms
17 ge1-0-0-5.jr1.phx3.llnw.net (69.28.139.254) 111.775 ms ge1-1-0.jr1.phx3.llnw.net (69.28.139.250) 110.277 ms 113.833 ms
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

Funny thing is that I can retrieve headers and read postings. I'll forward
this to a feedback contact at the Gibson website. Thanks.

Fred
 
fred ma said:
Thanks, Ian, it seems to work OK if I use the IP address (69.28.135.241).

Fred

If the IP address works but the FQDN does not (news.grc.com) then here are
some possibilities:
- you have an entry in your hosts file for news.grc.com
- you are running a dns client that caches
(if you are on XP, stop and then disable the DNS Client service) and
then do ipconfig /flushdns
- your dns servers are brain dead
etc
 
The voice of "fred ma" drifted in on the cyber-winds,
from the sea of virtual chaos...
Looks like I spoke too soon. I can retrieve headers, but can't
post. Server doesn't respond and mozilla times out. Looks
like I got me some head banging some time.


Two points...
- Check your your host file for a "news.grc.com" entry
- And read "Authenticated Logon Before Posting" in GNF

The relivent part:

From: Steve Gibson...

"We have been experiencing increasing trouble with unsolicited
SPAMMING across our news server, and it appears to be a trend
that's on the rise. Since this unwanted newsgroup spamming can
be largely if not completely eliminated by requiring that people
who wish to post configure their news reading software to
'Authenticate' itself by providing an identical username and
password, we will shortly be adopting this posting requirement
for the GRC server.
 
The voice of "fred ma" drifted in on the cyber-winds,
from the sea of virtual chaos...
I also hit a wall at llnw.net:
Funny thing is that I can retrieve headers and read postings.
I'll forward this to a feedback contact at the Gibson website.


Gibson's server isn't tracable form the outside...
He turned that off long ago, back when it was used to DoS him.

Second, he did move his news server recently so it would be outside his
network. Read "WELCOME to our new NEWS server" in GNF...
 
gram said:
You now must set up a "CECIL-ID" to post, take a look at imilly's site
here:
http://www.imilly.com/noregrets.htm#guide

Thanks, gram pappy & Tech Zero. I tried this and even restarted mozilla.
Still having problems posting. Same username & password, and got the
password manager to remember both. Set the server settings so that
login in required. I will have to do further trouble-shooting.
Unfortunately, I can't do so at the moment. Appreciate your suggestions.

Fred
 
The voice of "fred ma" drifted in on the cyber-winds,
from the sea of virtual chaos...
I tried this and even restarted mozilla. Still having problems
posting. Same username & password, and got the password manager
to remember both. Set the server settings so that login in required.


Unfortunatly Mozilla isn't happy with Steve's set-up. You need to set
it to "requires Atentication", and "Ask each time" instead.

That means it'll be an extra step post, but you can still post.
 
Back
Top