I am using Networker 8.2.2. I have a data domain 620. When I try to mount the volume through the Networker Administration module I am getting the following error:

In short you need to check if proper resolution is happening with fqdn and short names of DD and NW server. Check for the management IP of DD and if it is reachable from NW server. Recommended to make DNS entry for the same mgmt IP

Tried that already.  Am actually working with support to resolve the issue.  We have run the ddpconnchk utility and it is resolving correctly

can hardcode the DNS information into the host files on both the DD and the server/servers and this should resolve the issue. Unless there is a firewall involved.

as Hrovje said be aware that if NMC is nit running on the backupserver itself, its the NMC that tries to communicate directly with a DD and not via the backupserver (which if one would have a centralisef NMC to manage multiple NW servers eould make sense but alas emc did not setup communication like that. as in our case often nmc is hosted on the management vlan and not on the backup vlan, we also have installed nmc on the backupserver that is hsoted in the same vlan as the DD's or at least is able to directly connect to them via correctly defined static routes or preferably by making setting their default gateway for their backup interface, then also all client connectivity would be always going via that interface not requiring any static routes to be defined, except possibly for managent nic connections to other subnets).  besides creating ddboost devices via the device wizard the same applies to the client wizard, as via the NMC on the  backup server and its backup nic we have access to the clients to be able to browse their filesystems or configure application backups via the wizard. but via the normal. NMC we dont. by design alas. lets hope that emc will make that more transparent in the future so that nmc does not have to have access itself towards cluents and DD appliances but that all communication will route through the nw backupserver as it should.  and if you dont know about routing, you should be talking to your sysadmin as otherwise you might break your existing connectivity. is for instance always the tricky part when changing default gateway on a DD which might in certain situations cause bot being able to reach nor manage it, depending if you might have setup console functionality correctly...

Barry you have nipped it very well. I too faced this issue with Networker 9.1 and DD OS 6.0.x. We too had NMC on different systems and was on Management ip rather than on Backup VLAN. 
error message : 5037 cannot resolve ip address from DD host

We could not mount any DDboost devices even local devices on Networker server.

However after adding Static route problem got resolved

Hi Barry,

Is the communication between NMC and DD for nsrim or saveset expiry?

you are replying to a post that was 7 months ago...