On Sunday 24 November 2002 11:41 pm, Steve Marak wrote: > So do you, collectively or individually, have any particular > recommendation for a fix or experiment to run tomorrow when I get to work > (short of applying the TCPIP maint)? Drop the MTU size to something below > 1492 and see what happens?
Just out of curiosity, can you duplicate this problem on a client that is not running Microsoft's Windows telnet? The default telnet client in Windows NT 4.0 and its contemporaries was notorious for dropping characters whenever the host sent a lot of data, such as a command output that filled the screen. I don't know if they fixed this in Win2K or not. I don't think it was a TCP/IP stack problem, but rather something to do with how they took received data and posted it to GUI draw updates. There is some strange asynchronousness to the GUI draw process in early Windows (and OS/2) versions that can cause anomalous behaviors like this. [For the record, I personally witnessed the bug and can vouch for its existence, but my theory on the *cause* of the bug is only speculation, since Microsoft's code base is closed-source.] It's a long shot, but it's very easy to test this so as to eliminate it as a possible source of the error. Just login to your machine from a non-Windows client. If you can duplicate the problem, then it's not the Windows telnet bug. Scott -- ----------------------------------------------------------------------------- Scott D. Courtney, Senior Engineer Sine Nomine Associates [EMAIL PROTECTED] http://www.sinenomine.net/
