Deploying agents via Scalability Server using the Deployment Wizard end with error "Windows Delivery Failed Failed to obtain package from scalability server. Telnet not enabled on x.x.x.x".
If the Scalability Server uses two NIC cards one to communicate with the Domain Manager and the second with the agents on a different subnet this error may occur,
Ex: 220.127.116.11: known from the DM.
150.150.119.xxx: subnet of the new agents.
Dmdeploy (DSM\logs\TRC_CF_DMDEPLOY_*.log) is able to do the initial install and then instructs dmprimer to get the package from the SS but using the IP address 18.104.22.168:
260514-15:48:22.7935659L|020860|00003a5c|DMDeploy |DmDeploy |cdmdeployer.cpp |001446|WARNING |
Deploying from scalability server 22.214.171.124 to wrks.mydom.com
Then, dmprimer (see file %Temp%\dmprimer.log) fails to connect:
05/26/14 15:48:33 | 4624 | 1488 | cdmprimer.cpp | 2526 | Attempting to open share \\126.96.36.199\DMDeploySS$ 05/26/14 15:48:33 | 4624 | 1488 | cdmprimer.cpp | 2547 | FullUsername mydom\ca_inst 05/26/14 15:49:16 | 4624 | 1488 | cdmprimer.cpp | 2620 | The network path was not found
Nslookup from the agent machine resolves the IP address of the SS as 188.8.131.52 and show a server in the subnet 150.150.119.
Ping works using the name and IP address 184.108.40.206 but mapping the share using the IP address shows a network error.
By default, the deployment wizard instructs the dmprimer process to map the DMDeploySS$ using the IP address.
To avoid the situation explained above it is suggested to map the share using the hostname instead of the IP address by changing the followingconfiguration policy to True:
DSM > Manager > Infrastructure Deployment > Use host names