Video Screencast Help

DS - randomly failing jobs "A connection attempt failed"

Created: 29 Oct 2012 | 4 comments
LCode's picture

Has anyone encountered randomly failing jobs in Deployment Solution, each time with error "A connection attempt failed because the connected party did not properly respond"?
It only occurs when running jobs at at least 6 computers at the same time.
Oddly enough the jobs don't fail when running them on less than 6 computers.
Mostly it are two jobs in a row which fail and the jobs after them run just fine.
Which two jobs fail is also a bit random.

Situation: new computers are preinstalled by manufacturer with OS (Windows 7) and contain Altiris AClient configured to find the Altiris server using multi-cast.
New computer boots up, agent connects to the deployment server.
Once the new computers are online in the deployment server the jobs to install default software are scheduled on them.

Deployment Solution version used is 6.9 SP3.
The server and computers are located in an isolated network.

Comments 4 CommentsJump to latest comment

andykn101's picture

Are the jobs trying to access the same network file simultaneously from two seperate clients?

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

bhawver's picture

Can you confirm if you are using AClient or DAgent on the Windows 7 machines?  If you are using AClient, this can definitely be an issue as AClient wasn't designed for Windows 7, but DAgent is.

The other question I would have, is how is the Windows server licensed?  Per server or per device/user?  If you are licensed per server, make sure you have enough concurrent connections.

Also, you might check your network connections, a flaky or misconfigured port on your switches can cause issue as well.

Brian Hawver
Systems Engineer
Yaskawa America, Inc.

Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.

LCode's picture

The jobs that mostly fail contain distribute software tasks.
The Windows 7 machines are indeed installed with AClient. We already have tested with DAgent but same issue occurs. We made sure that AClient was completely installed before installing DAgent.

I have to check about the server licensing. Amount of concurrent connections could be an issue.

Switch would not be the problem because it is an unmanaged switch which is not connected to corporate network. It is a complete separate network just for preparing new computers.

One of the first jobs that is being executed is disable Windows Firewall, and this job always runs fine. With Windows Firewall turned off it should not be interfering with the next scheduled jobs.

IT Consultant - IT LifeCycle Management/Symantec Endpoint Management @Xylos

bhawver's picture

I assume you mean you made sure that AClient was completely UNinstalled before installing DAgent...right?

On a machine that is experiencing the issue, can you double-click on the DAgent tray?  What does the Status say when this happens?

Brian Hawver
Systems Engineer
Yaskawa America, Inc.

Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.