The organization I currently work for is trying to sequence and use Dameware Mini Remote Control V6.8.1 using Softgrid V4.2.2.15. We will be upgrading to App-V V4.6.0.1523 next year but until than I need it to work for the older version.

So the problem I'm having is that after sequencing Dameware, when I try to use it on a client computer it gives an error upon connecting to the client that I'm trying to remote into using dameware. If someone has already remoted into the computer and has installed the dameware service on that perticular computer than the sequenced version of dameware has no problems remoting into it.

But if i'm trying to remote into a computer that has not been remoted into previously using dameware or does not have the dameware service installed it gives an error saying that the client computer has actively refused my request. The error and link to damewares knowledge base article are listed below. I looked through it but it says that the problem is generally with the client however it works fine when using a locally installed version of dameware so I don't think there's anything wrong with the client.

I've also tried using ProcessMonitor to monitor the services used with a locally installed version and then adding the files needed to the VFS however so far I haven't had any luck.

Winsock Connect Error:
System Error: 10061
System Message:
No connection could be made because the target machine actively refused it.

Any information would be greatly appreciated.
Thank you in advance for your help.
0 Comments   [ + ] Show Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.


Dameware will usually install the client components on first connection if they don't exist. If you are trying to make a sequence to run on the client machine with the service the sequence will have to be running before a connection will work. You can place a shortcut in the start menu to launch the sequence on user logon but if you need the sequence running before then it could be tricky because App-V needs a user profile loaded for it to launch a sequence.

If it is App-V that is blocking a physical agent installation then there might be an OS integration issue with the virtual application that is preventing the remote agent installation. On a failed attempt is the service partially installed on the target PC or does it even get that far?
Answered 03/18/2010 by: kkaminsk
Ninth Degree Black Belt

Please log in to comment
What i'm trying to do is Sequence Dameware and deploy it to clients throughout our network. When a client launches the sequenced Dameware everything appears to run fine. However if you try to remote into another computer one of two things happen. Either (1) the computer you are trying to remote into has the Dameware services already installed on it (because it was remoted into some other time with Dameware on another computer and the service was never removed) and it works perfectly OR (2) the computer you are trying to remote into doesn't have the Dameware service already installed and the Sequenced Dameware tries to install it on the remote computer. When it trys to do this it errors out with the error given above and I can't seem to find a work around for it.

Again, it works properly if the computer being remoted into by the Sequenced Dameware computer already has the Dameware service installed. However it doesn't work if the that computer doesn't already have the Dameware service installed. Instead it gives the above error.

Hope that makes sense.

Any Ideas?
Answered 04/16/2010 by: bluger86
Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity