The below article details what to look for to get a client ready to "receive" the communications package push attempt (you can get to this by clicking through a couple of the links in the communications package udpate article)
http://www.symantec.com/docs/HOWTO80805
Generally speaking, the most common issues are:
- firewall is blocing the connection
- remote registry service is not started on the recipient/target endpoints
- permissions
- Admin$ is unavailable
As an aside, I've always found using SylinkDrop mroe reliable, as it is initiated by the endpoint and I tend to distribute it via script. Much like the one below (which I've posted a few variations of, all over the forums ):
If not exist %temp%\<newsylinkfile> (
Xcopy \\<NetworkLocation>\*.* %temp%
“%temp%\SylinkDrop.exe” –silent %temp%\<newsylinkfile>)
FYI, This article assumes you;ve put the sylinkdrop tool and the new sylink communciations file in a share that can be read by all the endpoints. I normally end up pushing this out via GPO, but it can work with whatever you have for pushing .bat files