Telnet to 3601 port does not work

[Carles Viaplana]

Hello,

SAP uses port 3601 for internal communications and I get a connection refused message. For this reason I'm checking 3601 port to my system trying a telnet, but I also get connection refused message.

Should I open/restart any service in HP-UX in order to allow connections to port 2601?

Note system is HP-UX 11.23 and I already added an entry to /etc/services for this port.

Thanks in advance for your help.
Regards,

Carles

[Peter Godron · Accepted solution]

Carles,
from another thread:
/etc/service - All services are listed and mapped to ports
/etc/inetd.conf - Services are enabled or disabled
/var/adm/inetd.sec - Access given to specific services and hence specific ports.

Have you got all thee files sorted and an application listening on the other side of the port ? Any firewall ?

Please also read:
http://forums1.itrc.hp.com/service/forums/helptips.do?#33 on how to reward any useful answers given to your questions.

[Marco A.]

If all those files are ok, check for firewall configurations, look at your other networkdevices, firewall, router, etc...

[Steven E. Protter]

Shalom,

Two major issues.

Firewalls
Nothing listening.

netstat -an | grep ":3061 "

SEP

[Mel Burslan]

connection refused messages on the telnet connections, usually caused by a mis-configured firewall. If you are working in a security conscious data center, your firewall admins most probably blocked every unused port. 3601 not being a standard port in environments not running SAP may be a victim to this. Talk to firewall admins.

If your SAP implementation is good,

netstat -an | grep 3601

should give you a line like this:

tcp 0 0 *.3601 *.* LISTEN

if not, you need to talk to your SAP BASIS admins as well, but connection refused usually does not come from the server generally.

Also, another good point to check is /var/adm/inetd.sec, to see if there is any blocking of access to this port.

Hope this helps

[Carles Viaplana]

Application wasn't listening due system was not into SAP ACL list.

Thanks anyway for your help.
Regards,

Carles

[Tor-Arne Nostdal]

Hi,
Just a couple of hints related to SAP...

You should use the SAP delivered program niping to verify the connection.
It might be that you need to add the rfc addons to your SAP kernel.

portnumber 36xx is pointing to the message server processes (xx=system number).
You could also check whether the message server process is running.
ps -ef | grep ms.sap

The message server process also require a correct entry in the services file...
sapms{system ID} 36{system number}/tcp

This is also important for the clients.

I've often seen that users do not have problems connecting the dialog server process (32xx) but fail to connect to message server because of this...

/2r