HP Data Protector port 5555 issue

 
Thread Tools Search this Thread
Operating Systems Linux Red Hat HP Data Protector port 5555 issue
# 1  
Old 05-12-2011
HP Data Protector port 5555 issue

Dear All,

I have my HP Data Protector installed on the backup server.
I want to connect this backup server with the client server through
telnet port 5555 like below

telnet < ipaddress of client> 5555

But when I try like this , it says ...Connection refused ...unable to connect to remote host.

I tried to open the port 5555 in the client machine...which I could not.

Kindly help me in opening the port in client machine.

Rgds
Rj
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. IP Networking

Port forwarding issue

hi guys i have a simple question ! i have two ips . a valid and internal(172.16.11.2) i want to use port forwarding to forward any request to valid IP port 8001 to internal ip port 80 . i use this rule : sysctl -w net.ipv4.ip_forward=1 iptables -t nat -A PREROUTING -p tcp... (1 Reply)
Discussion started by: mhs
1 Replies

2. IP Networking

port state issue

Hello, I have following issue: traceroute connection works to given address(ip + port) but telnet(and other network tools) do not. How it is possible? telnet 10.150.184.225 443 Connection refused tracert -T -p 443 10.150.184.225 traceroute to 10.150.184.225 (10.150.184.225), 30 hops... (3 Replies)
Discussion started by: kuba7
3 Replies

3. HP-UX

FC port issue

I'm facing some strange HP-UX behavior. I have a small SAN with one HP server, two Cisco SAN switches and one HP tape library connected. When I issues port reset, syslog shows the following: Oct 15 07:34:51 terumos-bckp-srv2 vmunix: Target path (class=tgtpath, instance=12) has gone online. ... (2 Replies)
Discussion started by: Sapfeer
2 Replies

4. Linux

Open port for Data Protector

Hi guys. Opening port 5555 for Data Protector on Linux box but can't telnet to it. Modified /etc/services to have: omni 5555/tcp # DATA-PROTECTOR But when I telnet into it: telnet <ip address> 5555 Doesn't connect Need help figuring out what I need to do to open this port. ... (0 Replies)
Discussion started by: jamie_collins
0 Replies

5. Programming

Locking issue with serial port

Hi, In my application,I need to monitor the devices connected through serial port in solaris sparc 9 OS.I used c and java code for it and I am able to do the same but the problem comes when I restart the system and the open my application and try to monitor it.but I m unable to monitor the... (2 Replies)
Discussion started by: smartgupta
2 Replies

6. Solaris

Serial port issue

Hi, I am working with Sun Solaris 9 Sparc,Sun-Blade-100.In my application,I need to monitor the UPS using Serial port. When I am using JRE 1.4 in my application,I am able to monitor it but when I am upgrading the JRE version from 1.4 to JRE1.6. I am not able to monitor the UPS.It is showing the... (1 Reply)
Discussion started by: smartgupta
1 Replies

7. HP-UX

anyone ever play with omniback(data protector) command "omnir"?

playing around with a command-line restore from omniback...anyone ever play with omnir? I have the following test backup: $ omnidb -session 2008/02/01-6 Object Name Object Type Object Status... (1 Reply)
Discussion started by: mr_manny
1 Replies

8. HP-UX

PXE boot port issue

Hi,all: I want to boot an IA unix box from network, I am sure I set the DHCP and boot server, but it still failed ! It says : Client MAC Address: 00 18 FE 28 91 82 .....- PXE-E16: Valid PXE offer not received. Load of Core LAN Gb A failed: Not Found I use the nettl command to trace the UDP... (0 Replies)
Discussion started by: bluepluto
0 Replies

9. HP-UX

Data protector GUI gives Blank screen

Hi, Haveing a little trouble with data protector (5.5) on HP-UX (11.11, 11.23) under Xwindows Chameleon UNIX 97 (7.0 - its a old version) I am trying to get the GUI for DP up and running on a HP-UX cell manager and I have the following problem. The GUI starts up with no errors that I can... (2 Replies)
Discussion started by: Andrek
2 Replies

10. UNIX for Advanced & Expert Users

Omniback/Data Protector cell_info file

People, Can any one tell me the meaning of the "-main" option in the Omniback cell_info file. (We have Data Protector 5.5) ?? (4 Replies)
Discussion started by: Andrek
4 Replies
Login or Register to Ask a Question
ipsec_policy(1M)														  ipsec_policy(1M)

NAME
ipsec_policy - HP-UX IPSec policy tester SYNOPSIS
src_ip_addr] dst_ip_addr] src_port] dst_port] DESCRIPTION
is a utility program that allows the HP-UX IPSec Administrator to query the active policy database to determine which host IPsec Policy will be used for an IP packet based on a packet descriptor, or 5-tuple, and the direction. The packet descriptor consists of a source IP address, source port number, destination IP address, destination port number, and network protocol. If the host policy uses dynamic key Security Associations, also displays the authentication record and IKE policy selected. If the authentication record contains two values for the IKE (KMP) version, uses the first value and selects the IKE policy according to this value. If the host policy uses a tunnel pol- icy, also displays the tunnel policy used. requires the optional HP-UX IPSec software. You must have superuser capabilities to run the utility. Command-Line Arguments recognizes the following command-line options and arguments: Specifies the source IP address (src_ip_addr) of the packet. If the direction is out, this is the local IP address. If the direction is in, this is the remote IP address. Acceptable values: An IPv4 address in dotted-decimal notation or an IPv6 address in colon-hexadecimal notation. Default: If you omit the source address and destination address uses the wildcard IPv4 address If you omit the source address but specify the destination address, uses the wildcard IPv4 address or wildcard IPv6 address according to the type of IP address you specify for the destination address. Specifies the source port number (src_port) of the packet. If the direction is out, this is the local port number. If the direction is in, this is the remote port number. Range: An unsigned integer in the range 1 - 65535. Default: Any port number(0). If you are making a query for an outbound client-server application where the source port number can be any user-space port, specify a "dummy" user-space port number for the source port, such as 65535. Specifies the destination IP address (dst_ip_addr) of the packet. If the direction is out, this is the remote IP address. If the direction is in, this is the local IP address. Acceptable values: An IPv4 address in dotted-decimal notation or an IPv6 address in colon-hexadecimal notation. Default: If you omit the source address and destination address uses the wildcard IPv4 address If you omit the destination address but specify the source address, uses the wildcard IPv4 address or wildcard IPv6 address according to the type of IP address you specify for the source address. Specifies the destination port number (dst_port) of the packet. If the direction is out, this is the remote port number. If the direction is in, this is the local port number. Range: An unsigned integer in the range 1 - 65535. Default: If omitted, any port number is assumed. If you are making a query for an inbound client-server application where the client port number can be any user-space port, specify a "dummy" user-space port number for the destination (server) port such as 65535. Specifies the network_protocol of the packet. Acceptable values: (Mobile IPv6 Mobility Header), or Default: Any network protocol(0). Specifies the direction for the packet specification. Acceptable values: or Default: RETURN VALUE
Upon successful completion, returns 0; otherwise it returns 1. ERRORS
fails if any of the following conditions is encountered: o Command used incorrectly - Usage message is returned. o HP-UX IPSec subsystem is not running - returns the following message: EXAMPLES
IPv4 Example On system A you want to determine which host IPsec policy will be used for outbound telnet traffic to system B or when local users telnet to system B. Since the telnet clients on system A will use any unused user-space TCP port and the telnet daemons on system B will use TCP port 23, you could use the following command: On system A you want to determine which host IPsec policy will be used for inbound telnet traffic from system B or when users on system B telnet to the local system. Since the local telnet daemons will use TCP port 23 and clients on system B will use any unused user-space TCP port, you could use the following command: IPv6 example On system A you want to determine which host IPsec policy will be used for outbound telnet traffic to system B or when local users telnet to system B. Since the telnet clients on system A will use any unused user-space TCP port and the telnet daemons on system B will use TCP port 23, you could use the following command: On system A you want to determine which host IPsec policy will be used for inbound telnet traffic from system B or when users on system B telnet to the local system. Since the local telnet daemons will use TCP port 23 and clients on system B will use any unused user-space TCP port, you could use the following command: WARNINGS
requires the optional HP-UX IPSec software. AUTHOR
was developed by HP. SEE ALSO
ipsec_admin(1M), ipsec_config(1M), ipsec_config_add(1M), ipsec_config_batch(1M), ipsec_config_delete(1M), ipsec_config_export(1M), ipsec_config_show(1M), ipsec_migrate(1M), ipsec_report(1M). HP-UX IPSec Software Required ipsec_policy(1M)