This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

DameWare MRC v6.1 does no longer work on client computers

Good Morning,

I have been using DameWare MRC for quite some years now and all of a sudden I get the following error:

Winsock Connect Error:

System Error 10060

System Message:

A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

I believe there were settings changed in the group policy that does not allow a client to respond to the remote calls because it stopped working from 1 day to the next.

Still the same OS Windows 7.

I do not have any problems at all to install/uninstall the service via network on the client computers thru the MRC.

Using it on my servers it works perfectly.

Since my domain administrators are glueless what change they could have done with the group policy to prevent the clients from responding and I do not know either I would like to find out thru this route if anyone is outthere that would have idea which setting needs to be switched on the client computers.

Thank you for your time and possible assistance.

Regards.

          Hoagie

  • To be sure.... v6.1 is really old. Version 6.2 was released in May, 2007.

    Support for Windows 7 (released October 2009) was not added until version 6.9 (April 2010), so any functionality you have had with Windows 7 was purely luck.

    As such, there is a vast unknown of possibilities of things that could be configured on a Windows7 system that might adversely interact with an unsupported instance of DW v6.1. If you were using RDP-based connections, then I'd look strongly at changes Microsoft has made in the Remote Desktop Protocol since May 2007, but most likely ones recently implemented. In any event, though, a functional change-documentation record would be your best friend at this point. If the Domain Admins are clueless as to what changed in group policy, you may actually have bigger problems than DameWare. :-)

    As for the Winsock Error 10060, you might start with this article in the DameWare Knowledge Base.

  • Thank you LGarvin.

    I was afraid that I do need a newer version of the MRC.

    Issue on it is I mostlikely need to ask for a older version again since the Military is pretty strickt on the software usage. I am allowed to use only versions that are listed on their approval list and those are usually older versions (I believe right now it's MRC 7.x).

    Regarding the article link - been there and checked it out before I posted this message

    Thank you again for your reply.

    Regards,

              Hoagie

  • hoagie wrote:

    I am allowed to use only versions that are listed on their approval list and those are usually older versions (I believe right now it's MRC 7.x).

    Regarding "the list", certainly v7.5.9 would be a starting point for getting upgraded, but I'd be surprised if newer versions were not already on that list. The last release of v7 is from October, 2011, almost two years ago.

  • Good Morning LGarvin,

    you'll probably smile now but......

    I checked the list yesterday and it is still only showing it up to version 7.x  .

    When it comes to these type of things the military is very slow.

    So I have been trying to get a quote from Solarwinds for a 7.x version before and again this week but no success.

    I don't know if they still have a copy of the old program version but at least I have tried.

    Wouldn't mind though to find someone who would be willing to give up on one of their licenses and donate it.   :-)

    Regards,

                   Hoagie

  • You can only buy the current release.

    I'll check internally and see if we have a scenario that addresses the fact that 7.x is the only "military approved" version.