About telnet?

[leereg_5]

I have two box, and I try to telnet to box1, it does not response. When I telnet to box2 from box1, it's ok. When I telnet to box1 from box2, it hangs, but I can see the process when I issued: $ps -ef|grep telnet.And when I kill the process ID, the hunging window prompt out. I have check the config files and the daemon is running too.
What is the secret?

[Rainer von Bongartz]

take a look at your syslog; telnetd should log messages there

Regards
Rainer

[leereg_5]

Hi Rainer:

I checked syslog but find no record on telnetd!



Regards!

Rick

[Robin Wakefield]

Hi,

Switch on logging (inetd -l), then try connecting and see if syslog is written to.

Also, do a "netstat -an" and see if the following line is displayed:

tcp 0 0 *.23 *.* LISTEN

Rgds, Robin.

[leereg_5]

Hi Robin:

I checked as you said and there is no such line. What's wrong with it and How to resolv it?



Regards!

[Paula J Frazer-Campbell]

Hi

Check /etc/inetd.conf for the telnet line :-

telnet stream tcp nowait root /usr/lbin/telnetd telnetd

then restart with inetd -c


HTH

Paula

[harry d brown jr]

Another possibility is that your network routing information on box1 is not similar to box2. Check your /etc/rc.config.d/netconf files. If both boxes are on the same subnet, then they should have the same gateway info, and the same subnet masks.

[Jay Newman]

Some very quick diagnostics that should narrow things down:
- From each box, ping the other. If one gets a lot of "no route to host", you know there is likely an issue with routing or your default gateway. Use netstat -rn to take a look at your routing tables.
- If pings work in both directions between each other, find another box to telnet to. This will isolate if you have a problem with the telnet client or server.
- Also try using both the host names and their I/P addresses in your commands, in case you have a DNS/BIND issue.

[Michael Tully]

Hi,

As the others have suggested try and make sure
that you have the 'inetd' daemon running and
that your routing tables are correct. One
further thing you can do is run the
'/usr/contrib/bin/traceroute' command to see
if system B can find system A.

Michael

[Printaporn_1]

does it work by telnet with IP ?
if yes , may be just hostname resolution problem.

[Magdi KAMAL]

Hi Leereq,

It's a problem of Broadcasting.

Edit your /etc/rc.config.d/netconf and verify the value of entry :
BROADCAST_ADDRESS[x]=
if it's correct.

Attention :
Ignite-UX software got a bug will clonning other systems. When you interrupt the recovery process from Ignite tape and give new values, IP values are not changes even of you give new ones ( I got this problem before due to this bug !!! ).

Magdi