topic Re: telnet issue in Operating System - Tru64 Unix

telnet issue

Rupert_1 — Wed, 07 Nov 2007 05:46:51 GMT

Tru64 Unix V5.1B, latest patch-kit, standalone server.

Nodename as registered in kernel is mmp3.sems.com

Have two interfaces configured as follows:

Tu0: 128.6.5.10 netmask : 255.255.0.0 hostname: mmp3.sems.com
Tu3: 128.6.5.33 netmask : 255.255.0.0 hostname : mmp33.sems.com

When configured as above, we can ping to the IP addresses.
When telnet to the hostname, it gives an error – unable to open port on interface or similar.

What is wrong with the configuration ?

Interface ip hostname

Tu0 128.6.5.10 mmp3.sems.com
Tu1 100.100.100.10 mhdb2
Tu2 100.100.100.11 mhdb3
Tu3 128.6.5.11 mmp33.sems.com

Re: telnet issue

Danny Petterson - DK — Wed, 07 Nov 2007 05:49:20 GMT

Is telent configured in /etc/inetd.conf?

Yours
Danny

Re: telnet issue

Rupert_1 — Wed, 07 Nov 2007 05:57:18 GMT

we used sysman to configure, then stop/start network services, did not reboot server.

Re: telnet issue

Danny Petterson - DK — Wed, 07 Nov 2007 07:26:23 GMT

Can you telnet from the host itself to itself (telnet localhost)?

If you grep for telnet in /etc/inetd.conf, what does the line enableing telnetd look like?

Yours
Danny

Re: telnet issue

Steven Schweda — Wed, 07 Nov 2007 08:39:04 GMT

> [...] latest patch-kit [...]

How do I know what the latest one is? More
important, how do I know that _you_ know what
the latest one is?

> When telnet to the hostname

From where? To which address does the host
name resolve wherever you're Telnetting from?

> [...] it gives an error [...] or similar.

Who is "it"? What's the actual error
message? A transcript showing what you did
and what happened when you did it might be
much more helpful than a vague description.

> [...]
> Tu3: 128.6.5.33
> [...]
> Tu3 128.6.5.11 mmp33.sems.com

Eh?

Re: telnet issue

Rob Leadbeater — Fri, 09 Nov 2007 10:08:34 GMT

Hi,

Having two network interfaces on the same subnet is likely to cause you problems...

Check whether telnetd is listening, by looking at the output of "netstat -a"

You might also want to review your routing configuration... "netstat -rn"

Cheers,

Rob