- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- VMS-UCX rsh port no
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-12-2007 03:59 AM
06-12-2007 03:59 AM
VMS-UCX rsh port no
What is the TCP/IP port used by RSH to execute a com file on a remote VMS server?
As shown below, when I ran a test from VMS to Unix, VMS shows up as 1023.
dbs2:sanghvi> netstat | grep gnfa
tcp 2 0 dbs2.wilm.ge.com.exec gnfa.wilm.ge.com.1023 ESTABLD
Is this correct?
Thanks.
Arun Sanghvi
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-12-2007 04:09 AM
06-12-2007 04:09 AM
Re: VMS-UCX rsh port no
ALP $ tcpip show service rsh
Service Port Proto Process Address State
RSH 514 TCP TCPIP$RSH 0.0.0.0 Enabled
I'd say the VMS uses the same port for RSH as everyone else does, 514.
Or, for "rsh command":
ALP $ tcpip show service rexec
Service Port Proto Process Address State
REXEC 512 TCP TCPIP$REXEC 0.0.0.0 Enabled
Or, to see them all:
tcpip show service
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-12-2007 04:20 AM
06-12-2007 04:20 AM
Re: VMS-UCX rsh port no
What particular situation might you be addressing here?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-12-2007 04:29 AM
06-12-2007 04:29 AM
Re: VMS-UCX rsh port no
Thanks for your prompt response.
I need to provide the RSH port no to network team for firewall configuration.
It seems that firewall needs to opnen up 512, 513 and 514.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-12-2007 04:40 AM
06-12-2007 04:40 AM
Re: VMS-UCX rsh port no
already _know_ which port(s) to open for RSH?
Time for a new network team?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-12-2007 04:44 AM
06-12-2007 04:44 AM
Re: VMS-UCX rsh port no
It is both interesting and quite surprising that a network team is unfamiliar with rsh. This is one of the standard Berkeley r-commands, after all.
The rsh daemon listens on 514/TCP.
512/TCP is the biff daemon. biff isn't usually found on OpenVMS.
513/TCP is the rexec daemon.
rsh is a comparatively insecure and open protocol, and not something generally seen nor selected for passage through firewalls. ssh and other (encrypted) approaches are often a better and more secure choice.
rsh attacks are quite common -- well, so are ssh attacks, but at least ssh doesn't leak its information in cleartext.