1. I run the utilities and then select all active directory computers.
2. Some of the computers come active and others do not.

3. Of the one that do not,

3a. I can "refresh" and the computer come back as online "blue" on my display.

3b. others I can ping and they do not come blue

3c.  Other I can not ping so I can call the user location to check on them, no big deal.

4.  The ones that do not go "blue", what packet am I not receiving from the target computer.

4a. or what packet causes the dameware computer display to turn "blue"?

or is there documentation??

thanks in advance /s/ Frank in Florida

Platform: HP ProBook 4420s, Windows 7(x64) pro SP1, DRS v10.0 installed

Use-Case: In the DRS opening window, select Tools, Search, enter text string, click "Search"

Failure: An unhandled win32 exception occurred in DNTU.exe

Event is repeatable.

------------------

Application Event Log Properties:

-----------------

Log Name:      Application

Source:        Application Error

Date:          3/19/2014 10:00:15 AM

Event ID:      1000

Task Category: (100)

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      IT-PROBOOK1.dcgc.net

Description:

Faulting application name: DNTU.exe, version: 10.0.0.372, time stamp: 0x51796d95

Faulting module name: DNTU.exe, version: 10.0.0.372, time stamp: 0x51796d95

Exception code: 0xc0000409

Fault offset: 0x00148ce9

Faulting process id: 0x2748

Faulting application start time: 0x01cf4394a6a9415a

Faulting application path: C:\Program Files (x86)\SolarWinds\DameWare Remote Support 10.0\DNTU.exe

Faulting module path: C:\Program Files (x86)\SolarWinds\DameWare Remote Support 10.0\DNTU.exe

Report Id: f0a5e089-af87-11e3-b55a-3c4a9252f274

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

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

Hello, hoping that someone might be able to point me in the right location for troubleshootting this issue.

I have found numerous posts with Win7 machines not showing active, but nothing under computers that have a comment by their name and showing offline.

Any suggestions welcome.

Thank you,

Robin

Are there any security concerns with older versions of DAMEware and this vulnerability?

Can I map a drive on the remote client from within DRS?

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?

Hello;

I've using DameWare Remote Support v9 - DRS1.

I have two IP class first one is 172.16.10.xx, it's local PC's class.

Second IP class is 192.168.1.xx, it's for servers and shop's computers. "We have 10 shops".

When I want to connect shops' pc I must to use 192.168.1.xx IP class. "But Shop's computers have 172.16.1,2,3,4...10.xx ıp adress"

When I connect to local PC I must to use 172.16.10.xx IP class.

We have forinet 100D. It is firewall and DHCP server.

Some shops has fortinet 40C "I have not any problem because central firewall and shop's modem same fortinet"

Some shops have Zyxcel ADSL modem and their IP class 172.16.10.xx

Have you got any idea about this scenario.

Thanks.

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 just want to try Dameware and it would be important that I can offer remote support on client machines that are not in our lan. So I figured that Dameware Proxy could be the right solution, but unfortunatetly I find the provided documentation is lacking some practicable examples on how to setup the firewall properly. I found some kind of documentation http://ramgesoft.com/index.php/de/hersteller/solarwinds/dameware-mini-remote/technikhowtofaq-s/497-dameware-server-11-installation-und-konfiguration in which it says, that all traffic on port 443 and 80 must be forwarded to the server which ist hosting dameware proxy. Well, our firewall itself ist listening on port 443 and 80 so I suppose it would not be advisable to redirect that traffic to the Dameware Proxy, wouldn't  it? What about ports 6132 and 6133? Must they be redirceted too?

Right now all Dameware Servers are running locally on one single machine, just for testing purposses.. There is on Firewall with multiple WAN, one of which should accept incomming traffic which should then be redirected to the Proxy.

Could anyone give me a few hints on how to achieve my goal of a working Proxy?

regards, heinzelrumpel

I went to the DRS properties, Remote Control tab, Settings button (lower right corner), General tab, entered my logon settings and hit save password.  It shows there again when I go back in, but none of the machines have the information showing when I try to log on, so I have to enter my credentials every time. 

Good day!

Help please, about a month drip internet in search of an answer to your question , really hope you can help me .

We have over 10k machine which is still running services and it so happened that the settings apply DWRCS DWRCS.ini (reg) those that were set when you first install the service.

And we have each their gadgets ... Please tell me how to update the file when connecting to a remote machine without removing the service and re- install it.

Ready even in monetary terms from thank brain is melting ...

Thank you.

Can I map a drive on the remote client from within DRS?

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.

MRC Properties?
by KarbonKopy on Thu Jan 13, 2011 4:27 pm

I know in MRC in 6.x you should set the defaults for the MRC agents that would automatically roll out to them during a install etc. It was under install options on MRC's default host properties. Has this been moved somewhere? I need to be able to change those values.
________________________________________
Re: MRC Properties?
by ukwalnuts on Fri Jan 14, 2011 11:34 am

I'm also looking for this. Trying to disable 'Notify Dialog' but can't find option anywhere.

I've emailed support but still waiting on reply.
ukwalnuts
________________________________________
Re: MRC Properties?
by Marty on Fri Jan 14, 2011 4:02 pm

Version 7.x no longer uses a DWRCS.INI file for the settings of the service and therefore the option to copy that file over to the remote machine has been removed.

The settings for the MRC client agent service can be customized using the new and improved MSI Builder.

Thanks,
Marty Bonvillain
Support Staff
DameWare Development, LLC.
http://www.dameware.com

________________________________________
Re: MRC Properties?
by ukwalnuts on Sat Jan 15, 2011 5:24 am

Hi Marty,

Thanks for help so far.

I've looked at MSI builder but still can't see how to apply changes I want to my existing desktops.

When I connect to desktops which has version 6 agent installed Dameware asks me if I want to upgrade. If I click yes it upgrades agent to v7 but there isn't any option to choose which msi installer it should use or profile.

If I go to File > Install Service again I can't choose which msi or profile Dameware should use.

Other than manually going to each desktop and installing customized msi. How do I get agents upgraded on my desktops with settings I want?

Thanks
________________________________________
Re: MRC Properties?
by KarbonKopy on Sun Jan 16, 2011 11:37 am

I am in the same boat Marty, I want the default install to be able to be set before I roll out the client. At the moment I'd have to either build a MSI and deploy it or customize after the fact on the client itself.
________________________________________
Re: MRC Properties?
by bryan on Sun Jan 16, 2011 7:26 pm

Hey KarbonKopy,

There is two ways you can do it.

1. Build an MSI Package with all your custom settings and then distribue this MSI package to all your users via any of your existing distribution methods. The MRC Client Agent Service will be installed using the custom settings you specified.

2. Install the MRC Client Agent Service on your own machine. Then right-click on the MRC SysTray icon and select the Settings context menu. Once you've made all your settings changes, you can then export the following Registry key for the v7 Client Agent Service into a .REG file:

[HKEY_LOCAL_MACHINE\SOFTWARE\DameWare Development\Mini Remote Control Service]

Once you have your .REG file, you can then distribute this .REG file to all your remote machines prior to installing the MRC Client Agent Service on those machines. By importing the .REG prior to installing the Service, when the Service is eventually installed it will automatically start using these custom settings (not default settings).

I hope this helps.

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

________________________________________
Re: MRC Properties?
by bryan on Sun Jan 16, 2011 9:36 pm

**Update: Our developer is currently working on a function that will allow you to copy/merge settings from a DWRCS.reg file during Client Agent Install/upgrade. This functionality should be available shortly, and we will notify everyone when it's available.

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

________________________________________
Re: MRC Properties?
by Marty on Mon Jan 17, 2011 6:07 pm

We have just released an update, 7.0.1.0, that includes an option to push out a DWRCS.reg file to the remote machine with your preconfigured settings.

You will need to install the MRC client agent service on your local machine, configure it to your specifications, then export the [HKEY_LOCAL_MACHINE\SOFTWARE\DameWare Development\Mini Remote Control Service] registry key and name it DWRCS.reg. Place that file in your DameWare installation directory and when you push out the service, you should have the option to “Include Configuration File DWRCS.reg.”

Thanks
Marty Bonvillain
Support Staff
DameWare Development, LLC.
http://www.dameware.com

________________________________________
Re: MRC Properties?
by KarbonKopy on Tue Jan 18, 2011 11:03 am

I can confirm this works, thank you! If I had any suggestion, it would be a easier way to include the settings much like v6 did.
________________________________________
Re: MRC Properties?
by ukwalnuts on Tue Jan 18, 2011 1:47 pm

KarbonKopy wrote:I can confirm this works, thank you! If I had any suggestion, it would be a easier way to include the settings much like v6 did.
100% Agree. Thanks for sorting this out so quickly.

Re: MRC Properties?
by Maverick on Tue Jan 18, 2011 1:51 pm

Ditto!

Mav
________________________________________
Re: MRC Properties?
by Roger on Wed Jan 19, 2011 4:19 pm

Just curious, but now that Dameware is 64 and 32 bit, does this reg import account for both locations of the keys since 64bit stores in a different location when a reg import is executed from a 32bit process? It may need to write to both unless you use the registry api flags to make both 32 and 64 bit read/write from/to the same location. May only apply to a 32bit MRC updating the reg of a 64bit machine.
________________________________________
Re: MRC Properties?
by Marty on Wed Jan 19, 2011 4:50 pm

Hi Roger,

The registry key for both 32-bit and 64-bit are in the same location. Do not use any keys from the “HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node” on 64-bit machines. Always use “HKEY_LOCAL_MACHINE\SOFTWARE\DameWare Development\Mini Remote Control Service” on any machine. Lastly, don’t use a 32-bit application for registry import or export on a 64-bit machine.

I hope this information helps.

Marty Bonvillain
Support Staff
DameWare Development, LLC.
http://www.dameware.com

________________________________________
Re: MRC Properties?
by Roger on Wed Jan 19, 2011 5:05 pm

How does the 32bit version of MRC import the .reg file on a remote 64bit machine? Does it pass the file to the 64bit app and let it import it?
________________________________________
Re: MRC Properties?
by Marty on Wed Jan 19, 2011 7:31 pm

Hi Roger,

Even when you are using the 32-bit application, the service on a 64-bit machine will be the 64-bit service and the service is what imports into the Registry.

Thanks,
Marty Bonvillain
Support Staff
DameWare Development, LLC.
http://www.dameware.com

________________________________________
Re: MRC Properties?
by arasg on Thu Jan 20, 2011 9:39 am

KarbonKopy wrote:it would be a easier way to include the settings much like v6 did.
I agree. I have been using this for many years and it was much easier the old way.

Please add this back.
________________________________________
Re: MRC Properties?
by zack1010 on Thu Jan 20, 2011 11:27 am

Hey DameWare Guys,

Thanks for making this DWRCS.Reg enhancement. This new functionality is so much better than the way it was in older versions. I don't know about the rest of you here on the forum, but so many times I pushed out config files to my agents, only to find out later someone had enabled the setting to use the Registry instead, which meant my INI file was being ignored anyway. Now the settings are only in one place (the Registry) instead of multiple places (INI file or Registry), so no more confusion.

Zack

________________________________________
Re: MRC Properties?
by MTheile on Tue Jan 25, 2011 9:21 am

Hi,

is there a way to set the option to include Configuration File DWRCS.reg as a default setting?
Our supporters often forget to set this option, it was easier for us to deactivate it, when we don´t need it.

Thanks

________________________________________
Re: MRC Properties?
by Ragil on Wed Jan 26, 2011 10:48 am

MTheile wrote:

Hi,

is there a way to set the option to include Configuration File DWRCS.reg as a default setting?
Our supporters often forget to set this option, it was easier for us to deactivate it, when we don´t need it.

Thanks

Same here!!! This option must be added...

Thanks
________________________________________
Re: MRC Properties?
by dustino on Wed Jan 26, 2011 6:24 pm

We just got 7.0.3.0 installed and have been trying to get all the desired settings set in the MRC. However, everytime we make our changes to the settings, we click OK and all the settings get reset back to default.

Is this normal behavior? We are trying to follow the procedure outlined by Marty to push our MRC settings to other computers via the .reg file.

Thanks in advance.

Re: MRC Properties?
by bryan on Wed Jan 26, 2011 11:04 pm

Hi dustino,

Thanks for your feedback.

Just to make sure we understand you correctly, you've already installed the MRC Client Agent Service on this machine, and then you right-click on the MRC Tray Icon and select Settings. You then configure all your custom settings, however, after selecting OK all the settings revert back to default. Is this correct ?

By any chance, is this machine running XP or 2003 Server ? If so, after clicking on the MRC Tray Icon's Settings context menu, you should have been presented with a Run As dialog asking if you want to "Run this program with Restricted Access". If you do not clear this checkbox before selecting OK then any changes you make will not be saved.

Your feedback is appreciated.

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

________________________________________
Re: MRC Properties?
by ukwalnuts on Thu Jan 27, 2011 8:27 am

I've come across this issue.

When I right-click on the MRC Tray Icon and select Settings I get window pop up saying "Which user account do you want to use to run this program"

For some reason domain administrator account doesn't work but if I enter local administrator account settings are saved correctly.

This is happening when I'm logged in as domain administrator on XP or Server 2003 machine.
________________________________________
Re: MRC Properties?
by dustino on Thu Jan 27, 2011 1:17 pm

Bryan wrote:

Hi dustino,

Thanks for your feedback.

Just to make sure we understand you correctly, you've already installed the MRC Client Agent Service on this machine, and then you right-click on the MRC Tray Icon and select Settings. You then configure all your custom settings, however, after selecting OK all the settings revert back to default. Is this correct ?

By any chance, is this machine running XP or 2003 Server ? If so, after clicking on the MRC Tray Icon's Settings context menu, you should have been presented with a Run As dialog asking if you want to "Run this program with Restricted Access". If you do not clear this checkbox before selecting OK then any changes you make will not be saved.

Your feedback is appreciated.

The check box was the problem Bryan. We had not unchecked the "Protect my computer and data from unauthorized program activity". Once we unchecked this and made our desired changes, the MRC popped up a notification that "The client agent is in the process of configuring". Then it retained the settings we changed.

FYI we are running Windows XP.

Thanks, Bryan.
________________________________________
Re: MRC Properties?
by bryan on Thu Jan 27, 2011 5:54 pm

You're most welcome, and thank you very much for your feedback. I'm glad we were able to help.

Best Regards,
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
________________________________________
Re: MRC Properties?
by jpflepsen on Fri Jan 28, 2011 11:24 am

I have to agree with some of the previous posters - this having to save a .REG file after making settings changes on the host is a much more time consuming & convoluted way of deploying settings to clients. Especially when you want the client settings to be different from how you want your host to behave. I'd sure like to see the return of the v6 way of pushing these settings to clients.
jpflepsen
________________________________________
Re: MRC Properties?
by bryan on Mon Jan 31, 2011 5:41 pm

Hi Everyone,

Just FYI, we're looking into adding some new functionality in the next release of the software, which will be v7.1.0.0, where you can optionally configure and save the DWRCS.Reg file via a GUI during service installation. I will update everyone here as more information becomes available.

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

________________________________________
Re: MRC Properties?
by KarbonKopy on Wed Feb 02, 2011 1:47 pm

Awesome to hear Bryan!
________________________________________
Re: MRC Properties?
by KarbonKopy on Thu Feb 03, 2011 5:38 pm

Just saw the 7.1.0 install...and can confirm you can now set the options in MRC. Thanks! If I may add one more suggestion it would be the option to set a default...either include or exclude the .reg file.
________________________________________
Re: MRC Properties?
by Ragil on Fri Feb 04, 2011 1:33 pm

KarbonKopy wrote:

Just saw the 7.1.0 install...and can confirm you can now set the options in MRC. Thanks! If I may add one more suggestion it would be the option to set a default...either include or exclude the .reg file.

I want it too!!!

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.

Disable automatic saved hosts
by boucherjeanfra on Fri Jan 21, 2011 2:06 pm

Hi,

In the version 7 of Mini-Control, is it possible to disable the "automatic" save to a new host ?
I verified twice in the settings but found nothing.

Thanks for your help,

Cheers,

Re: Disable automatic saved hosts
by bryan on Mon Jan 24, 2011 4:01 pm

Hi boucherjeanfra,

Anytime you start typing while the Host field is selected the New Host dialog will be displayed, to allow you to create a new Saved Host entry. If you're trying to modify an existing entry, select the desired entry in the Saved Host List, then right-click on this entry and select Rename Host. This will allow you to modify the existing entry without creating a new one.

I hope this helps.

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

Re: Disable automatic saved hosts
by Siggi on Wed Jan 26, 2011 5:18 am

Hello there,

I just installed the MRC7 and have the same problem as boucherjeanfra. I also want to get the "automatic-saving-a-new-host" feature disabled because in the past I always connected to a remote host by only typing in the adress. The hosts don't need to be saved. It's faster for me than selecting the host from a list.

Hope you got what I mean.

Re: Disable automatic saved hosts
by williaa on Wed Jan 26, 2011 4:01 pm

@Bryan, what we're wanting to know is if there's any way to disable the New Host dialog from displaying anytime you start typing while the host field is selected. It's more convenient for this to not happen when using the Mini Remote Control.

Re: Disable automatic saved hosts
by bryan on Wed Jan 26, 2011 5:36 pm

Thanks everyone for your feedback.

Presently there is no way to turn this functionality off. MRC v7 will automatically create a new Host Entry when you start typing, whereas v6 would create a (Temporary) entry. (Temporary) entries no longer exist in v7.

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

Re: Disable automatic saved hosts
by Siggi on Thu Jan 27, 2011 3:12 am

Perhaps, it could be an idea to add a "Quick connect" adressbar to the next version of MRC for those who want to connect in that specific way?

Re: Disable automatic saved hosts
by bryan on Mon Jan 31, 2011 5:35 pm

Hi Everyone,

Just FYI, we're looking into adding some new functionality in the next release of the software, which will be 7.1.0.0, where you can turn off the Host Entry "Auto Save" feature. I will udpdate everyone as more information becomes available.

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

Re: Disable automatic saved hosts
by KCarney on Tue Feb 08, 2011 2:14 pm

So has it been added?

Re: Disable automatic saved hosts
by bryan on Tue Feb 08, 2011 3:17 pm

The new "Disable Auto Save" functionality was implemented in v7.1.0.0. On the MRC Remote Connect dialog (not from the main menu) first select the Edit menu, then enable the "DisableAuto Save" setting. This will instruct the software not to display the "new host" dialog when you modify the HostName/IP-Address of an existing Host Entry. Instead, a new temporary entry will be created, designated by a red circle with an x in the icon's lower right corner. If you close the MRC Remote Connect dialog, or simply Connect then Disconnect, this temporary entry will now be gone.

I hope this helps.

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

Re: Disable automatic saved hosts
by KCarney on Tue Feb 08, 2011 4:57 pm

When "Disable Auto Save" option is enabled "reconnect" no longer functions properly, it now displays the last computer I connected to when the option was disabled. Please fix this

Re: Disable automatic saved hosts
by bryan on Tue Feb 08, 2011 5:35 pm

This is exactly how the reconnect option is designed to function, and this is the same way it worked in v6.x as well. By default only Saved Host entries are added to the Reconnect list, because we only have settings stored for the entries in your Saved Host list. There are no settings stored for any type of "temporary" entries, therefore, they are not added to the Reconnect list. If you need custom settings stored for any remote machine, then you must save it to your Saved Host List.

With that being said, there is a setting on the Local Global Options dialog called "Add only savedhost entries to Reconnect list". If you choose to disable this setting, then any machine you connect to will be added to the Reconnect list. However, since no custom settings exist for any of these non-saved machines, you may not be able to successfully reconnect.

If all of these non-saved machines use the same default credentials & settings, then you should be able to add these default credentials and settings to the Default Host Properties dialog. These Default Host settings are used when you create a new Host Entry. However, if you highlight an existing Saved Host Entry and then change the HostName or Ip-Address, then the settings from this Original Host Entry (not default) are used to create your new Temporary entry.

I hope this helps.

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

Re: Disable automatic saved hosts
by KCarney on Wed Feb 09, 2011 2:39 pm

and this is the same way it worked in v6.x as well.

No, it didn't. It randomly picked a host that was connected to by any number of open DMRC windows, it was a little annoying at times but worked. This new version seems a lot cleaner

If you need custom settings stored for any remote machine, then you must save it to yourSaved Host List.

That makes sense.

With that being said, there is a setting on the Local Global Options dialog called "Add onlysaved host entries to Reconnect list". If you choose to disable this setting, then any machine you connect to will be added to the Reconnect list. However, since no custom settings exist for any of these non-saved machines, you may not be able to successfully reconnect.

That is exactly how it worked in 6x, I will give that a try. Thanks for explaining! 

Re: Disable automatic saved hosts
by KCarney on Mon Feb 14, 2011 1:24 pm

Works great now in 7.2.0.0, thank you!

Re: Disable automatic saved hosts
by KCarney on Fri Feb 18, 2011 11:10 am

Correction, this works *sometimes*. After a week of using it disconnecting from a host and attempting to reconnect results in blanked out connection options. I have to enter the previous host manually to reconnect.

Re: Disable automatic saved hosts
by bryan on Fri Feb 18, 2011 3:02 pm

Just because you connected the first time doesn't mean you can immediately Reconnect to any machine when it's not saved in the Saved Host List. This is exactly why we did away with this feature initially for version 7.x, for all machines not saved to the Saved Host List.

When a machine is saved in the Saved Host List, we have all the settings necessary to Reconnect (UserID, Password, Port, etc...). However, when a machine is not saved to the SavedHost List, there are no settings we can use to Reconnect. Once you click on Disconnect, all those settings are now gone. We no longer have any settings for this machine. Therefore, by design, they will be blank settings exactly as you mentioned previously when you try to Reconnect, and the connection will fail.

The only way "Reconnecting" to a machine that's not explicitly saved to the Saved Host List will ever work would be if you enter the correct settings (UserID, PW, Port, etc..) under the Default Host Properties dialog (i.e. View / Default Host Properties from the main menu). Just keep in mind that these default settings would be the same settings used for all "Reconnect" attempts when a machine is not explicitly saved to the Saved Host List.

I hope this helps.

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

Re: Disable automatic saved hosts
by KCarney on Mon Feb 21, 2011 9:18 am

When a machine is saved in the Saved Host List, we have all the settings necessary to Reconnect (UserID, Password, Port, etc...). However, when a machine is not saved to theSaved Host List, there are no settings we can use to Reconnect. Once you click on Disconnect, all those settings are now gone. We no longer have any settings for this machine. Therefore, by design, they will be blank settings exactly as you mentioned previously when you try to Reconnect, and the connection will fail.

I would agree with you, however, I have set my default settings to "NT Challenge/Response" and "Use Current Logon Credentials" selected. *Sometimes* when I launch DMRC all settings are blank and "Encrypted Windows Logon" is selected with no machine name as host. So as you can see I don't need any saved settings, I don't want hosts automatically saved, and this should be working but is not.

Re: Disable automatic saved hosts
by bryan on Mon Feb 21, 2011 2:04 pm

Based upon the screen shots you sent to support, the software is working exatly as it should.

In your screen shot there is no Host Entry selected, instead, the Root folder (i.e. Saved Host List) was selected. When MRC starts up it will try to locate and highlight the last entry you connected to. However, when that entry cannot be found (i.e. it was not saved), then the root folder is selected. Therefore, by design, since a folder is currently selected and not a host entry, MRC will not go through all the work of pulling the default host properties just to populate the RC dialog. So the fact that you see Encrypted Windows Logon shown in the RC dialog while a folder is selected when you’ve selected NT Challenge/Response as default doesn’t mean there is an issue with the software.

Also, the fact that you say this only happens *sometimes* means that these other times when this does not happen, there must be an existing host entry already with this same name. So when you click on reconnect, those settings from the existing entry will be used and not default settings.

I hope this helps.

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

Re: Disable automatic saved hosts
by TrafficTech on Fri Mar 04, 2011 11:09 am

I have a few comments to make on the Saved Host List of version 7.3.0. I currently have my settings to "Disable Auto Save" and I have disabled the "Add Only Saved Host Entries to Reconnect List". I seem to have found a little bug in the process.

1) If I enter a new temporary entry, it indeed populates in the reconnect list. I can go back and connect to another temporary address and that also goes into the reconnect list. I notice the reconnect list has only unique entries (If I reconnect to a previous entry using the Connect button and not the reconnect button. However, if I use the reconnect drop-down, the entries are no longer unique. Furthermore, when I close and reopen the application, my reconnect entries have vanished, the button is grayed out. This happens every time I use the reconnect button.

2) If I leave the Auto Save feature on, I would like to have an option to have unique entries in the Host List. The list can get long and I don't necessarily want to go through it every time, but I do not want to duplicate my entries either

3) I can understand that if I select a Saved Host entry and decide afterwards I want to connect to a temporary host instead, the Alias from the previous entry is still shown. What I don't like is that if I inadvertently left the alias there and connected, the entry listed in the reconnect drop down shows as ALIAS (HOST). I am more interested in the host and don't really want to see the alias entry (especially since I mistakenly left it in during the temporary entry previously).

David M
Systems Admin
Traffic Tech

Re: Disable automatic saved hosts
by bryan on Thu Mar 10, 2011 11:10 am

Hi David,

Thanks very much for all the info you provided. This should be now be resolved in v7.4.

Your feedback is appreciated.

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.

Granting remote control rights to non-admins
by abentley on Wed Sep 09, 2009 4:38 am

Try as I might, I have been unable to get non-admin users to be able to remote controlcomputers. I am running Windows Vista Enterprise SP2 and MRC 6.8.1.4. I have read a lot of posts on the subject and understand that the default dwrcs.ini settings need to be altered during MSI creation so that non-admins will be able to connect (after permission is granted) and i'm pretty sure I've got the settings correct, but only users with admin rights are currently able to connect successfully.

What I want is for members of a specific domain global group to be able to connect to any MRC client. All of the members of this group are at the very least members of the local 'Users' group on each computer (becuase they are members of Domain Users which is in-turn a member of the local Users group). Some members of the domain group have local admin rights on computers, and it is only these accounts that are able to authenticate and connect.

I require all connection attempts to prompt for permission when someone is logged on to the target computer, and for any connection to a locked or un-logged-on computer to be automatically accepted.

I have tried both Encrypted Windows Logon and Windows NT Challenge Response authentication methods without success. I'm pulling my hair out now as I really need some users who can't have local admin rights the ability to remote control with MRC.  

Here is my INI file (I am not using registry settings), can anyone spot anything wrong with it?
CODE: SELECT ALL
[Settings]
Port=6129
Adgang NTLM=Yes
Adgang 1=
Adgang 2=
Adgang 3=0
Notify On New Connection=Yes
Notify On Disconnection=No
No Notify Sound=No
Notify On New Connection Timeout Value=30
Notify Dialog Caption=Remote Control
Notify Dialog Text 1=Remote Control Notification
Notify Dialog Text 2 Remote Control=The following user has connected viaremote control.
Permission Required=Yes
Center Permission Dialog=No
Permission Dialog Set Focus On Decline Button=No
Show SysTray Icon=Yes
Enable User Option Menu=No
Option Notify On New Connection=Yes
Option Notify On New Connection Dialog Timeout=Yes
Option On Disconnect Logoff Desktop=Yes
Option On Disconnect Logoff Desktop Force Applications Close=Yes
Option On Disconnect Lock Workstation=Yes
Option Logon At Logon Desktop Only=Yes
Option Logon At Logon Desktop Only Timeout=Yes
Option Enable File Transfer=Yes
Option Enable Chat=Yes
Option Enable Chat Allow Anyone To Initiate=Yes
Option Permission Required=Yes
Option Enable Add Client Connection Menu=Yes
Option Enable DisConnection Menu=Yes
Option Enable Email Notification=Yes
Option Enable Email Notification Change Email Address=Yes
Permission Required for non Admin=Yes
Permission Required for non Admin Disconnect If At Logon Desktop=No
Permission Required for non Admin Force View Only=No
On Disconnect Logoff Desktop=No
Force Applications Close=No
On Disconnect Lock Workstation=No
Logon At Logon Desktop Only=No
Logon At Logon Desktop Only Timeout=Yes
Logon At Logon Desktop Only Timeout Value=20
Enable Add Client Connection Menu=Yes
Enable Disconnection Menu=Yes
Enable Settings Menu=No
Absolute Timeout=0
Requires Explicit Remote Admin Rights=No
Allow Only Administrators To Connect=No
Requires Logon Locally Privilege=No
Must Be Member Of This Local Group=No
Local Group Name=
Must Be Member Of This Global Group=Yes
Global Group Name=DameWare Desktop Remote Control Access
Enable Email Notification=No
Email Notification Address=
Email Notification Server=
Disable Host Lookup=Yes
Socket Logon Timeout=90000
Authentication Type=2
Must Have Logon Locally Rights with Windows Logon=No
SFT: Enable Simple File Transfer=Yes
SFT: Append Host Name=No
SFT: Upload Folder=%SYSTEMROOT%\DWRCS UploadsSFT: User Response Time Out=6000
Disable Version Downgrade=No
Global Group Machine 0=[IP address of Domain Controller 1]
Global Group Machine 1=[IP address of Domain Controller 2]
Global Group Machine 2=[IP address of Domain Controller 3]
Global Group Machine 3=
Global Group Machine 4=
Global Group Machine 5=
Allow All Administrators To Have Control=Yes
Upgrade Information=
Downgrade Information=
Max Access Log Size=10240000
Force Encrypt Data=No
Force Encrypt Images=No
Force Encrypt Files=No
Configuration Version=5.5
[Proxy]
Enable Proxy=No
Require Shared Secret=No
Disable Remote Control=No
[IP Filter]
Enable Filter For Remote Control=No
Enable Filter For Proxy=No
Access Granted=Yes

Questions: Can 'Global Group Name' contain spaces and does it need to be prefixed with 'DOMAIN\' ?

Many thanks in advance

Re: Granting remote control rights to non-admins
by switbro on Wed Sep 09, 2009 6:21 pm

I am having a similiar issue - I have 45 domain controllers and have a group assigned to "Account Operators" so they can remotely access these machines with DMRC. They can access 44 of the 45 but they seem to be in view only mode on the 45th. They cannot connect even when the server is at the login window. The dwrcs.ini file looks the same as all the others, Is there a particular setting I should be looking for that would cause this behavior?

Thanks
Scott

Re: Granting remote control rights to non-admins
by abentley on Tue Sep 15, 2009 2:07 am

Hi, is anyone able to advise on this issue? Thanks

Re: Granting remote control rights to non-admins
by bryan on Fri Sep 18, 2009 1:24 pm

Exactly what error message are you receiving when you try to connect? Because it looks like everything is setup correctly. Spaces in the Global Group name should also be fine (i.e. Domain Admins).

Permission Required=Yes
- all users, even Admins, will require permission from the desktop user
- unless remote machine is at Logon Desktop or Lock Screen

Permission Required for non Admin=Yes
Permission Required for non Admin Disconnect If At Logon Desktop=No
Permission Required for non Admin Force View Only=No

- non-Admins will require permission from the desktop user, unless @ Logon Desktop or Lock Scr.

Please also look for DWMRCS entries in the Operating System's Application Event Log on theremote machine. Copy & paste the entire text from each of these entries back to our support team so they can review them. There should be at least two entries for each failed login attempt.

Once we have this information we whould be able to assist you further.

I hope this helps.

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

Re: Granting remote control rights to non-admins
by abentley on Mon Sep 21, 2009 3:14 am

Thanks for the response Bryan. When any non-local admin attempts to connect they get this error immediately:

Authentication failed:
System Error: 5
System Message: Access denied

Event log entries:
CODE: SELECT ALL
Error:
DameWare Mini Remote Control
System Error: -2146893044
Failed to establish a security context. OS Error Code: [SEC_E_LOGON_DENIED] The logon attempt failed. : (srv)

CODE: SELECT ALL
Error: Failed Authentication.
Using Windows NT Challenge/Response.

  
Date: 09/21/2009 09:02:59  
Computer Name: [computername]  
User ID: [logged-in username]  
Logon As ID: [login credentials username - not the same as username above]  
Domain:   
Desktop User ID:   
Desktop Name:   
System Settings Using: INI-File  
Desktop State: Unknown  
Permission Required: Yes  
Access Approved By: N/A  
Access Declined By: N/A  
Access Request Timeout: N/A  
Access Request Disconnected: N/A  
OS Product ID: [product id]  
OS Registered Owner: [registered owner]  
OS Registered Organization: [registered org]  
Host Name from Peer: [computername]  
IP Address(es) from Peer: [ip address]  
Peer Host Name:   
Peer IP Address: [ip address]  
Protocol Version - DWRCC.EXE: 6.800000-0.000010  
Protocol Version - DWRCS.EXE: 6.800000-0.000010  
Product Version - DWRCS.EXE: 6.8.1.4  
Product Version - DWRCC.EXE: 6.8.1.4  
Proxy Host Used: No  
Proxy Host:   
Proxy Destination Host:   
Proxy Destination Port: 0   
Proxy Callback Port: N/A   
Authentication Type: NT Challenge/Response  
Last Error Code: -2146893044  
Last Error Code (WSA): 0  
Host Port Number: 6129   
Host IP Address: [ip address]   
Host Name: [computer name]   
Absolute timeout setting: 0 minutes  
Connect/Logon timeout setting: 90000 milliseconds  
AccessCheck:   
Registered: No  
WTS Session: No  
Used RSA Public-Key Key Exchange (1024 bit keys).  
Encryption IDs: 26128 (24576,1536,16) [256].  
Hashing IDs: 26128 (24576,1536,16).  
Used Shared Secret: No  
Registration: [registration code]

Re: Granting remote control rights to non-admins
by mbernards on Tue Sep 29, 2009 4:32 am

We have added all global groups in our forests and domains with one name: UG_DWMRC
Universal groups does not seem to work here.

In those groups reside all support personal.

A tip: don't get fooled by the PDC/DC list requirement here, better use the domain names. (6 max)
let DNS find the nearest DC instead of hardwiring nodes here.
We recenly retired a bunch of old DC's and this nuked the authentication process at the clients
You have to force new settings by removing the current remote control agent and installing the new builded MSI file
The repair option does not restart the service for unknown reasons
(I am local admin, but event log says cannot find file)

I also enabled a central log server ( needs a active DWMRCS service )

Domain and enterprise administrators are also allowed to take over machines.

Works great here.

Re: Granting remote control rights to non-admins
by abentley on Wed Oct 07, 2009 5:04 am

Hi, any update on this issue from DameWare support? Thanks

Re: Granting remote control rights to non-admins
by bryan on Fri Oct 09, 2009 9:54 am

See this post for additional information:
http://forums.dameware.com/viewtopic.php?f=8&t=1189

Do those non-Admin credentials have sufficient right to login at the console of this remotemachine? In other words, can these non-Admins physically walk up to this machine and sit down at the console and use their credentials to login? If not, then they won't be able to use those credentials to connect via our software either.

SEC_E_xxxxx errors are produced by Microsoft's SSPI (Security Support Provider) interface within the O/S, which is only used when using NT Challenge/Response authentication. Our software simply passes the necessary information to Microsoft's SSPI interface and the O/S takes over and performs all authentication.

This specific SSPI Error, "Failed to establishing a security context" - SEC_E_LOGON_DENIED, implies there may be some setting within your O/S that's preventing "LAN Manager Authentication" on this machine, possibly a Policy setting (i.e. "Send NTLMv2 response only\refuse LM & NTLM" , etc.).

Therefore, you might want to try using the Encrypted Windows Logon authentication method instead. Using the Encrypted Windows Logon authentication method may resolve your issue, or it may actually generate another error message which may point us in the right direction with regard to this issue. However, presently this behavior appears to be related to some type of O/S configuration issue.

Here are some other things you can check:

- For machines in a Domain, make sure the Net Logon Service is running.
- Make sure the credentials you're using to connect do not have an expired password.
- Check your LanManager Authentication Level policy.
- Try using the Encrypted Windows Logon authentication method instead.

I hope this helps.

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

Re: Granting remote control rights to non-admins
by abentley on Mon Oct 12, 2009 3:03 am

Thanks Bryan,

I did read the article above and have tried Encrypted Windows Logon before. I have just tried again on several computers and still no joy...

1. The NETLOGON server is running. Confirmed on all computers. All other domain-based authenticaion would fail without this service, so it's definitely running OK.

2. The credentials I am testing with are definitely OK. The account is not expired, locked out and does not require a password change. I can logon interactively at the console of any computer with this test account.

3. LAN Manager Authentication Level is configured using Group Policy to: Send LM & NTLM - use NTLMv2 session security if negotiated. I have also set this to 'Not Configured' so that the default Vista setting (Undefined on workstations) takes effect, this does not help either.

4. Both Windows NT Challenge Response and Encrypted Windows Logon consistently fail for all users who do not have local admin rights. I changed the 'Authentication Type' in the ini file (restarting DameWare service after each change) to 2,4 and 6 to test the different scenarios.

Here's the event log of a failed Encrypted Windows Logon attempt:

Error: Failed Authentication.
Using Encrypted Windows Logon.
CODE: SELECT ALL
Error:
DameWare Mini Remote Control
System Error: 1326
Failed to Logon User (srv)

CODE: SELECT ALL
Date: 10/12/2009 08:46:45  
Computer Name: [computername]  
User ID: [username]  
Logon As ID: [username]  
Domain:   
Desktop User ID:   
Desktop Name:   
System Settings Using: INI-File  
Desktop State: Unknown  
Permission Required: Yes  
Access Approved By: N/A  
Access Declined By: N/A  
Access Request Timeout: N/A  
Access Request Disconnected: N/A  
OS Product ID: 89579-236-0200203-71402  
OS Registered Owner: [owner]  
OS Registered Organization: [org]  
Host Name from Peer: [client computer name]  
IP Address(es) from Peer: [client ip address]  
Peer Host Name:   
Peer IP Address: [client ip address]  
Protocol Version - DWRCC.EXE: 6.800000-0.000010  
Protocol Version - DWRCS.EXE: 6.800000-0.000010  
Product Version - DWRCS.EXE: 6.8.1.4  
Product Version - DWRCC.EXE: 6.8.1.4  
Proxy Host Used: No  
Proxy Host:   
Proxy Destination Host:   
Proxy Destination Port: 0   
Proxy Callback Port: N/A   
Authentication Type: Encrypted Windows Logon  
Last Error Code: 1326  
Last Error Code (WSA): 0  
Host Port Number: 6129   
Host IP Address: [host ip address]   
Host Name: [host computer name]   
Absolute timeout setting: 0 minutes  
Connect/Logon timeout setting: 90000 milliseconds  
AccessCheck:   
Registered: No  
WTS Session: No  
Used RSA Public-Key Key Exchange (1024 bit keys).  
Encryption IDs: 26128 (24576,1536,16) [256].  
Hashing IDs: 26128 (24576,1536,16).  
Used Shared Secret: No  
Registration: [reg code]

Two issues - I had DRS installed on my Windows 7 Pro workstation, but was experiencing some unexplained weirdness, so thought that I'd remove and reinstall just to rule that out.  I can't get it reinstalled - keep getting the message   "There is a problem with this Windows Installer Package.  A program run as part of the setup did not finish as expected.  Contact your support personnel or package vendor.".

So far, I've tried:

• Re-downloading the zipped installation files
• Installing to a different directory
• Rebooting
• Removing the \Program Data\Solarwinds files
• repairing my .net installation

I've also tried installing on a difference Windows 7 Pro machine, and on this computer, the installation starts but just hangs.  I can see two DRS10... processes running in task manager, but they never do anything.

Not sure what to try next.

Ideas?

The Beta for DameWare Mobile (iOS) is now available to existing customers on maintenance. DameWare mobile will allow you to use the remote control function you have come to know and love, from your mobile device. Currently this beta is only for iOS, but rest assured Android is on our list as well. We're all super excited to play with it ourselves, so if you are interested in participating, please fill out this survey and I will send you the Beta information right away.

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