If telnet won't connect, try ssh. It's a better (or at least safer) protocol to 
connect with anyway.

On most modern systems (mainframe and intel), you probably won't see telnet or telnetd 
running in a ps command. It's controlled through inetd or xinetd.

If you're running inetd (Look in that ps command), look in /etc/inetd.conf to see if 
telnet is allowed. The line starting with telnet  could be commented out (i.e. It 
would begin with "#telnet").

If you're running xinetd (The better choice), look in the directory /etc/xinetd.d for 
a telnet file. In it there may be a line with "disable = yes". Change this to "disable 
= no" to enable telnet through xinetd.

In any case, you'll be more secure in the long run if you look into starting up the 
sshd deamon and using an ssh client to access the system instead of telnet. ssh access 
is encrypted, where telnet sends you text (including userid and password) as open 
ascii text.

----
Robert P. Nix                            internet: [EMAIL PROTECTED]
Mayo Clinic                                  phone: 507-284-0844
200 1st St. SW                             page: 507-255-3450
Rochester, MN 55905
----
"In theory, theory and practice are the same,
 but in practice, theory and practice are different."


> -----Original Message-----
> From: Gregg C Levine [SMTP:[EMAIL PROTECTED]]
> Sent: Tuesday, October 08, 2002 9:31 AM
> To:   [EMAIL PROTECTED]
> Subject:      Re: Suse 7.0 (LPAR)  can't telnet after installation
>
> Hello from Gregg C Levine
> A good question. Can you login to the system using other methods? Check
> the settings in the configuration files listed inside the etc directory.
> Typically some distributions are installed, or install themselves, with
> that one turned off. Also go over the list of files you installed. If
> this one normally comes with a telnet server, you might forgotten to
> install it, since it was considered an optional package. Granted, this
> might be just my opinions, mind, but I could be right.
> -------------------
> Gregg C Levine [EMAIL PROTECTED]
> ------------------------------------------------------------
> "The Force will be with you...Always." Obi-Wan Kenobi
> "Use the Force, Luke."  Obi-Wan Kenobi
> (This company dedicates this E-Mail to General Obi-Wan Kenobi )
> (This company dedicates this E-Mail to Master Yoda )
>
>
>
> > -----Original Message-----
> > From: Linux on 390 Port [mailto:[EMAIL PROTECTED]] On Behalf Of
> > Harmen Mak
> > Sent: Tuesday, October 08, 2002 10:20 AM
> > To: [EMAIL PROTECTED]
> > Subject: [LINUX-390] Suse 7.0 (LPAR) can't telnet after installation
> >
> > Hello,
> >
> > I am installing suse 7.0 on a Multiprise 3000, after several
> adjustments the
> > installation ends with a prompt on the console. The problem is that I
> can't
> > telnet to my Linux environment. When I ping from the console to my
> desktop I
> > can find the mac address, of the Ethernet nw-card in the MP3000, in
> the arp
> > list of my desktop, that's al I get. I can't get a response of the
> Linux
> > environment, when I ping telnet or whatever I try, nothing.
> >
> > It's an installation in an LPAR and we use the Intel Pro PCI Adapter
> for
> > network communication.
> >
> > Anyone who knows this problem, have I missed something?
> > I hope you can help me.
> >
> > Regards,
> > Harmen

Reply via email to