Thanks to all who provided ideas - looks like MTU is the big winner. Some quick tests this morning revealed that when I bring up the Linux guest with an MTU of exactly 576 my missing telnet output shows up where it should. Both higher and lower values fail, but since I pretty much ensured a mismatch by not changing the value on the VM side of the link, I'm not worrying too much about that at the moment. Works fine from all 3 telnet clients which had previously failed.
On another, unrelated but equally newbie topic - while TRACEing around the Linux guest, I saw what seemed an alarming number of PROG 4's (not the expected page and segment translation exceptions, which I also see). In systems with which I'm more familiar, this number of protection exceptions (48 during a "who") would have meant a serious coding problem. But I see no indication of any error. Should I assume this is just part of normal Linux operation? If it's normal, would anyone care to explain (or point me to a discussion somewhere which explains) how it's being used? It's obviously not critical, and I only did a quick search myself, but I'd like to understand. Thanks again, Steve On Mon, 25 Nov 2002, John Summerfield wrote: > On Mon, 25 Nov 2002 05:04, you wrote: > > That's assuming the MTU for the VM/TCPIP stack is >= 1492, which may not be > > the case (but most likely is the case). Rather than hit and miss, checking > > what it is and adjusting from there is important. > > Isn't the relationship supposed to me > MTU <= MRU > where MTU and MRU are values at the opposite ends of the link? > > I can send as much as I like so long as it's no more than you expect to > receive. > > > -- > Cheers > John Summerfield > > > Microsoft's most solid OS: http://www.geocities.com/rcwoolley/ > Join the "Linux Support by Small Businesses" list at > http://mail.computerdatasafe.com.au/mailman/listinfo/lssb > -- Steve Marak -- [EMAIL PROTECTED]
