Physicians; heal selves.

Post #17,451 by Ashton 11/9/01 3:35:08 AM Reply	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 by boxley 11/9/01 9:42:53 AM Reply	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 by Ashton 11/9/01 4:19:51 PM Reply	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 by boxley 11/9/01 4:54:06 PM Reply	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 by Ashton 11/9/01 5:07:37 PM Reply	Ah.. I see. Thanx

Welcome to IWETHEY!