The version of ESX is 3.0.0 and in the future we are planning to install the 3.0.1.
now i the 3.0.0 infrastructure.

the version of networker is 7.3.2 client linux
the version of the serve is 7.3
maybe is this the problems?
do i need to update the server?

the daemons nsrexecd is running

ps -ef | grep nsr

root 3205 1 0 14:10 ? 00:00:00 /usr/sbin/nsrexecd
root 3432 2684 0 16:54 pts/0 00:00:00 grep nsr

Patrizio,

Which is your ESX version?

Can you verify if the daemons on the client are running?

I don't believe your problem is version. This ESX version is compatible with your Nw version.

Server 7.3 should also work with clients in 7.3.2, but as 7.3.2 fixes a lot of bugs (and brings new ones), it may be related, but only upgrading or contacting support would give you a correct answer.

I would first verify network connections using ping, trace, nslookup and reverse nslookup, from both server and client. I believe you already did this, but I don't see any other options here. Maybe someone with more experience working with ESX could give us any details we might be forgoting...

trace and nslookup work correctly is not a problem of TCP/IP because work all
i think that maybe is a problem of installation of server or client side

ping work good from server to client:

Pinging xx.xxx.xx.xxx with 32 bytes of data:

Reply from xx.xxx.xx.xxx: bytes=32 time<10ms TTL=64
Reply from xx.xxx.xx.xxx: bytes=32 time<10ms TTL=64
Reply from xx.xxx.xx.xxx: bytes=32 time<10ms TTL=64
Reply from xx.xxx.xx.xxx: bytes=32 time<10ms TTL=64

ping work good from client to server:

PING xx.xxx.xx.xxx (xx.xxx.xx.xxx) 56(84) bytes of data.
64 bytes from xx.xxx.xx.xxx: icmp_seq=0 ttl=128 time=0.204 ms
64 bytes from xx.xxx.xx.xxx: icmp_seq=1 ttl=128 time=0.169 ms
64 bytes from xx.xxx.xx.xxx: icmp_seq=2 ttl=128 time=0.180 ms
64 bytes from xx.xxx.xx.xxx: icmp_seq=3 ttl=128 time=0.195 ms
64 bytes from xx.xxx.xx.xxx: icmp_seq=4 ttl=128 time=0.165 ms

i set the local host with the ip when i try to connect in the neworker administrator configuration it write remote-system error (it is block for 15 second at 5% starting operation...)

now i want to try to install the client in HP UX system and if work is a problem with ESX server

someone can provide me the link for download for the correct client networker for VMware ESX server
are there some modules that i have to install an the server side of networker to see linux version?
i have to set particular option for the server side of networker to see linux version?
thank a lot
Patrizio

Message was edited by:
Patrizio

Message was edited by:
Patrizio

If you query rpc service from server do you get positive feedback?

the rpc service from sever work properly...
on the ESX server in /etc/rpc file there is

nsrstat 390109
nsrjbd 390110 nsrjb
nsrexecd 390113 nsrexec
ecc
is correct?

i don't think i have a problem with network....
however thanks a lot...now i read the documentation if i forgotten something

Message was edited by:
Patrizio

do i have to install a linux module on the networker server windows?

i have to install NetWorker ClientPak for Linux in windows server installation? where i can dowload it? i need a license?

Message was edited by:
Patrizio

Is your server running on Windows? If so, you'll need a ClientPak for Linux license, so you can backup linux clients to you Windows server.

ClientPak is just a license, you don't need to download anything.

It depends what you wish to backup and how do you wish to restore it. Clientpak is license which gives you right to backup system with different OS than your backup server.

Back to your original issue; when you run following from backup server against Linux box what do you get:
echo print | nsradmin -p 390113 -i - -s client_name

Try the same in other direction too.

yes i read this yesterday on the administration guide:

If only the NetWorker client software for Linux is being installed, purchase the NetWorker ClientPak for Linux with a separate enabler code. The NetWorker for Linux software is licensed as a separate platform.

so is not a problem of installation but of license because my server is windows version...
do i have to order the licensing true?
now i check on my company if there is...
thanks a lot and if is this the problem next time i read better the documentation.

now work it was a firewall problem...not license problem :P
thanks a lot to all for the support
patrizio

What ports did you have to open in the firewall?

I'm having the same issue.

Hi,

ESX server is a linux client.I have backed up ESX using 7.2.2.-clinet and 7.2.1-server.
- Have you tried telneting on legato ports from both sides
- If the Networker server is running on Windows do you have client pack for linux and client connection license installed
-Whats the error yoy are getting when starting backup

Thanks
Saleesh