We have all been waiting for this, and now it's here: the Dameware 12.0 Release Candidate is now ready for you on the Customer Portal! Don’t wait, just download it while it’s still fresh and hot.

This release brings several bigger and smaller improvements, so let me highlight a few of them:

• Over the Internet (OTI) unattended sessions for Dameware Centralized users
  • Allows you to remotely support users on the move, and assist remotely without the presence of the end user
  • Deploy agents with OTI unattended support to end-points
  • Manage agents for OTI unattended sessions to maintain high security and control
• Search Hosts in Mini Remote Control
• Support for Windows 10
• Ability to switch between the Standalone and Centralized versions without reinstallation
• And many other improvements and bug fixes

If you want to learn a bit more about the new features read about them in Dameware 12.0 Release Candidate is Available now! blog post.

Enjoy!

Hallo,

wir setzen Dameware MRC V.12 auf jedem unserer IT-PC ein und planen eine zentrale Ablage der Client-Liste samt Mac-Adresse etc. für den Wake-on-LAN Einsatz.

Dies funktioniert soweit lokal an einem PC schon gut, jedoch bietet das WOL-Fenster nur Zugriff auf die Saved Host List eines jeweiligen Rechners.

Gibt's es eine Möglichkeit diese Einstellung zu beeinflussen/ändern?

Die Global Host List kann ich z. B. am Server befüllen, jedoch bräuchte ich diese List dann wiederum im WOL-Fenster.

Hat hierzu irgendjemand einen Tipp oder Erfahrung?

Besten Dank im Voraus.

Siegfried Fedrich

Hi,

we've enabled Microsoft's Security Baseline via GPO to our Windows 10 computers. If we now like to use dameware 12 to  remote control a computer the authentication is not working through.

No matter which protocol from the dropdown list (Windows NT Challange / Response, Encrypted Windows Logon, ...)  is used it all fails.

Somebody meet this situation and knows what to do? Is there a configuration in dameware that can be changed to work with the basline or did u change a setting on the baselines?

Windows Security Baselines | Microsoft Docs

I have checked the application log of the remote machine and found these events:

I know that NTLM version 1 is deactivated via Security Basline, but I assume Damware is using Version 2?

Thanks in advance

Ruben

Hello,

We`re going to migrate W7 to W10 and our service desk agents are currently using Dameware 9.x to remotely support the end users. We`ve been testing Dameware 9.x on Windows 10 machines and it seems to be working fine, but I wonder if this version is really officially supported.

Does anyone has any information about support? I asked the support but I did not get the answer.

Thank you

Hi,

New to DWRS - I have looked at the various installation suggestions based on use cases but the admin machine in my case will not be part of a corp domain.

I would like to support multiple domains from my laptop outside of their firewall without being joined to any of them. I have access to firewalls, AD and can install whatever VMs/Components are needed in each supported domain.

What would be the best installation template for this scenario?

Thanks

Hello DameWare users!

Here is a brief guide to shows how to gather information from computers in your network or domain using the DameWare Exporter tool included with DameWare Remote Support.

Objectives:

1- Get "Installed Software" data from computers in my network to create a report.

2- Get the information in a CSV file format so it can be easily imported into an Excel spreadsheet

3- Get the information from several computers in a single file

First, you have to launch the tool. You can find it in the same location as the main DameWare Remote Support application (Start > Programs > SolarWinds > DameWare Remote Support 9.0 > DameWare Exporter). You can recognize it easily by the colors in the icon (blue/yellow) :

In the Exporter tool you must change the settings so the files created have the CSV format instead of XML (which is used by default). In this example we want to get "Standard" information (which basically means we are pulling data from the machine instead of Active Directory) so that's the tab we need to modify:

NOTE: The "Single File" option here indicates that a single file will be made per-machine including all properties selected. It DOES NOT mean a single file will include each computer.

Once the output file type is set, do the following:

1- Under "Task List" uncheck everything except for Standard Properties - Software.

2- Click the "Add Machines" button to include the computers you want to survey.

3- Make sure all the systems in the "Computer List" are checked

4 - Click on "Start Exporting"

After this you will end up with a .csv file for each computer you surveyed. Unfortunately, DameWare Exporter doesn't feature an option to generate a single file for all the computers. However,  CSV files are easily merged using the Windows copy command. Place all the files in the same folder and run the following command in the Command Prompt:

copy *.csv allcomputers.csv

This line will create a new file, "allcomputers.csv" (you may use the name of your choice) that will be a merging of all .csv files found in that folder.

Hi,

I have a problem with DameWare Remote Support v9, I am unable to connect using the DameWare Mini Remote Control when the "Permission Required" setting is enabled on the "Additional Settings" tab within the settings of the MRC Client Agent Service on the remote machine. When enabled, this option should prompt the currently logged on user to grant or deny permission for every connection attempt.

Unfortunately when I try to connect from my local machine to remote machine instantly I get an error:

"DameWare Mini Remote Control

Your logon request was declined.

Disconnecting...

Request for permission to remote control encountered an error.

- Failed to send from socket (5). [10047]"

In Windows event log is an error:

'Error: Failed to acquire logon permission.

User Disconnected."

The currently logged on user on the remote computer don't even have a chance to accept or decline my connection (there is no pop up window asking for permission).

When I disable "Permission Required" setting on the remote machine I can establish the connection  from my local machine without any problem but also without asking for permission the currently logged user.

Both computers runs Windows XP Pro 32-bit version.

From the security reason in my computer environment  "Permission required" setting must be enabled on remote machines, but currently it doesn't work.

I would really appreciate some help and advice.

Note: This is a topic brought over from DameWare Forums which has been closed. If you wish to engage in this discussion, just comment here.

Unable to log onto remote machines using DameWare 5.5.0.2
by threeofspades on Thu Sep 13, 2007 5:34 am

Hi All,

We are currently having issues with logging onto some of our machines using the DameWareMini Remote Control. We recently installed some Microsoft patches on the machines and this has resulted in us having to log onto the machines using Remote Desktop rather than DameWare. Do you know of any Windows updates that may affect DameWare connection? When we try toconnect using DameWare we get the Winsock error:

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

We have gone onto the DameWare help site and read through the help topics on this error but are still unable to resolve.

Any help would be greatly appreciated.

Kind regards.

Re: Unable to log onto remote machines using DameWare 5.5.0.2
by bryan on Fri Sep 14, 2007 11:13 am

Hello threeofspades,

Are you sure you're specifying the correct TCP port in your Host settings?
Is the MRC Client Agent Service already installed & running on these remote machines?
If so, have you tried stopping the Service, changing the TCP port, and then restarting the Service?

Because 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.

However, please also click on the Copy button on the Winsock Error Dialog, then send me this information (paste it into this email) back to me for examination. Also include a screen shot of the actual Winsock Error dialog as well so I can review it.

Your feedback is appreciated.

Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com

Re: Unable to log onto remote machines using DameWare 5.5.0.2
by threeofspades on Mon Sep 17, 2007 6:19 am

Hi Bryan,

Thank you for your response.

I have some additional information that may help to try to resolve this issue.

I can use MRC on the servers themselves to connect to my own machine, but am unable toconnect from my machine to the servers using MRC.

When i try ot connect to the server using MRC i first get a message saying the following:

"The DameWare Mini Remote Control is not running on onyxctx2.

Would you like to start it now?

Host: onyxctx2".

I select OK but then get the following error:

"Unable to start Service
System Error: 2
System Message:
The system cannot find the file specified"

When I RPC'ed onto the server and checked the DameWare Mini Remote Control service is was not running. When i selected to start it i get the error:

"Could not start the DameWare Mini Remote Control service on Local Computer

Error 2: The system cannot find the file specified."

When i checked the path to the executable 'C:\WINDOWS\system32\DWRCS.EXE -service' the DWRCS.EXE was not in there.

I have tried to load DameWare again but get the same errors. It seems that this executable has been deleted for some reason. How can i retrieve it or load it again?

Thank you for your time and effort.

Kind Regards

Re: Unable to log onto remote machines using DameWare 5.5.0.2
by bryan on Mon Sep 17, 2007 10:37 am

Hi threeofspades,

You're welcome and thank you for this additional information. It was very helpful...  

As you have already found, Microsoft's System Error: 2 means File not found, and that's definitely due to the DWRCS.EXE file being missing in the System32 folder.

However, all you should have to do is re-copy the DWRCS.EXE file from your local DameWareInstallation folder to the System32 folder on this remote machine. Then you should be able torestart the Service again.

But you might also want to do a little extra research to find out how this file could have been deleted.

I hope this helps.

Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com

Re: Unable to log onto remote machines using DameWare 5.5.0.2
by threeofspades on Tue Sep 18, 2007 4:43 am

Hi Bryan,

I took your advice and copied the DWRCS.EXE file from my local machine to the WINDOWS\system32 folder on the server.

When i tried to MRC onto the server i got the request:

"The DameWare Mini Remote Control is not running on onyxctx2.

Would you like to start it now?

Host: onyxctx2".

I selected OK and it came up withthe message:

"Service Start Status:

Starting service....."

I thought that this was looking good but unfortunately it came back to the above message:

"The DameWare Mini Remote Control is not running on onyxctx2.

Would you like to start it now?

Host: onyxctx2".

It seems that the service is starting but is tehn stopping several seconds later.

I RPC'ed onto the server to check out the DameWare Mini Remote Control service. It was setto automatic and was not started. i set it to start and it did so. But about 5 seconds later it just stops.

Not sure what is going on but something is stopping the service from running.

Any ideas?

Kind regards

Re: Unable to log onto remote machines using DameWare 5.5.0.2
by bryan on Tue Sep 18, 2007 1:46 pm

Hi threeofspades,

Thanks very much for the update. This is some great information.

I believe you're right. There appears to be something else here that's stopping the Service from running. What other software do you have running on this machine? Do you have anything like CA eTrust, or Pest Patrol, or Pest Patrol remote (look for ppRemoteService.exe in Task Manager under Processes)?

If this is the cause, then additional information on how to configure the appropriate exception within Pest Patrol is also available in another thread on our forum:

The Dameware mini remote service is not running on XXX.
http://forums.dameware.com/viewtopic.php?f=8&t=47

Your feedback is appreciated.

Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com

Re: Unable to log onto remote machines using DameWare 5.5.0.2
by threeofspades on Thu Sep 20, 2007 5:42 am

Hi Bryan,

Thank you for all your help.

We do have eTrust running on our systems and when i placed the DameWare exception into the Management Console i got DameWare back working on all but one server. But i will check it out and see if i can figure out where the problem is. I'm sure it's just something simple but the service still seems to be stopping on that particular server.

Thanks again for all your help and it was very much appreciated.

Kind Regards

Note: This is a topic brought over from DameWare Forums which has been closed. If you wish to engage in this discussion, just comment here.

one more time about user notify dialog
by MasTiCorE on Mon Nov 19, 2007 3:14 am

i knew FAQ, search do not give me answers.

i want to connect to users without confirmation notify dialog.
i've entered key into dmware nt utilities, also, as it in FAQ, i tryed ro re-activate dameware mini remote control. Also ths not helped.
before install i've editied configuration file, set no notify dialog, and installed service with this configuration.
Not helped. Why?

PS: sorry for my bad english, no practice..

Re: one more time about user notify dialog

by bryan on Mon Nov 19, 2007 4:33 am

Is this a "Permission" dialog that the user must click on "Accept" to allow you to connect? Do you see the text "Waiting for CLient to Accept the Connection" dispalyed within your Status bar at the bottom of your MRC window?

Or is this the Notify dialog that is displayed in the lower right-hand corner of the screen after you have already connected? Do you see the text "Evaluation" displayed within this Notifywindow?

Your feedback is appreciated.

Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com

Re: one more time about user notify dialog
by MasTiCorE on Mon Nov 19, 2007 7:58 am

Bryan wrote:Is this a "Permission" dialog that the user must click on "Accept" to allow you to connect? Do you see the text "Waiting for CLient to Accept the Connection" dispalyed within your Status bar at the bottom of your MRC window?

yes. I want to hide it.
user do not see icon of dmware in tray, no menu
but "Permission" dialog is showing every time that i want to connect.
user can click on "Decline". But i want, that user do not know about connected people to his computer.

Bryan wrote:Or is this the Notify dialog that is displayed in the lower right-hand corner of the screen after you have already connected? Do you see the text "Evaluation" displayed within this Notifywindow?

nope, no evaluation enyware.

Re: one more time about user notify dialog
by bryan on Tue Nov 20, 2007 11:19 am

So this is actually the Permission Required dialog, not the Notify dialog.

The need for Permission (Accept/Decline) when connecting to a remote machine using the MRC software is primarily based upon what right you have within the O/S security on that remote machine. However, the current Desktop State on the remote machine, and also some settings within the software itself are also factors in this equation as well.

Therefore, the very first thing you need to examine is what rights your credentials have within the O/S security on this remote machine, Administrator or non-Administrator, and by non-Administrator this refers to everyone that is not a member of the Administrators group on that machine either directly or indirectly via some other group membership.

There is also a "Permission Required" setting within the MRC Client Agent Service on the remote machine as well. Here is some additional information with regard to Permission that will hopefully help you out:

Administrators:

Administrators by default do not require permission in order to connect to any remote machine, unless you enable the “Permission Required” setting within the MRC Client Agent Service (at the top of the Additional Settings Tab). Then any Administrator would also require permission to connect. However, this does not apply when the remote machine is currently at the Logon Desktop or Lock screen. There is no way to prevent any Administrator from connecting to a remote machine when it is currently at this Desktop state.

Non-Admins:

Non-Admins cannot connect to any remote machine without requiring explicit permission from the Desktop user, regardless if the “Permission Required” setting was enabled or not. This is built into the software. The only time a non-Admin could possibly connect without requiring permission would be if the remote machine was currently at the Logon Desktop or Lock Screen. Then access would be Allowed or Denied based upon the “Disconnect if at Logon Desktop” setting (at the bottom of the Access Tab).

There are also several settings within the Client Agent that pertain to non-Administrator accounts that affect permission. If you look at the bottom of the Access Tab within the Client Agent Service, you will see three settings. "Permission Required for these Account Types", "Disconnect if at Logon Desktop", and "View only for these account types", and each of these settings only pertain to non-Administrators (not Administrators).

Another thing to keep in mind is that when you connect to a remote machine, it will be in one of two states:
1. Machine is sitting at the "Logon Desktop" or "Lock" Screen. Hence a user is not present on the remote machine.
2. Machine is not at the Logon Desktop or Lock screen, hence a user is currently logged into the desktop.

Scenario 1:
A non-Administrator tries to connect and the remote machine is currently at the Logon Desktop or Lock Screen. The non-Administrator will only be allowed to connect if the "Disconnect if at Logon Desktop" feature has been disabled (it is enabled by default). If it's enabled, their connection request will be denied with a dialog box stating: "The remote machine is currently at the Logon Desktop. Your credentials do not allow you to access the remote machine at the current desktop state". (just as you were presented with below)

Scenario 2:
A non-Administrator tries to connect and the remote machine is NOT currently at the Logon Desktop or Lock Screen (hence user is logged in). Then you must look at the "Permission Required for these account types" field.

A. If "Permission Required for these Account Types" is enabled, then whoever is currently logged into the desktop of the remote machine will be presented with a Permission Required dialog box asking to Accept or Decline this non-Administrator's connection request. If they press the Accept button, then the non-Administrator will be allowed to connect. If they press the Decline button, or if the dialog times out with no response, then the non-Administrator will not be allowed to connect.

B. If "Permission Required for these Account Types" is NOT enabled, then the non-Administrator's connection will be immediately denied with a dialog box stating: "The Remote machine is not currently at the Logon Desktop. Your credentials do not allow you to access the remote machine at the current desktop state".

I hope this helps.

Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com

Re: one more time about user notify dialog
by MasTiCorE on Mon Jan 14, 2008 8:21 am

thanks for your answer! It's helped to understand. 

Re: one more time about user notify dialog
by bryan on Wed Jan 30, 2008 4:10 pm

You are absolutely welcome.
It was my pleasure helping you out.

Best Regards,
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com

Re: one more time about user notify dialog
by lufoxe on Wed Apr 23, 2008 11:48 am

Hi Guys, I am having the same issue, I am a local administrator on the machine, however I am still getting the dailog box   is there anyway to force that off? remotely. I have tried remove and installing the service, also the DWRCs.ini file with the setting unchecked. any help?

Re: one more time about user notify dialog
by bryan on Wed Apr 23, 2008 1:23 pm

Hello lufoxe,

Admin vs. non-Admin rights are not a factor for determining if the "Notify on connection" dialogis displayed when you connect. So are you speaking about the "Notify on connection" dialog that is displayed in the lower right-hand corner of the remote machine when you connect? Or are you speaking about the Permission Dialog, which requires the desktop user on the remote machine to physically press the Accept or Deny button for your MRC connection? If it's the Permissiondialog, then please see my previous post in this thread to resolve this behavior.

With regard to the Notify dialog, the first thing you must look at is if your local copy of the Mini Remote Control program is currently registered, or if its running in Evaluation Mode (Help /About DameWare MRC). Because if it's running in Evaluation Mode, then the notify dialog will always be displayed on the remote machine when you connect, no matter what settings are currently in the DWRCS.INI file. You will also see the text "Evaluation" displayed within the notifydialog as well.

The only other factor would be the actual configuration settings for the Client Agent Service itself, which are located on each individual remote machine. These configuration settings will either be stored in the Registry, or in the DWRCS.INI file, depending on how you configured the Service. During startup, the Service will first look to the "Use Registry for all Settings" key. If this is set to 1 (one), then all the additional settings will be retrieved from the Registry and the DWRCS.INI file will be ignored. If this key does not exist, or is set to 0 (zero), then the settings will be read from the DWRCS.INI configuration file instead.

[HKEY_LOCAL_MACHINE\SOFTWARE\DameWare Development\DWRCS\Settings]
"Use Registry for all Settings"=dword:00000001 or dword:00000000

However, are you looking at the DWRCS.INI file on your local machine, or in the System32 folder on the remote machine? Because the one on your local machine (in your DameWare Installation folder) is only pushed out the remote machine during Service installation, and then only if you also enable the "Copy configuration file DWRCS.INI" setting during the install. It is not copied to the remote machine each time you connect.

During the installation of the Service, click on the Install Options button then enable the "Copy configuration file DWRCS.INI" setting. Now click on the Edit button to modify the DWRCS.INI configuration file on your local machine. On the Properties dialog, select the "Notify Dialog" Tab and disable the "Notify on Connection" setting. Now click on OK twice to return back to the Service Installation dialog. Click on OK to complete the install of the Service, including your new DWRCS.INI configuration file.

I hope this helps.

Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com

Re: one more time about user notify dialog
by lufoxe on Thu May 01, 2008 5:52 pm

Thank you,
That has been a great help. I was reffering to the prompt not the eval version dialog.
Thank you very much

Re: one more time about user notify dialog
by bryan on Fri May 16, 2008 11:51 am

Hi lufoxe,

You are most welcome.
I'm glad we could help.

Best Regards,
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com

Note: This is a topic brought over from DameWare Forums which has been closed. If you wish to engage in this discussion, just comment here.

System Error: 5 Acces is Denied ??? [I PUT LOGS]
by Mrconnard on Wed Jan 30, 2008 1:13 pm

Hello everybody, i got this error today:

AUthentification failed:
System error: 5
System message: Access Denied
Please check the event log on the remote machine for possible cause

And the event gives me this:

Date:01/30/0823:55:21
ComputerName:DJ0DJ0
UserID:DjoDjo
LogonAsID:
Domain:
OSProductID:55274-642-5926024-23226
OSRegisteredOwner:Dj0Dj0
OSRegisteredOrganization:Dj0Dj0
HostNamefromPeer:dj0dj0
IPAddresse(s)fromPeer:192.168.0.17
Host:
IPAddress:(HIDDEN)
ProtocolVersion-DWRCC.EXE:6.650000-2.000000
ProtocolVersion-DWRCS.EXE:3.600000-0.600000
ProductVersion-DWRCS.EXE:3.63.1.0
AuthenticationType:NTChallenge/Response
LastErrorCode:0
LastErrorCode(WSA):0
Absolutetimeoutsetting:0minutes
Connect/Logontimeoutsetting:90000miliseconds
AccessCheck:
  0 LfLes
º G
º G  ^^* DWMRCSSERVER_NECH
DameWareMiniRemoteControl
SystemError:10061
Unabletoconnecttomailserver-Error:100610 (    """"3333DDDD0 ¸t (

I don't know if the last part (SystemError:10061
Unabletoconnecttomailserver-Error:100610 (    """"3333DDDD0 ¸t ()
is really part of the log concerning DWRCS because the event log was corrupted so ...

I thought it was due to the Absolute timeout setting put to 0 but i don't know..

I hope you'll be able to help me. Thanks in advance

Re: System Error: 5 Acces is Denied ??? [I PUT LOGS]
by bryan on Wed Jan 30, 2008 1:31 pm

The remote machine appears to be running a much older version of the software that we no longer support (i.e. version 3.x).

Therefore, I would suggest you first remove this older version of the Service and install your current version of the Service on the remote machine.

If you still receive the Access Denied error using the current version, then either paste those logs back here again, or send them to our support staff at support@dameware.com for review. There should also be multiple DWMRCS entries, so send the entire text from each entry.

Your feedback is appreciated.

Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com

Re: System Error: 5 Acces is Denied ??? [I PUT LOGS]
by Mrconnard on Wed Jan 30, 2008 1:40 pm

But... i managed to access this remote machine yesterday and then i DIDN'T touch anything (neither settings nor anything else) and now it doesn't work.. So it's not a problem of too much old version.

Re: System Error: 5 Acces is Denied ??? [I PUT LOGS]
by bryan on Wed Jan 30, 2008 2:02 pm

According to the log you posted, this remote machine is running version 3.63 of the MRC Client Agent Service.

ProtocolVersion-DWRCS.EXE:3.600000-0.600000
ProductVersion-DWRCS.EXE:3.63.1.0

... and you will not be able to connect to version 3.x of the Client Agent using any 6.x version of the software.

Therefore, please remove the MRC Client Agent from this machine and install the current version. Then you should be able to connect.

You may also want to check the logs on this machine to see if someone else connected after you did and downgraded the Client Agent to this older version. That's the only explanation I can offer at this time.

I hope this helps.

Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com

Re: System Error: 5 Acces is Denied ??? [I PUT LOGS]
by Mrconnard on Wed Jan 30, 2008 2:09 pm

In fact, i connected yesterday for the 1st time to this machine with the DWRCS CLIENT version 3.60.... so i installed the version 3.60... on the remote machine... and it worked! i didn't upgrade the remote version.. (today i tried with both versions of the client and none worked)

Re: System Error: 5 Acces is Denied ??? [I PUT LOGS]
by Mrconnard on Wed Jan 30, 2008 2:33 pm

And i forgot to say i had a "Access denied" with DNTU 6.6 !! for the remote command view and a Error for the event logs ...
So it's not linked to DWRCS in fact :s

Re: System Error: 5 Acces is Denied ??? [I PUT LOGS]
by bryan on Wed Jan 30, 2008 3:24 pm

If you in fact connected with version 6.x of the software to a 6.x Client Agent service on the remote machien, then send me the log files from that connection just as I asked you in my original response. Because without that information I cannot help you. Also send me all of the DWMRCS log entries associated with this failed login attempt, not just the connect or disconnect entry.

- What rights do you have within the O/S security on the remote machine?
- What O/S and Service Pack level is installed on both the local & remote machines? If it's XP or Vista, also distinguish the exact version of the O/S as well (i.e. XP Home, XP Pro, etc...).
- Are these machines located on the same LAN, over the WAN, accross the Internet?
- Can you access the Admin$ share on the remote machine (net use \\remotemachine\Admin$) via a CMD prompt on your local machine?

Also, just FYI, DNTU uses a completely different set of ports & protocols and wouldn't have anything to do with your behavior via MRC. Microsoft's APIs used within DNTU use what's called NT "Pass-Through" authentication. Therefore, if you receive Access Denied errors using Remote Command View or Event Log View, this means your current O/S logon credentials don't have sufficient rights within the O/S security on the remote machine. Therefore, you would have to establish an authenticated connection to this remote machine using sufficient credentials (i.e. Administrator), either within the O/S itself or by using DNTU's LogonAs feature.

Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com

Re: System Error: 5 Acces is Denied ??? [I PUT LOGS]
by Mrconnard on Wed Jan 30, 2008 3:44 pm

- What rights do you have within the O/S security on the remote machine?
Administrator rights in theory..
- What O/S and Service Pack level is installed on both the local & remote machines? If it's XP or Vista, also distinguish the exact version of the O/S as well (i.e. XP Home, XP Pro, etc...).
Both XP Pro
- Are these machines located on the same LAN, over the WAN, accross the Internet?
Across the Internet
- Can you access the Admin$ share on the remote machine (net use \\remotemachine\Admin$) via a CMD prompt on your local machine?
No.. Error 1219

Most of our users now have 2 - 3 displays. Is there a way to show all displays by default when connecting to he user's PC? 

Can I uninstall software remotely from the DRS interface?  Looked for a "how to", but could not find.  I'd like to uninstall unneeded software from remote computers without logging into them at a specified time.  I am a network admin and have an admin acct. on most of the remote computers.  Thanks.

Last year when we renewed our licenses we upgraded from ver 9 to version 11.  I put together a Centralized server which everyone now logs into to use DameWare.  However, when I tried to enter the keys into the License Activation program it wouldn't accept them and I had to open a service request to get it resolved so we could use DameWare.  Earlier this year I expanded my license count, and again, when I tried to update using the License Activation program it wouldn't accept the keys so I had to open another service request.

I just upgraded to the new Version 11.2 and renewed my licensing again for another year.  However, it is not reflecting in either the Server Admin Console or the Activation program.  Both still show the license is only valid through the middle of next week and the Admin Console comes up w/ warnings that there is only 7 days left.  When I click the "I Already Paid" button in the warning it just opens the web page for me to sign into.  I found the License Manager out there and downloaded it.  I ran the sync on that and it comes back fine, shows that I'm good through next year.  Still not updating in the Admin console.  I can enter the keys from my info on the customer portal in the Activation program and at least it shows that it takes them - used to always fail.  However, the dates are still showing that my licensing is about to expire.

What am I missing?!!  Why isn't it updating the date info for me so I'm not seeing the errors in the Admin console any longer?!

Hi all,

I am having issues authenticating to a client machine. I am using Dameware Mini Remote Control version 7.5.9.1. I have attached a picture so you can see the exact error I am receiving. I can log onto the remote machine via the Windows NT Challenge/ Response option. It won't seem to authenticate the smart card for whatever reason. I have checked for the DWRCSS.dll in %systemroot%\DWRCS on the local and remote machines. It is in both locations. Any help on this issue would be greatly appreciated.

Note: This is a topic brought over from DameWare Forums which has been closed. If you wish to engage in this discussion, just comment here.

The Dameware mini remote service is not running on XXX.
by Jodi on Mon Jul 09, 2007 5:28 pm

The full text of the message is The Dameware mini remote service is not running on xxx. Would you like to start it now? I answer OK and get "Unable to Start Service; System Error 2; The system cannot find the file specified. It started on a server this morning. After doing a random check of the computers on our domain I have found that it is random. Some machines are ok, some I can't access. It is not dependent on a specific operating system. Can anyone help?

Thanks.
________________________________________
Re: The Dameware mini remote service is not running on XXX.
by bryan on Mon Jul 09, 2007 6:02 pm

Hello Jodi,

Exactly what version of the MRC Client Agent Service do you have installed on these remote machines (right-click on DWRCS.EXE, then select the Version Tab)?

Also, what Operating System and Service Pack level is installed on these remote machines? Are these 64-bit Operating Systems?

Also, did you recently install, or update definitions for any type of Anti-Virus or Anti-Spyware software? Because it could be that this software is mistakenly flagging some of the files within the MRC CLient Agent Service.

Microsoft's System Error: 2 basically means File Not Found. So based upon this error it appears that some of the necessary files for the MRC CLient Agent Service may have been deleted on these remote machines somehow. They also could have been mistakenly flagged and deleted by some type of Anti-Virus or Anti-Spyware software on your machine or your network as well.

Therefore, the first thing you need to do is verify that all the files are still there in the System32 folder on the remote machine (SYSWOW64 for 64-bit Operating Systems). If any files are missing, then this is the source of your issues, and you'll have to track down exactly what deleted these files on these machines.

For a listing of necessary files, you can take a look at the following KB article on our website:

How To Manually Install or Remove the Mini Remote & NT Utilities Client Agents
http://www.dameware.com/support/kb/article.aspx?ID=100000

Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com

________________________________________
Re: The Dameware mini remote service is not running on XXX.
by Jodi on Mon Jul 09, 2007 7:12 pm

Bryan,

The DWRCS.exe file is version 5.1.1.0. We are using 32 bit computers running Windows 2000 SP4 and Windows XP SP2.

One of the machines we can't access has the DWRCS.exe file but it has been renamed to DWRCS.exe.manifest. Some of the machines don't have the file at all.

Our AntiVirus software is Computer Associates and it checks for updates each day and will download them to the individual computers if needed on a daily basis.

Thanks for your help.

Jodi
________________________________________
Re: The Dameware mini remote service is not running on XXX.
by bryan on Tue Jul 10, 2007 3:30 am

Hi Jodi,

You're welcome.
One of the machines we can't access has the DWRCS.exe file but it has been renamed to DWRCS.exe.manifest
Actually, the manifest file is a valid file, so it appears your DWRCS.EXE file has been deleted, not renamed. So this is most likely due to your CA eTrust software, either within the Anti-Virus portion of the software, or within the Pest Patrol portion of the software.

Therefore, all you should have to do is define an exception for our software in either portion of the CA software (AV or Pest Patrol) so it does not delete any files for our software.

I hope this helps.

Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com

________________________________________
Re: The Dameware mini remote service is not running on XXX.
by bryan on Tue Jul 10, 2007 9:33 am

Hi again Jodi,

Here is some additional information I received from another customer on this. Many thanks go out to Zac T. for this information. Hopefully this will help you out:
Here is what worked for me…

1. Log into the E-Trust management console
2. click on the policy management tab at the top of the page
3. under the policies section, change the application dropdown to eTrust PestPatrol and the Type dropdown to Pest Exclusion
4. on the right side of the page change the tab to “Pests” and click the change button.
a. In the box type DameWare and click search.
b. Highlight “DameWare Mini Remote Control” and hit the over arrow so it moves to the Excluded Pests box on the right
c. To close click the “Set Exclude List” button at the bottom
d. Click apply in the Policy Management tab to save those settings
5. Change the tab to “Paths”
a. Click Add
b. Type “Program Files\DameWare Development\DameWare NT Utilities” in the box and click “Set Exclude Path”. (I also added “c:\windows\system32\dwrcs.exe” but I don’t know if that is necessary)
c. Click apply in the Policy Management tab to save the settings
6. the last step is to assign the group to these policies
a. click the “Assign” button
b. navigate to the organization to assign the policy to, move the group to the right and click “assign branches”

that should do it…

This is what worked for us and I hope it helps someone else out that might experience similar issues.

Zac T
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com

________________________________________
Re: The Dameware mini remote service is not running on XXX.
by Jodi on Tue Jul 10, 2007 12:11 pm

Thanks Bryan and Zac T,

We excluded the dwrcs.exe in Pest Patrol and everything is back to normal (at least on the computers we have copied the file back to). Your help has been much appreciated.

Jodi
________________________________________
Re: The Dameware mini remote service is not running on XXX.
by bryan on Wed Jul 11, 2007 6:53 pm

Hi Jodi,

You're absolutely welcome, and thanks so much for letting us know this resolved your issues.
I'm glad we were able to help out.

Best Regards,
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com

________________________________________
Re: The Dameware mini remote service is not running on XXX.
by wuliping0011 on Fri Apr 16, 2010 8:39 pm

Bryan wrote:Hello Jodi,

Exactly what version of the MRC Client Agent Service do you have installed on these remote machines (right-click on DWRCS.EXE, then select the Version Tab)?

Also, what Operating System and Service Pack level is installed on these remote machines? Are these 64-bit Operating Systems?

Also, did you recently install, or update definitions for any type of Anti-Virus or Anti-Spyware software? Because it could be that this software is mistakenly flagging some of the files within the MRC CLient Agent Service.

Microsoft's System Error: 2 basically means File Not Found. So based upon this error it appears that some of the necessary files for the MRC CLient Agent Service may have been deleted on these remote machines somehow. They also could have been mistakenly flagged and deleted by some type of Anti-Virus or Anti-Spyware software on your machine or your network as well.

Therefore, the first thing you need to do is verify that all the files are still there in the System32 folder on the remote machine (SYSWOW64 for 64-bit Operating Systems). If any files are missing, then this is the source of your issues, and you'll have to track down exactly what deleted these files on these machines.

For a listing of necessary files, you can take a look at the following KB article on our website:

How To Manually Install or Remove the Mini Remote & NT Utilities Client Agents
http://www.dameware.com/support/kb/article.aspx?ID=100000Replica chanle handbags

though that i know a lot.thanks

Hello All,

So here is my issue. We have over 300 computer that we remote into here at my job. The problem is all of our desktops have dual network connections (wireless & Wired). So when I go to remote into a computer Dame ware automatically connects to the wireless connection and it brings me to the windows login screen. The problem happens when I use the local administrator account to log into the computer. Because the local administrator account does not have Network credentials it can’t connect to the wireless and I lose connection. When I go back in and try to connect to the computer by name dame ware continues looking for that wireless address and never bothers trying to find it on its wire connection that is active. When I go into command prompt and try to ping the computer by name, again it keeps trying to ping the wireless address.  The only solution I have found is go out to the computer pull the  wired address and then connect directly to it. There has to be a way to connect to this computer after the wireless connection is lost. When I remember to I will log in with my domain credentials pull the wired IP address and then connect directly to it. The problem with that is I don't always remember and then the computer also builds me a profile on the computer that 90% of the time I don't want there. Please help we have been dealing with this issue for a long time and can’t figure it out. Is this a domain controller problem? Is there a way to refresh/ renew IP address on the domain controller? Would that even help? Thanks for every ones help in advance!

So after upgrading my M.2 240ssd to a 1TB m.2 I figured I would reinstall windows 10 and go with the latest creators version 1709. After installing Dameware Remote Support 12.05.6002 I no longer saw the MS network section expanded in the master browser with all my windows devices like it had in previous versions of windows, including previous windows 10. 1703

Well after contacting solarwinds support and working through the issue, as well as searching on google for this issue. I came across  Microsoft disabling smbv1 in windows 10 1709 by default. After I went in to contol panel, add/remove programs, and windows features turn on/off I renabled the smbv1 protocol and now the MS windows network section is once again populating.  Ive attached a screen shot of the place to check.

I have a couple Windows 10 computers that when I remote to them, as soon as I even move the mouse to do anything, the desktop locks and I have to have the user unlock it.  Then as soon as I try to do something again, it locks up the desktop again.  It's a never ending cycle.

I have uninstalled and re-installed the Dameware client on the machines a couple of times, but it still isn't working.

Any ideas?

Dameware 12.0.4 via a Centralized Server

I get this error when I use Dameware SSH client for windows(Ver: 1.0.0.0) to ssh to some of my ESXi servers. Any idea how it can be resolved?

Error Message: connection error: Could not negotiate diffie-hellman-group1-sha1

Any help appreciated..

Regards,

S.G.K !

Hi, I have a problem to activate the latest version of DameWare Remote Support. When I i try to launch the executable SolarWinds.DRS.Licensor.exe or try to click the button "Enter License" inside DameWare Remote Support software I obtain the following error: "SolarWinds.MRC.Licensor has stop working" and in my computer event viewer I have these two entries:

1. Event 1026, .NET Runtime

Applicazione: SolarWinds.DRS.Licensor.exe

Versione framework: v4.0.30319

Descrizione: il processo è stato terminato a causa di un'eccezione non gestita.

Informazioni sull'eccezione: SolarWinds.Licensing.Framework.Store.LicenseStoreException

   in SolarWinds.Licensing.Framework.Store.LicenseStoreDAL.ValidateStoreHash(Byte[])

   in SolarWinds.Licensing.Framework.Store.LicenseStoreDAL.CreateNewStore()

   in SolarWinds.Licensing.Framework.Store.LicenseStoreDAL.InitializeStore()

   in SolarWinds.Licensing.Framework.Store.LicenseStoreDAL..ctor()

   in SolarWinds.Licensing.Framework.Store.SingletonLicenseStoreFactory.get_StoreInstance()

   in SolarWinds.Licensing.Framework.LicenseManager..ctor(SolarWinds.Licensing.Framework.Interfaces.ILicenseStore, SolarWinds.Licensing.Framework.IOnlineLicenseManager)

   in SolarWinds.Licensing.Framework.LicenseManager.GetInstance()

   in SolarWinds.NTUtilities.Licensor.Program.RunLicensingWindow(Boolean, System.Collections.Generic.Dictionary`2<System.String,System.String>, Boolean)

   in SolarWinds.NTUtilities.Licensor.Program.Main(System.String[])

2. Event 1000, Application Error

Nome dell'applicazione che ha generato l'errore: SolarWinds.DRS.Licensor.exe, versione: 12.0.4.5007, timestamp: 0x58366005

Nome del modulo che ha generato l'errore: KERNELBASE.dll, versione: 10.0.14393.479, timestamp: 0x58256d37

Codice eccezione: 0xe0434352

Offset errore 0x000da832

ID processo che ha generato l'errore: 0x28c4

Ora di avvio dell'applicazione che ha generato l'errore: 0x01d2a2e463f502f7

Percorso dell'applicazione che ha generato l'errore: C:\Program Files (x86)\SolarWinds\DameWare Remote Support\SolarWinds.DRS.Licensor.exe

Percorso del modulo che ha generato l'errore: C:\WINDOWS\System32\KERNELBASE.dll

ID segnalazione: 245c6734-4e27-4431-9f06-11dc7ae1a826

Can you help me?

My computer is running Windows 10 64bit with all the updates installed.