Post #17,370
11/8/01 3:12:09 PM
|
Yah...
This...
The page cannot be found
The page you are looking for might have been removed, had its name changed, or is temporarily unavailable.
Please try the following:
If you typed the page address in the Address bar, make sure that it is spelled correctly.
Open the z.iwethey.org home page, and then look for links to the information you want.
Click the Back button to try another link.
HTTP 404 - File not found
Internet Information Services
Technical Information (for support personnel)
More information:
Microsoft Support
[link|http://uptime.netcraft.com/up/graph/?mode_u=off&mode_w=on&site=z.iwethey.org|Someone's having fun with the 404 page] *grin*
Imric's Tips for Living- Paranoia Is a Survival Trait
- Pessimists are never disappointed - but sometimes, if they are very lucky, they can be pleasantly surprised...
- Even though everyone is out to get you, it doesn't matter unless you let them win.
|
Post #17,379
11/8/01 3:50:28 PM
|
I have no idea where that's coming from.
As you pointed out, z.iwethey.org is Zope (proxied through Apache, actually).
I haven't fiddled with the 404 page, though.
Regards,
-scott anderson
|
Post #17,381
11/8/01 4:00:32 PM
|
Then since it's not just me getting it ...
It seems there is someone upstream from you having problems. I checked what I could on the page and couldn't find anything that didn't point to either iwethey.org or microsoft.com. Wish I could be more helpful.
BTW: I get the 404 occasionally, but after a few reloads I get the page. Has all the symptoms of someone upstream from you having router issues.
We have to fight the terrorists as if there were no rules and preserve our open society as if there were no terrorists. -- [link|http://www.nytimes.com/2001/04/05/opinion/BIO-FRIEDMAN.html|Thomas Friedman]
|
Post #17,386
11/8/01 4:10:08 PM
|
I always ping z.iwethey.org for connect probs
tshirt front "born to die before I get old"
thshirt back "fscked another one didnja?"
|
Post #17,413
11/8/01 8:14:22 PM
|
IP stealing?
I've been having connection problems also to II, but the IP address stays correct. Could this be another box (running NT) at the co-lo accidentally trying to steal the IP address?
Wade.
"All around me are nothing but fakes
Come with me on the biggest fake of all!"
|
Post #17,457
11/9/01 5:45:50 AM
|
Unlikely
Far more likely is a horked round-robin DNS server at the colo.
Peter
Shill For Hire
[link|http://www.kuro5hin.org|There is no K5 Cabal]
|
Post #17,414
11/8/01 8:14:50 PM
|
IP stealing?
I've been having connection problems also to II, but the IP address stays correct. Could this be another box (running NT) at the co-lo accidentally trying to steal the IP address?
Wade.
"All around me are nothing but fakes
Come with me on the biggest fake of all!"
|
Post #17,444
11/8/01 11:59:46 PM
|
No, it's definately not just you
Just ran into the problem myself tonight. Took about 5-8 reloads to get the right page to show up.
Most unnerving.....
|
Post #17,450
11/9/01 3:23:21 AM
|
II was going weird this afternoon, too.
No idea if it's related or not though. Was thrown off it a few times around 3pm this afternoon (Aus Eastern Standard Daylight Savings Time) Or, like, about four and half hours ago from now. Still, was able to log back inn each time after waiting a few minutes.
On and on and on and on,
and on and on and on goes John.
|
Post #17,473
11/9/01 10:26:10 AM
|
Happened just this morning here
Here = Northwest suburbs of Chicago. got same message, too. But we're behind a corporate firewall that is definately IIS. Could that be the cause?
jb4
(Resistance is not futile...)
|
Post #17,451
11/9/01 3:35:08 AM
|
Physicians; heal selves.
How would one trap this page (as in: ID its actual server and go from there) ?
I know what a packet sniffer does - youse guys know how to use one to some effect. Right? (I mean of course.. if this &*$%* continues to get worse - where it appears to be heading..)
Maybe the poor dear has his IIS installed just like Billy says: insert the CD and We'll Take Care of Everything; don' need all that geek BS about knowin stuff..
:-)
|
Post #17,465
11/9/01 9:42:53 AM
|
wouldnt help here is a clue
last night had trouble connecting, so fired up a dos prompt and did
ping -t z.iwethey.org
found a minute or two of time outs then a few very large ttl (time to live) then a solid connection, left ping running and went back to browsing, timed out again then cacked again. Peter is prolly right horked round robin router.
thanx,
bill
tshirt front "born to die before I get old"
thshirt back "fscked another one didnja?"
|
Post #17,561
11/9/01 4:19:51 PM
|
Re: wouldnt help here is a clue
Would that be something like ~ a typo, two ports w/ same address (or a mask with wrong range) so that randomly a packet queries this (wrong) server -- and we wouldn't see the traffic from outside - to examine?
(Just wondering what sort of BS youse guys have to put up with normal homo-sap errors.) I inferred somewhere that - changing a router address in an operating network needs careful restraint and coordination - er 'propagating' and such..
Izzat (maybe) it? like newbies fakin-it, not knowin WTF happened: "must be a protocol error.." (The MDs' version when they don't know shit: "you have non-specific proctitis" ;-)
Gosh.. IP-addressing must be the same as when we first heard 'you have to take Algebra next year!' (and the old smug hands say.. 'yeah.. that's a Killer').
A.
|
Post #17,571
11/9/01 4:54:06 PM
|
router round robin
1 ip address several ports listening each taking turns.
1 packet goes to port 1
1 to port 2
1 to port 3 etc.
then back to port1
if you get a new packet the port that gets the first packet will handle the rest of the conversation.
Now say the cable on port 3 is cacked. The router will still send packets to that port as part of the round robin. That would generate odd timeouts of a ip address like I saw.
thanx,
bill
tshirt front "born to die before I get old"
thshirt back "fscked another one didnja?"
|
Post #17,578
11/9/01 5:07:37 PM
|
Ah.. I see. Thanx
|
