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

The DameWare app v10.0 for DameWare DRS customers on Android is now available on the Google Play store.

DameWare Mobile lets you remotely access and troubleshoot all of the Windows computers on your network from anywhere from your Android device. DameWare Mobile brings the powerful desktop remote control features of the award-winning systems administration software, DameWare Remote Support (DRS), to your Android device.

With DameWare Mobile, you can:

• Remotely access Windows computers from your Android device
• Provide technical support to end-users from anywhere while on-call
• Share the end-user’s screen during remote troubleshooting sessions
• Easily navigate remote computers with intuitive mouse and keyboard controls
• Quickly control favorites and frequently accessed computers

DameWare Mobile includes the following features:

• Full keyboard & hot keys (Ctrl-Alt-Del, CMD Prompt, etc.)
• 256bit AES security via SSL
• Intelligent auto-scrolling
• Favorites and recently accessed computers
• Intuitive mouse actions on a mobile platform

hello support,

i need to found the old version 6.9.0.4 of dameware because want to upgrade the my current license version of this product 6.8.0.4

anyone know where this old version is available ?

very thanks for support

francesco

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.

Global domain group access
by Verrry on Thu May 15, 2008 1:59 am

Good day!
During testing DNTU v.6.7.0.9 I have collided with a following problem: When i check the option "Must be member of this global group" in Access tab, i can login into remote machine only if there is a "logon screen" (locked or not logged in). When the user on remote machine logged in locally the mistake stands out: "The remote system is not currently at the Logon Desktop. Your credentials do not allow for access at the current desktop state. Please contact your Administrator for more information"
At Access tab no other options are checked.
At General tab only next options are checked: "Allow Windows NT Challenge/Response" and "Allow Encrypted Windows Logon"
At Additional setting tab no one option is checked.
The idea was to permit use DNTU only members of the global domain group.
How can i provide access only to members of the global domain group and not only from "logon screen"?

Re: Global domain group access
by bryan on Thu May 15, 2008 2:27 pm

Hello Verrry,

This specific message "The remote system is not currently at the Logon Desktop. Your credentials do not allow for access at the current desktop state" is not related to using a Local or Global Group. It has to do with what rights these users have within the O/S security on the remote machine.

Most likely these users do not have Admin rights within the O/S security on this remote machine, and you also disabled the "Permission Required for these Account Types" setting, at the bottom of the Access Tab.

Non-Admins will always require explicit permission from the Desktop User before they can connect, but if you turn off the "Permission Required for these Account Types" setting, then any non-Admin will simply be denied access to this machine, without even prompting the Desktop user to Accept their connection.

I hope this helps.

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

Re: Global domain group access
by Verrry on Fri May 16, 2008 2:10 am

Well, thanks Bryan for your answer.
I understand, that if user wants to connect to remote host, he must be a member of the local administrator group or must ask the permission on local user to login.
But in case the security service wishes to look silently the remote desktop, there is no ways to provide them this ability without adding to local admin group.
And for what global groups are in that case used?

Re: Global domain group access
by bryan on Fri May 16, 2008 11:49 am

Hi Verrry,

When a remote machine is not at the Logon Desktop or Lock screen, in order to connect without requiring explicit permission from the Desktop User then you must have Administrator rights within the O/S security on that machine. Otherwise if you don't have Administrator rights, then you will require permission before you can connect.

The only other possible work-around (to allow non-Admins to connect without requiring explicit permission) I can think of and I don’t necessarily recommend it, would be to allow these users to connect via the Proprietary Challenge/Response authentication method instead. This method of authentication used a fictitious hard-coded UserID & Password instead of your O/S credentials.

I hope this helps.

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

Re: Global domain group access
by TheCat on Fri May 08, 2009 9:07 am

Well i guess that answers my question !

But why would i be able to configure such a setup to only find out through support (not even with a correct error message) that this configuration is useless ?

Seriously, you can make your local group setup and all, but still cannot get it to work because your not a local admin.

I dont know about you, but if i setup a "must be in this localgroup", it's obvious that's because i dont want them to be local admin group... If i do not allow an admin to have remote access with dameware, they will just logon locally and setup their account to use remote desktop (as they have the right to do so as admin...)

Right now we're working on the PCI-DSS certification, so i ended up removing all level 1 tech admin rights to our POS system, giving them appropriate "power user" rights.

Part of there jobs, require them to logon remotly to remote pc's without having to ask for permission (as they sometimes work off-hours, or on call when there is no one to answer the connection request). For the PCI-DSS requirement, i cannot give them a generic username/password. Even you folks dont recommand me to use such a settings.

Sorry... i guess i'm just a little mad that i just spent the last 2 hours trying to figure out what went wrong, thinking i had the right config setup (and according to the setting description i had) but to find out later that this is a normal behavior. You can set it up, but it will not work... wow...   

It's like telling you i build you a car, gave you the key to it, tell you to go pick me something with that car. But when you'll hit the "start engine" it wont work and it's normal because your not the car owner...

Dameware install in linux? If not, have hold map for new version for this system operation. ?

Hi.

On my DRS10 I'm not able to see/manage scheduled tasks created on Windows2008 and above systems.

W2K3 scheduled tasks can be managed.

Don't know were to look for the root cause - so any help will be appreciated.

Thanks and regards

Peter

Yes, I've seen the June 2011 discussion blaming Microsoft for this same problem but I'm wondering if anything has changed since then. Here's why.

Since I upgraded to DRS v9.0.1.247 last week, I have been unable to use it. I continually show No PDC. Yes, when I use Hyena v9.2 and open Computers, they all show.

Does this not indicate a problem within DRS? If the problem was due to NETBIOS browsing in Windows Server 2008 shouldn't both DRS and Hyena be unable to access the computer browser?

Thanks,

Phil

Our company is evaluating your product (DRS) for wide use in our environment, but due technical issues we are not able to do that.

About the issue, I want to use Microsoft App-V to virtualize DRS in our environment (because we will distribute DRS with Citrix XenApp). I was able to virtualize DRS, but licence won't follow with virtual package. When I start DRS inside virtual bubble, it says that there were no licence available (all tho I gave licence information via /ARGS during installation like your KB article 400113 states).

So where licence lays? Is it in registry or where? Have anyone done App-V virtualization to DRS earlier successfully with latest versions (DRS 10 and App-V 4.6 or 5.0)?

Thank you already for your reply.

Hello, I'm just starting with DameWare Remote Support and would appreciate any suggestions for learning all the various functions of this application. I work in an IT environment but I'm not an engineer. I run a helpdesk and do remote support for hospital with several hundred users and could really use some help to go beyond the basics.

I have an evaluation installation copy of Version 10.0.0.372 but a purchase order for a license is being processed now.

Sincerely,

Bill

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.

Hello,

We just recently upgraded from DameWare Remote Control 7 to DRS 9 with DRC 10. I'm enjoying the potential here, but some features don't work without the DRS Client Agent service running on the remote machine.

This seems to be installed OK on some of our straggler Win XP workstations, but on Win 7 workstations, trying to use features like RCmd Console doesn't work, and the automatic service activation feature doesn't work, either.

I have just seen this howto for using the batch feature to install/activate the DRS agent service, and it worked when I tested it on some of the problem Win 7 workstations.

However, we'd much prefer to be able to activate this by Group Policy, so we don't need to micromanage workstations as we deploy them.

I've searched around through the MSI Builder settings for anything to add "install DRS client agent service" or "activate" it, and done my best with Google, too, but I can't figure out if there's a way to do this. Does anyone have a way to install & activate the DRS Client Agent service by Group Policy and/or MSI? We already have a policy set up to install the Mini Remote agent with a built MSI, and that works great.

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.

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

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.

Can you lock down the settings?
by balboa on Wed Jun 20, 2007 10:09 am

Is there a way to lock down the dwrcs.ini file? For example, we use the Permission required option for end-users to be notified of a new remote control connection and then grant us access. We would want these settings to locked down and not changed by our technicians. Is this possible?

Re: Can you lock down the settings?
by bryan on Wed Jun 20, 2007 12:20 pm

Hi Balboa,

The DameWare Mini Remote Control program relies heavily on the Operating System's built-in security and Administrator is the highest authority in Windows NT/2000/XP/2003/Vista security. Therefore, the ability to "lock down" or modify any settings for the MRC Client Agent depends solely on what rights your technicians have within the Operating System's security on each individual remote machine.

However, we are also investigating what it will take to add "Server Side configuration" functionality within a future version the software. What I mean is that you would have theability to store the settings for your Client Agents on a completely separate machine, a sort of "configuration server". That way, you would have greater flexibility to lock down the settings, because even though someone may have local Admin rights on this specific machine, they may not have Admin rights on the configuration server, hence they could not make changes to theconfig. Unfortunately, I just cannot make you any promises when this functionality may be available.

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

Re: Can you lock down the settings?
by Jenson on Mon Jun 25, 2007 10:57 am

Speaking for our organization, we would be very interested in purchasing a Dameware product that would centralize the Mini Remote configuration settings, and then secure them. In fact, thelack of this functionality has become such an issue that we are now being forced to remove theDameware product from the PC's of several of our technicians who have chosen (for whatever reason) not to adhere to our standard configuration settings. This is a big deal for my organization is particular as our users insist and rely on their privacy during the workday.

We consider this issue to be the achilles heel of the Dameware Mini Remote product. The irony, of course, is that -- if Dameware wasn't as "full featured" as it is, having to centrally control theconfiguration settings would not be an issue. So kudos on one hand, and a headache on theother.

Jim Jenson
Superior Court of California

Re: Can you lock down the settings?
by bryan on Mon Jun 25, 2007 3:48 pm

Hi Jim,

Thank you very much for your feedback on this. It's very much appreciated, and we are working towards providing a centralized configuration solution for the MRC software. It's just going to take some time to develop this new functionality, because it's going to require a major rewrite ofthe existing codebase. So hopefully we will be able to offer this functionality in the next major release of the software (7.x), but again I just cannot make any promises.

However, as a possible work-around during the interim, the MRC Client Agent Service also hasthe ability to store it's settings in the Registry on the remote machine instead of theDWRCS.INI file. So perhaps this functionality may help you out:

The Mini Remote Control Client Agent Service always looks to the Registry first to see if the"Use Registry for all Settings" Registry key has been enabled. Therefore, once that setting has been enabled on the remote machine, removing & reinstalling the Service or copying a new version of the DWRCS.INI file to the remote machine will have no affect on the settings.

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

The easiest way I can think of to easily implement the "Use Registry for all Settings" Registry key across several machines is to use the new MRC Client Agent Service MSI Builder to build youa Microsoft Installer Package (MSI). The current version of our software (v6.3) also now includesthe fully completed version of the DameWare MRC Client Agent MSI builder, which allows you to build custom MSI packages (including all settings, INI or Registry) to deploy the MRC Client Agent in your environment. These MSI packages can then be sent to your clients (or even distributed via Group Policies within Corporate Environments, etc...) via any of your existing distribution methods.

I hope this information helps.

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

Re: Can you lock down the settings?
by bryan on Fri Jul 06, 2007 7:21 pm

Hi Again Everyone,

Just FYI, in addition to storing settings in the Registry, we have also provided our users with numerous additional features, such as IP-Filtering, Shared Secret key, & local / global group membership to assist with controling your environment.

I hope these additional tips help.

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

Re: Can you lock down the settings?
by bryan on Wed Jul 18, 2007 7:56 pm

Hi Everyone,

Here is another update that may help someone out. rgeorge has created an ADM template file forthe MRC Client Agent, for use in storing the MRC Client Agent Settings in the Registry.

Group Policy ADM for MRC Agent Settings
http://forums.dameware.com/viewtopic.php?f=9&t=71

Thank you rgeorge. Very much appreciated !!!

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

bryan

Re: Can you lock down the settings?
by jameslocksmith on Wed Feb 03, 2010 7:34 am

how can we lock the operating systems so that password is needed to use the computer.
Best Locksmiths Phoenix
Commercial Locksmiths Phoenix

Re: Can you lock down the settings?
by goldstar on Sat Oct 01, 2011 7:41 am

i totally agree  

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.

Damware Remote on Windows PE?
by guy on Wed Feb 24, 2010 5:01 am

Hello,
Over the last few days I have been trying to get Windows PE to run Dameware.
What I have done is install the client onto a base PC, copy off the drivers I think are required (below) copying them to PE in X:\Windows\System32\ and then started DWRCS.exe - install /-service.

DWRCK.dll
DWRCS.exe
DWRCSET.dll
DWRCSI.dll
DWRCST.exe

I can ping the PC with PE (firewall switched off on both computers) and it authenticates and it even tells me the keyboard set is in a different language but it then gets stuck on "initializing desktop, please wait"

Can anyone help me? I'm using Windows PE 3 with all packages installed WMI etc. 

Many Thanks!

Re: Damware Remote on Windows PE?
by guy on Wed Apr 07, 2010 9:04 am

Bump...
Anyone have any ideas at all?

Re: Damware Remote on Windows PE?
by dcolpitts on Sun Apr 25, 2010 8:15 am

You didn't make mention of whether you are using x86 or x64 of WinPE... As of 6.8.1.4, the Dameware client was 32 bit only, so it wouldn't work with the x64 builds of WinPE. You may want to have a look at my posting here: http://forums.dameware.com/viewtopic.php?f=9&t=469

Also, since my last posting there, I found a somewhat simplier way to do things. Use the "DameWare Mini Remote Package Builder" to build an MSI, including configuration for Proprietary Challenge/Response, then extract that resulting .MSI with 7-Zip, and then within there, you will find a Cabs.dwrcs.cab. Extract that to your WinPE's \windows\system32 folder. That contains everything you need to run the client. Lastly, you will need to add a line to run "\windows\system32\DWRCS.EXE -install" within WPEINIT.

And just to be perfectly clear, I have not tried what I suggested above yet with WinPE 3, but I believe it should work.

dcc

Re: Damware Remote on Windows PE?
by rotot on Tue Apr 27, 2010 7:47 am

mmm...thanks for info

Re: Damware Remote on Windows PE?
by guy on Tue May 11, 2010 11:31 am

Sorry I was not clear and the delay.
my WinPE is currently 32bit.
I will test the install and let you know.

Re: Damware Remote on Windows PE?
by guy on Tue May 11, 2010 11:55 am

Thanks for your help so far!

Ok so I've done the follows:
Made a Windows Vista (32-bit) MSI with proprietary challenge/responce
Build the MSI
Extracted the MSI
Extracted Cabs.dwrcs.cab
Copyed the files: DWRCK.dll,DWRCS.exe,dwrcs.ini,DWRCSET.dll ,DWRCSh32.dlx,DWRCSh64.dlx,DWRCSI.dll,DWRCST.exe to X:\Windows\System32\ (X: being the standard drive letter PE sets)
Launched "X:\windows\system32\DWRCS.EXE -install"
It connects to the point saying Initalzing Desktop. Please wait...." and thats it nothing more I have turned off the mirror driver as well.

Any Ideas

Re: Damware Remote on Windows PE?
by dcolpitts on Tue May 11, 2010 12:37 pm

Not right off... I just tested it and get the same result you do. I fear you may SOL unless someone from Dameware wishes to point us in the correct direction.

dcc

Re: Damware Remote on Windows PE?
by guy on Wed May 12, 2010 4:48 am

Thanks for that...
At least I know I'm not being stupid now if someone else can replicate the issue I have.
It's as shame as I'm sure it's something fairly simple to fix as it's -almost- working....
Anyone from Dameware - Are you reading ?

Re: Damware Remote on Windows PE?
by guy on Wed May 12, 2010 7:56 am
Just to update further.... It seems that becuase Dameware required Terminal Services this will never work....
PE is just too stripped down to allow anything like this to work 
I guess it's time to look at an open source application for PE.... 

Re: Damware Remote on Windows PE?
by dcolpitts on Wed May 12, 2010 9:38 am

I'm not sure that is the issue... My BartPE (with Sherypa's XPE based on Windows 2003 SP1) works fine with Dameware, and it does not have RDP support in it.

Re: Damware Remote on Windows PE?
by guy on Thu May 13, 2010 8:13 am

in your BartPE if you type Net Start do you have Terminal Services running?!

Re: Damware Remote on Windows PE?
by dcolpitts on Thu May 13, 2010 8:50 am

Nope. These Windows services are started:
Audio Windows
DameWare Mini Remote Control
DCOM Services
DHCP Client
EventLog
Network Connections
Network Location Awareness (NLA)
Plug and Play
Protected Storage
Remote Procedure Call (RPC)
Security Accounts Manager
TCP/IP NetBIOS Helper
Workstation

dcc

Re: Damware Remote on Windows PE?
by nhelp4k6 on Wed Jun 02, 2010 12:51 pm

Read both the WAIK documentation (msdn or technet) and the Technet forums; PE stands for Preinstallation Environment - as in completing tasks so that the *full* system can be loaded. If you are interested in a windows "slackware" style session there is a convuluted method of building XPe to CD size. Disadvantages of the XPe method are several, to begin with it's a lot of work for limited (based on your description) payback, targeting tends to be specific to machine hw config, and you need the target designer - last I checked it ran ~$1K.
Better question, why do you want to use dwmrc inside PE/slackware?

Re: Damware Remote on Windows PE?
by guy on Tue Aug 10, 2010 5:55 am

The reason for wanting Dameware in PE is for remote rebuilding/repair.
PCAnywhere has "thin host" which works but it's very expensive and not really helpful as we have Dameware in many places.
The idea is that you boot into PE (remotely) connect into the PC with Dameware start the process you need i.e. A build and off you go.

Does anyone know the location of the latest patch for Dameware Remote Support v.10. I am looking for the patch to get me from 10.0.0.372 to 10.0.0.410

We are still using the DameWare RS 9.0V where I work and I had to reload DameWare on to my system the other day.  When I loaded DMRS onto my system I received a "SolarWinds.MRC.Licensor has stoppped working" error.   When I click on the "Close the program", the entire program closes.  What is the fix for this error?

Thank you

Tawna

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.

Let the community know how impressed you are with DameWare Remote Support and earn a $25 Amazon gift card!  Simply post your review in Spread The Word with the questions answered below:

1.       What was life like before using SolarWinds? (Include what you were using and why you decided it was time for a change)
2.        Which SolarWinds product(s) saved your bacon?
3.        Did you consider other options, and why did you choose SolarWinds?
4.       How has life been since you've rolled out SolarWinds in your environment?