Telnet restriction?

[E. Wong]

I am having trouble with users opening a Telnet session to my HPUX box. They get Connection failed. What is intriguing, I have other users able to telnet without any problem. Is there any telnet quota exceeded? I already checked Kernel variable npty = 60. Any thoughts?

[Uday_S_Ankolekar]

Hi,

Check /var/adm/inetd.sec file for any subnet being blocked.

-Goodluck,
-USA..

[Sanjay_6]

Hi Wong,

Check this link and update your kernel parameter if you feel that is the problem,

http://us-support.external.hp.com/cki/bin/doc.pl/sid=461069dd19391c1585/screen=ckiDisplayDocument?docId=200000046112381

Hope this helps.

Regds

[Craig Rants]

Check the syslog for connection messages from telnet.

grep -i Telnet /var/adm/syslog/syslog.log

If telnet is not being logged go to /etc/rc.config.d/netdaemons and modify INETD_ARGS line with the "-l" option.

Restart your service and have them try there telnet again.

Good Luck,
C

[E. Wong]

no "deny" in inetd.sec
still can't ping certain users workstations.

[Uday_S_Ankolekar]

Hi,
It's Network issue. Try traceroute command to see where all the packets are moving.
Also check the default route for these workstations. They could be pointing to some other object.

Goodluck,
-USA..

[Sanjay_6]

Hi,

Can you ping you hp box from your user workstations. IF you know the ip for your user workstations you can try to do a "traceroute"

/usr/contrib/bin/traceroute ip_address

If you have exceed or some telnet packge you can use its traceroute to trace the route from the workstation to the hp-box. This looks like a gateway problem.

Hope this helps.

Regds

[E. Wong]

Sanjay,

I can do a ping from workstation to HPUX. But from HPUX to workstation, traceroute doesn't seem to work. Any further thoughts?

[Craig Rants]

What about your allows? If something is not allowed, it is implicitly denied.

Could you put your inetd.sec file in a post.

Also what are the ip's of the workstations you are refering to. That info would keep everyone from guessing on answers for you.

C

[Sanjay_6]

Hi,

Seems like a route problem to me. What is the OS on your workstation. Both Hp and win NT has route command to manually add a route. IS your Hp-ux server on a different subnet than your workstation. If their a route in between them. You can use the route command to add a route manually from your workstation. If you are using a NT Workstation, go to ms-prompt and type "route print". this will list all the routes available. Check whether the subnet to the hp server to available over there. you can configure a gateway from your nt workstation to the hp-unix server. Check the setting on another workstation from where you are able to login into hp.

We had a similar problem with another server sitting in between the hp-server and the node.

Hope this helps.

Regds

[E. Wong]

Here is the info on the inetd.sec

dtspc allow 127.0.0.1 hpux4
spc allow 127.0.0.1 hpux4
mserve allow 127.0.0.1 hpux4
hpux4 ip is 219.51.90.14
workstation in question is 219.51.90.134

Both ip's are in the 255.255.255.0 subnet

[harry d brown jr]

What is your default route on hpux4 ??

Do a netstat -rn, and it should show a line like this (but not exactly):

default 219.51.90.1 UG 0 lan0 0

and are you sure the netmask is 255.255.255.0?

Do a ifconfig lan0 and double check the netmask.




live free or die
harry

[Sanjay_6 · Accepted solution]

Hi,

what is the gateway for hpux4

Add the same gateway to the workstation you are connecting from.

Hope this helps.

Regds

[Craig Rants]

dtspc allow 127.0.0.1 hpux4
spc allow 127.0.0.1 hpux4
mserve allow 127.0.0.1 hpux4
hpux4 ip is 219.51.90.14
workstation in question is 219.51.90.134

Both ip's are in the 255.255.255.0 subnet

Based on the information above, telnet is allowed to all. I should have thrown in the caveat if the service is not listed then it is implicitly allowed.

Your subnet is flat so you don't even need a default gateway to talk between the workstation and hpux4, even though you do want one. A traceroute should only show 1 hop in this configuration. Could it be that your subnet mask is not set properly?

What type of workstation is it? W2K, HP, this will make a minimal difference, just curious.

C

[harry d brown jr]

Craig,

your subnet mask must be 255.255.255.0 for anyone to get in from 219.51.90.x, but I haven't seen anything to that fact yet. Also, I'm wondering if the clients that are trying to connect to the hpux4 are setup correctly?

live free or die
harry

[E. Wong]

Here are some results:

# traceroute 219.51.90.134
traceroute to 219.51.90.134, 30 hops max, 20 byte packets
1 219.51.90.134 1 ms * *

# netstat -rn
default 219.51.90.1 UG 3 24775 lan0 1500

# ifconfig lan0
lan0: flags=863
inet 219.51.90.14 netmask ffffff00 broadcast 219.51.90.255

Awaiting comments

[Sanjay_6]

Hi,

IS your default gateway 219.51.90.1 available.

Regds

[Craig Rants]

Harry,
I was making and assumption based on 255.255.255.0 comment. Just an assumption.

The * in your traceroute shows that the packet was not responded to. I would focus on that workstation.

Your ifconfig looks good, same with your default route.

C

[E. Wong]

Sanjay,

Yes, default gateway is available. I can telnet it both from workstation and HPUX.

[Sanjay_6]

Hi,

If on win NT workstation, go to dos prompt, add a route

route add 0.0.0.0 mask 0.0.0.0 219.51.90.1 metric 1 IF 219.51.90.134

then try a telnet.

Hope this helps.

Regds

[E. Wong]

halfway there. Once I add the "route add ...." command, I get to telnet from workstation to HPUX. But once I reboot workstation, the route doesn't show anymore. I have to add it once again.
Is there a way to add the route to the tables on a permanent basis in the workstation NT?

[Uday_S_Ankolekar]

Hi,

while adding route use -p option that will save the routing onfo NT.

Goodluck,
-USA..

[E. Wong]

Alright, that takes care of my NT. I have a few Win98. -p doesn't work there. Any workarounds?

[Sanjay_6]

Hi,

I would suggest you to set the gateway ip as 219.51.90.1 on all nodes in the TCP/IP properties for the lan card.

For us, we have DNS configured and the nodes pick up all the info from the DNS, we do not have any ip add setting. The workstation ip is assigned by DHCP server and the name and ip resolution being done by DNS.

Hope this helps.

Regds

[E. Wong]

Thanks everyone for your inputs. They're really helpful. Thanks Sanjay for narrowing down the problem.

Keep the forum going!