HP Unix 9000 Telnet

[Rich Yang]

We've an old HP9000 w/ A.09.04E OS. We migrated IP on our Unix box and after that we've two problems.

1). We can't telnet from other workstations to Unix server but we are able to ping the unix server from other workstations. From Unix box, we can ping to other servers, routers, and workstations.

2). We use Tiny Term, terminal emulation program, for our clients to run application on Unix server. The Tiny Term program uses IP to talk to the Unix box. The program failed.
The error messaqe tells me this is the wrong IP address to talk to the Unix.

The problem looks like there is a configuration file in Unix specified only reconize certain IPs to communicate to the server.

Any thoughts are welcome.

Thank you,

Rich Yang

[Pete Randall]

Hi Rich,

What do you mean when you say "We migrated IP on our Unix box"?

Pete

[Uday_S_Ankolekar]

Check /var/adm/inetd.sec file and see if the ip address is mentioned in this file
Also check you this IP configured in DNS

-USA..

[Rich Yang]

Hi Pete,

Thank you for your help. The "migration of IP" means we changed the IP address.

I checked Unix box. There is no /var/atm directory on old Unix server.

Thank you,

Rich

[Paula J Frazer-Campbell]

Rich

Do you have a router in your lan.

Paula

[Kelli Ward]

Hi Rich,
If by migrating Ip you mean changed the IP address, you need to check a couple of files to make sure they aren't running the old ip.

Check:
/etc/hosts
/etc/netlinkrc
/usr/adm/inetd.sec

Ensure there are no instances of the old ip in them, change them if there are.

Good luck,
Kel

[Mark Greene_1]

How did you change the IP address? If you did not use /sbin/set_parms, you may have not gotten all of the files updated. Also, do you get the correct host name if you nslookup on the new IP addresss?

What version of Tiny Term do you use? We have 3.2 (rather old) and can connect via hostname no problem. This is nice in that we don't have to update desktops if the IP of the box changes. If it turns our that the hostname is specified in the TinyTerm setup, then you most likely have a DNS issue.

HTH
mark

[Steven E. Protter]

check here.

/etc/rc.config.d/netconf

A mistake perhaps a typo?

SAM sometimes messes this up if you use that to make the change.

I like the router or inetd.sec idea better.

[Kelli Ward]

Hi all,
Remember the OS Rich is using is HP-UX 9.04.
The files you are mentioning do not exist on this OS.

The three main networking files in a pre HP-UX 10x environment are:

/etc/hosts (same on all HP-UX OS's)
/etc/netlinkrc (replaced by /etc/rc.config.d/netconf in 10x +)
/usr/adm/inetd.sec (replaced by /var/adm/inetd.sec)

set_parms for 9x won't necessarily get all ifconfig lan0 notes where the ipaddress is listed in netlinkrc.

Rich - In netlinkrc, I recommend replacing the old ip address if it exists with `hostname` where the ` is the single quote next to the 1 key. (This will resolve by hostname and never bother with the ip address again. Cleared up lots of little issues for me.

Also, if you have made a hostname change, verify the hostname in /etc/hosts matches the SYSTEM_NAME= in /etc/src.sh

Good luck,
Kel

[Balasiu Dan]

Hi Rich!

do you telnet by hostname or
IP adress?

regards

dan

[Sridhar Bhaskarla]

Hi Rich,

Logon to the unix prompt and try to telnet to the localhost from the command prompt. If it is successful, then telnet to the IP address. If it is successful, then do it for the hostname.

If all of them are successful, then please let us know.

-Sri

[Rich Yang]

Hello all,

I do appreciate all of your help. I just have time to sit down and answer some questions.

1). We do have routers. I ran tracert IP, and tracert unix_server_name and found out the packet go to Unix box directly.

2). We do have internal DNS and Unix box does have an entry on DNS server.

3). I did use SAM to modify the IP settings on the NIC card and also use SAM to modify /etc/hosts.

4). I telnet IP and telnet unix_server_name and both didn't work.

5). The Tiny Term version is 3.3.

6). I'll do some suggestions from you and will let you know.

Thank you much,

Rich

[Mark Greene_1]

Check your /etc/inetd.conf and see if you have an entry for telnet, and if it is commented out or not. It ought to look something like this:

telnet stream tcp nowait root /etc/tcpd telnetd -b /etc/issues


Also, what does 'whereis telnetd return, and can you do "nohup telnetd &" to get a process to run in the background and stay up?

HTH
mark

[Rich Yang]

Hello all,

Happy New Year to all of you. I do appreciate all your help.

The problem on this issue was on the inetd program did not come up when reboot the server.

Whenever I reboot the server, all programs run fine. But I had no idea why it didn't come up now. After I run inetd manually, the network connection works right away.

Thank you again,

Rich Yang