Deployment Solution

I am trying to push AClient to our network machines. Here is the specs on the client:

Server 2008
SQL 2005
Deployment Console
Version 6.9 (build 355)
Service Pack 1
10000 node
altiris-aclient-6.9.355.X86
2999 machines on the network, 1600 reporting in that accepted AClient


Install settings:
Connecting to server xxx.xxx.xxx.xxx on port 402.
This agent can be remote controlled from the console.
The agent is password protected.
Prompting for execution, reboot, and/or remote control events.
The user will be prompted for 10 seconds, then the operation will continue.
Always connected to the server, refreshing every 28800 seconds.

I have updated our server from 6.5 to 6.9. I have uninstalled the 6.5 agent from the old Deployment Console by advanced, uninstall windows agent, and then push the new client from the new Deployment console.  I get this error message on most machines:

Events:
Starting install for machine xxxx
'The network path was not found.' . Unable to connect to computer xxxx with username xxxx. I have tried the express account which is on all of our network machines, and I have also tried my credentials which has Domain Admin rights, but none of the settings work.

Does anyone have any idea what is going on?

Thanks
Curt

 On the machines that you are having problems pushing to, can you connect to their admin share from the DS server?

i.e. \\client\c$

If you can't that would be the problem.  To do a remote installation Altiris requires a netbios/rpc connection.  If file and print sharing is turned off or firewalled, this will prevent you from installing remotely.

Could be the clients are turned off too.  The netbios thing sounds more likely tho.

Agreed with bhawver, did you check the firewall settings for your network connection?

try pinging the machine (to check firewall), also check that simple file sharing is turned off. 

Some VPN software has a stateful firewall that is on, whether it is VPN'd or not.

Neil

I agree with  neil_rogers post, try to ping the machine, see the result, then check the firewall. See if there is an exclusion or better disable it during agent installation.