|
Syd, >Yes, I would agree that Windoze is the culprit. > >I solved my problem by replacing the Windows Gateway with a Linux >Gateway (SuSE 7.0). Much more reliable. This has never crashed since it >was installed. It was last booted over 6 months ago. My problem doesn't appear to me to be the Gateway. It seems to be my local desktop. The gateway machine continues to be able to browse etc even while my local desktop is timing out. >I think Windoze wait for the TCP/IP reply, somehow misses or looses it, >and goes into a wait state for that reply. Eventually it times out. That's what I think too, but the somehow missing or losing it seems to be on the desktop end, as far as I can tell. Did changing your gateway to Linux solve problems with local connections to a local 400? Or even telnet connections to a remote 400? Doug
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
