Post by thread:[PIC]: piclist.com web access: ng

It works fine for me. I'd tell you to search the archives for James's messages about how to verify why you can't, but as you can't hit the archive... (Courtesy of James) If your IP was blocked, you would get a message saying that your IP was blocked and explaining why. Can you reach: http://66.13.172.18/techref/piclist/index.htm ? If so, the problem is DNS. Can you reach: http://www.quickstepper.com ? If so, the problem is with the headers sent back by the PICList site. Quickstepper is on the same site but is a very simple, "out of the box" configuration of IIS. PICList has a batch of stuff installed. Why some people can deal with it and other can't is an ongoing mystery. It may be caused by a problem with some node in the route between your ISP and mine, or by your browser, or god knows what. If you can't reach any of them, your ISP or something between your ISP and mine is messed up. They will never believe this, but you can prove it to them by using a proxy server on another network. For example: http://www.the-cloak.com/Cloaked/+cfg=32/http://www.piclist.com/techref/picl ist/index.htm After you click on this link, it will ask you for some configuration info and you should check the URL in the lower left corner to ensure it is still www.piclist.com/techref/piclist/index.htm (sometimes the "http:" turns into "http%3A" or the "//" becomes a "/") then press the "Start Surfing" button. If you see the web site, search the page for the text "local time: " and make a note of the servers clock setting. It should show PDT (Pacific Daylight Time) or PST after daylight savings ends. Hit refresh and verify that it is changing. If you see the web site, and the time is updating, the web server is UP. If you cant see the site directly, then your ISP, or their upstream and nothing else, is the problem. Do a tracert and email it to your ISP's tech support along with your findings and this email. Josh -- A common mistake that people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools. -Douglas Adams On 7/8/05, Peter <spam_OUTplpTakeThisOuTactcom.co.il> wrote: > > I cannot access http://www.piclist.com and haven't been able to for some time > now (days). My previous caustic remark on this went unheeded (thanks). > Can anyone confirm that this is the case ?

Last August the piclist moved to mailman and I received an email welcoming me to the piclist (again) and giving me a new password. In May of this year I had a problem accessing the piclist and I requested a password reminder. It was the "new" password. Fast-forward to this month and I had a problem accessing the piclist: my (new) password was not a valid password on the server. So I looked up my previous password and tried that and I gained access to the list. My theory is that there was some information loss at the server end and a backup was used which contained my old password. Tom -----Original Message----- From: .....piclist-bouncesKILLspam@spam@mit.edu [piclist-bouncesKILLspammit.edu]On Behalf Of Peter Sent: Friday, July 08, 2005 3:08 PM To: pic microcontroller discussion list Subject: [PIC]: piclist.com web access: ng I cannot access http://www.piclist.com and haven't been able to for some time now (days). My previous caustic remark on this went unheeded (thanks). Can anyone confirm that this is the case ? thanks, Peter

> If your IP was blocked, you would get a message saying that your IP was > blocked and explaining why. > > Can you reach: > http://66.13.172.18/techref/piclist/index.htm ? If so, the > problem is DNS. > > Can you reach: > http://www.quickstepper.com ? If so, the problem is with the > headers sent > back by the PICList site. Quickstepper is on the same site but > is a very > simple, "out of the box" configuration of IIS. PICList has a > batch of stuff > installed. Why some people can deal with it and other can't is > an ongoing > mystery. It may be caused by a problem with some node in the > route between > your ISP and mine, or by your browser, or god knows what. > Josh -- Josh, I've been working this problem on and off with James for a long while and still haven't solved it. I can't reach http://www.piclist.com nor http://66.13.172.18/techref/piclist/index.htm but I can reach http://www.quickstepper.com. Any more troubleshooting hints? Thanks, Carey All Your Bucks Are Belong To US Govt

Hi Carey. I'm going to have to defer to James on this one. Hopefully he will pipe in soon. Josh -- A common mistake that people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools. -Douglas Adams On 7/8/05, Carey Fisher - NCS <.....careyfisherKILLspam.....ncsradio.com> wrote: > I've been working this problem on and off with James for a long > while and still haven't solved it. I can't reach http://www.piclist.com > nor http://66.13.172.18/techref/piclist/index.htm but I can > reach http://www.quickstepper.com.

In response to my own message and to suggestions posted here: >Can you reach: http://66.13.172.18/techref/piclist/index.htm ? If so, >the problem is DNS. Reach, yes, access, no. The page tries to load indefinitely without showing anything. >Can you reach: http://www.quickstepper.com ? If so, the problem is with >the headers sent back by the PICList site. Yes, but all the images show blank, and when I try to load them by force the same as above occurs (tries to load indefinitely) >Can you reach: http://www.quickstepper.com ? If so, the problem is with >the headers sent back by the PICList site. Yes, and it all works (with all the switches in default position). Further experimentation reveals (using lynx): user input -> http://www.piclist.com <- cookie ASPSESSIONID=EOILDICDCAILHP redirect -> www.piclist.com/techref/piclist/index.htm <- 500 Server Error <- HTTP/1.1 Application Restarting again, with wget: plp@plp:~/piclist$ wget -s http://www.piclist.com --10:42:51-- http://www.piclist.com/ => `index.html' Resolving http://www.piclist.com... 66.13.172.18 Connecting to http://www.piclist.com[66.13.172.18]:80... connected. HTTP request sent, awaiting response... 302 Object moved Location: http://www.piclist.com/techref/piclist/index.htm [following] --10:42:52-- www.piclist.com/techref/piclist/index.htm => `index.htm' Connecting to http://www.piclist.com[66.13.172.18]:80... connected. HTTP request sent, awaiting response... 500 Server Error 10:42:52 ERROR 500: Server Error. Peter