Skip to main content ↑ ↓
Topic: What's happened to the Scriptorium? (Read 3837 times) previous topic - next topic

What's happened to the Scriptorium?

I get a "Can't connect to server" error.  Is the server offline.  This is the 2nd day in a row.

Anyone else?

Re: What's happened to the Scriptorium?

Reply #1 –
Works fine from here.

Re: What's happened to the Scriptorium?

Reply #2 –
I got onto the Scriptorium just fine both yesterday and right now.  Have you mistyped the path?

http://nwc-scriptorium.org/

Re: What's happened to the Scriptorium?

Reply #3 –
Hmmm. I'll have to have a word with my ISP . . .

I simply can't connect.  This has never happened before.

Re: What's happened to the Scriptorium?

Reply #4 –
It works OK now.

Re: What's happened to the Scriptorium?

Reply #5 –
Francis, you might want to open a console window (Start, Run, CMD), then type "tracert http://nwc-scriptorium.org/" to show your system's path to the scripto. If the trace never begins, then it is probably a DNS issue. Otherwise, it will show the route that is failing.

See also:
- http://support.microsoft.com/support/kb/articles/Q162/3/26.asp

Re: What's happened to the Scriptorium?

Reply #6 –
OK.  Here's what I found:
- the front page of the scripto works VERY slowly from the Google cache.
- the site loads very slowly from the free part of Anonymizer.com and they block access to file downloads unless I pay money
- connecting to the scripto fails even before the connection enters PPP mode (ie from the terminal window you can have Windows XP display after the connection is dialed)
- tracert used to work for everything.  Now it fails for everything. "Destination net unreachable." is reported when I hit the proxy & DNS server even when I used ntworthy.com.
- ping & tracert both are able to retrieve an IP address, which is valid in the browser but again fails when ping-ing or tracert-ing.
- access to the scripto works from school

PS.  You remembered my OS
 

Re: What's happened to the Scriptorium?

Reply #7 –
Francis, I'm not sure of the meaning of your post.

Just so you know, the ping times for the Scripto server are very good from several sources that I have tested. If you are using a proxy, perhaps it is causing your problem.