However if you try to remote into another computer one of two things happen. When a client launches the sequenced Dameware everything appears to run fine.

What i'm trying to do is Sequence Dameware and deploy it to clients throughout our network. No connection could be made because the target machine actively refused it.Īny information would be greatly appreciated. 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. 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. The error and link to damewares knowledge base article are listed below. 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.īut 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. 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. next year but until than I need it to work for the older version. 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.

Dameware connect to client