I noticed the same problem, basically the same routing table failures that
y'all are getting. I've put my 486/win95 client on PAUSE (via DESGUI, not
sure exactly how this 'pause' works, if its like a SIGSTOP in unix) and
I'll resume it when I get back from class later, that way its not pounding
the server with "me! me! me!" ;)
To tell y'all the truth, as many things as could go wrong with the
internet, its quite amazing that more don't. *knock on wood* cause about
the time I say that, 80% of MCI's T3's go AWOL ;)
Rick
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
iQBVAwUBM5Ly69wN5z5H8eS5AQE79gIAlZOVefcic0C7W9eA41/vgSZoDjAIuXhS
KWnm/wgkCv+iiCEw4x+H+FsXCDhYJCNRGaJod9esGe7HAr1eqxg53w==
=oZzn
-----END PGP SIGNATURE-----
-- Richard Hornsby, The Ohio State University. Public key availible at http://www.cis.ohio-state.edu/~hornsby/who/pgp-key.asc.txt