Steve,

This sounds like an MTU mis-match between the Linux/390 guest and the VM
TCP/IP stack.  Don't default the MTU size in the VM TCP/IP definitions for
your guest.  Define it explicitly.  Make it match what the rest of your
network is expecting.  Then, make sure your Linux/390 network definitions
include that value as well.  You can check it with an "ifconfig" command.

Mark Post

-----Original Message-----
From: Steve Marak [mailto:[EMAIL PROTECTED]]
Sent: Friday, November 22, 2002 6:12 PM
To: [EMAIL PROTECTED]
Subject: Missing telnet output (another stupid newbie question)


I'm sure the answer is obvious and that 98% of this list will know it, so
I'll just ask that you be gentle to yet another old VMer who is now
beginning to play with Linux. (I did search the archives, as well as a
bunch of other places, before posting. We found what looked like two other
people with the problem, but no solutions, and they haven't responded to
us.)

We boot the SuSE instsys from the virtual card reader in a VM guest. It
appears to load fine, we are prompted for and provide basic networking
information, and again all appears well. (More version and config details
at the bottom.)

When we telnet to the host from another guest under the same VM (i.e.,
running CMS), all is fine, except that YaST doesn't appear to run well on
3215/327x terminals. We can telnet (awkwardly) or ftp from the Linux guest
out to other hosts.

But when we telnet into the Linux guest from elsewhere in the network (not
on the same subnet as either the Linux guest or the VM system due to
network configuration) things get odd. We are prompted for and provide
userid and password. Having hit return after entering the password, we
then show as logged on (according to who or ps from the console). We can
enter commands and, based on various trials, they are executed just fine.
But we never see another character of output on the telnet session - no
shell prompts, no command responses, nothing.

This happens no matter which of several telnet clients we use (including
putty), which of several terminal types we select (ANSI, VT100, etc.) or
whether the userid is root or another that we add on the fly (with
non-zero uid and gid).

One of the guys re-pulled the ipl decks just to be sure and got the same
results.

We've run this by a few people without any luck. Any help would be greatly
appreciated ... we're just not good enough to run YaST without responses.

Thanks,

Steve

Config stuff: SuSE 7 ipl deck from the ISO CD images we downloaded (cat
/proc/version -> Linux version 2.2.16 ([EMAIL PROTECTED]) (gcc version
2.95.2 19991024 (release)) #1 SMP Fri Nov 3 09:38:59 GMT 2000). Booting
under VM/ESA 2.4, using virtual CTCs for networking via the VM ip stack.
Network connectivity appears good by every test we've tried. MP3000 P30
hardware.


-- Steve Marak
-- [EMAIL PROTECTED]

Reply via email to