Install a linux client - step by step

STATUS CODE: 58, 25 connection errors occur when trying to backup a Linux client or view the client properties
http://seer.entsupport.symantec.com/docs/287346.htm

Overview:
The NetBackup services are registered with xinetd on Linux clients. If the xinetd option only_from = <host_name> is set, it will prevent the system from accepting connections from any system but the host name listed.

This will cause NetBackup to fail with a Status 58 (can't connect to client) when a backup of the system is performed. This can also cause a Status 25 (cannot connect on socket) to appear when trying to configure the host properties for the system.

Troubleshooting:
On the Linux machine causing the error, check the xinetd.conf file to see what options are used for all registered xinetd services. The following example shows that the client will only accept connections from localhost.
# cat /etc/xinetd.conf
#
# Simple configuration file for xinetd
#
# Some defaults, and include /etc/xinetd.d/
defaults
{
only_from = localhost
instances = 60
log_type = SYSLOG authpriv
log_on_success = HOST PID
log_on_failure = HOST
cps = 25 30
}
includedir /etc/xinetd.d


Log Files: N/A


Resolution:
It will be necessary to remove any only_from = <host_name> entries from the xinetd.conf file. The NetBackup daemons may need to receive connections from multiple systems during normal operations. This option will prevent connections from other systems and does not exist by default in the xinetd.conf file.

1. Edit the /etc/xinetd.conf file and comment out or remove the only_from = <host_name> line(s). Save changes.
2. Then, restart the xinetd daemon for the changes to take effect.
# /etc/rc.d/init.d/xinetd restart
3. Retry the connection to the Linux client.

... if you need to mount a windows share on a linux box you're better off googling for 'mount share +linux' - there are a LOT of forums & blogs out there devoted to Linux specifically. [Just confirmed that myself & found enough to help you if this is the direction you need to go].

Once mounted you should be able to cd into that share on the linux client & run the install script as directed above.

I would share this cd2 contents on You windows box - lets call it windows_srv, and the share name as cd2.
Than from linux try to mount this share:
login into linux box,
create a directory called remote_share in root: mkdir /remote_share
mount it: mount -t smbfs \\windows_srv\cd2_share /remote_share

Probably You would need to pass USER ID and its password to access this share.

Of course this is high level procedure - if I were You I would just burn this CD2 contnets onto cd and follow the procedure which was presented here a few post ago ;D.

ok, thanks all but:

i need to take the setup file from network. How can I do this?
Don't work with (
"
Insert CD)
# mkdir /cdrom
# mount -o ro /dev/cdrom /cdrom
# /cdrom/install
"

i agree with what Yasuhisa Itoh wrote. it worked for me.

"...
2 Change your working directory to the CD directory if you have a CD, or to the directory that contains the downloaded files:
..."

The relevant part here is "to the directory that contains the downloaded files" i.e. your network path where you have the install files which you can mount on your linux client?

and when I don't have a CD/DVD ??? I have just a network path where are the kit's/setup files.

but more explicitly, run as follows.

(insert CD)
# mkdir /cdrom
# mount -o ro /dev/cdrom /cdrom
# /cdrom/install
(Enter Master Server Name)
(Enter This Client Name)
(Installation Completed)
# umount /cdrom
# rmdir /cdrom

Can you more explicitly to be, Andy? pls.