Is the MRC Client Agent Service already installed & running on these remote machines? Re: Unable to log onto remote machines using DameWare 5.5.0.2Īre you sure you're specifying the correct TCP port in your Host settings? We have gone onto the DameWare help site and read through the help topics on this error but are still unable to resolve.
If so, have you tried stopping the Service, changing the TCP port, and then restarting the Service?īecause a Winsock 10061 error typically means the MRC Agent Service was not listening on the TCP port that you specified (default is TCP 6129). Then a subsequent attempt at interrogating the Servcie Control Manager on the remote machine failed for some reason (insufficient rights, ports blocked, file & printer sharing not enabled, etc…). This process of interrogating the Service Control manager requires the Operating System's Installed Protocols (File & Printer Sharing - UDP 137, UDP 138, TCP 139, TCP 445) to be open between the loal & remote machines, and it also requires Administrator rights within the O/S security on the remote machine. Therefore if we cannot connect to the MRC Client Agent on the remote machine using the specified TCP port, and then we also cannot communciate with the Service Control Manager on the remtoe machine using Microsoft’s APIs, then we have no choice but to fail. Because these same ports/protocols used by Microsoft’s APIs in order to communicate with the Service Control Manager are the same ones required to install, remove, start, or stop the MRC Client Agent Service on the remote machine.
0 kommentar(er)
