Right – you should pretty much be
able to hit any open port with the telnet command which should be confused with
the “telnetd” daemon that uses port 23.
It’s a good basic test when you want
to see if connectivity to a given port is an issue. It has nothing to do with
being able to actually access the service listening on that port unless that
service is poorly written.
From:
veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Patrick
Sent: Tuesday, February 05, 2008
2:17 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] login
through veritas
You can telnet to a client (or
media or master server) by:
telnet <client name>
[bpcd | vnetd ]
This will get you a prompt and
is a good test of connectivity and configuration, however as soon as you hit
the carriage return you should get a disconnect message and be returned to the
original prompt.
Regards,
Patrick Whelan
Whelan Consulting
Limited
VERITAS Certified
NetBackup Support Engineer for UNIX.
VERITAS Certified
NetBackup Support Engineer for Microsoft Windows.
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Ed Wilts
Sent: 05 February 2008 18:42
To: Dirk_Lutz AT rush DOT edu
Cc: Karl_Oder AT rush DOT edu;
veritas-bu AT mailman.eng.auburn DOT edu; Victor_Irlandez AT rush DOT edu
Subject: Re: [Veritas-bu] login
through veritas
On Feb 5, 2008 11:27 AM, <Dirk_Lutz AT rush DOT edu> wrote:
> Does anyone know if there's a way to get a shell prompt through Veritas
Netbackup using telnet?
> Also, what username does netbackup use and why
isn't it in /etc/passwd?
> It actually is in /etc/passwd. It uses the username provided by the
inetd or xinetd service - typically this is root.
> (Does Netbackup use a shell when it backs up clients and can this shell be
accessed manually using telnet to log into a client.)
On Unix (and Windows) systems, it does not use a shell - it connects to the
bpcd port. (usually 13782) In the system administration guides, there is
a great explanation with diagrams of what the communication paths are - i.e.
who talks to who.
On VMS clients, it does use a shell - the inetd-equivalent service spawns a
shell that simply runs the bpcd image. You can't execute DCL commands
through this ports. The service definition determines what username to
use - on my VMS systems, it's not the SYSTEM account.
You can telnet to the port on the client, but you won't get a shell.
telnet never has, and never will, equate to running a shell.
.../Ed
--
Ed Wilts, Mounds View, MN, USA
mailto:ewilts AT ewilts DOT org
