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

Hi All,

Currently evaluating Dameware DRS 11.0.0.1003 for our environment. In past employments I have relied heavily on Dameware for my Team's support operations. I was hoping to employ this tool here in my current role, but I have come across something that may be a deal breaker. The majority(about 2/3) of our staff here use WYSE terminals and login to a session on our Terminal Servers (WIndows 2008 R2). We have been connecting via RDC to the Terminal Server, login then using the TS Admin Tools launch a remote session to the Staff member. I was hoping to use Dameware DRS to actively connected to the session directly. Does anyone know if this is possible and if so how?

Many thanks.

Logan

Hi,

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

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

"DameWare Mini Remote Control

Your logon request was declined.

Disconnecting...

Request for permission to remote control encountered an error.

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

In Windows event log is an error:

'Error: Failed to acquire logon permission.

User Disconnected."

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

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

Both computers runs Windows XP Pro 32-bit version.

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

I would really appreciate some help and advice.

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

Computer Comments no longer appear
by Brachus on Thu Apr 30, 2009 7:00 am

We recently upgraded our domain controllers to Server 2008. However, after doing so, DameWare has stopped showing the Computer Comments for the Workstations.
If we right click, go to tools and then computer comments, the information is still there. When we hit OK, it appears next to the workstation as before, but only temporarily. If we restart the program, or even just collapse the Workstations tree, then expand again, they are lost.

Brachus
________________________________________
Re: Computer Comments no longer appear
by kfluckiger on Mon May 18, 2009 3:42 am

Hello!

Did you find a solution ? cause we got exactly the same problem yet!

Before we had a 2003 Server for secondary controller and it works and now I ugrade it to 2008 and all comment are lost!

If you go to tools computers comments it comes but only for the session when you close dameware it lose comments again!

I try to put it in Active Directory computer comments but not way to see it in Dameware

Today I update to 6.1.8.5 but still going wrong

Is the support knowing that problem ? any idea how to resolve it ?

We are very frustrating here cause a lot of computer and the name are not really comprensible so we have to lool all the time and search for...

Take a lot of time

Please remedy to that soon as possible or we will change to another software!

Thanks

Kevin
________________________________________
Re: Computer Comments no longer appear
by KarbonKopy on Tue May 19, 2009 12:01 pm

I too had the same problem when I migrated to a 2008 DC. It seems to work randomly, even with testing the AD computer names doesn't seem to make a difference. On a side note where did you get 6.8.1.5? I only see .4 on the download page.
________________________________________
Re: Computer Comments no longer appear
by kfluckiger on Wed May 20, 2009 2:22 am

Hello

Sorry for the mistake, yes you right I've the same version as you...

What I see today is if you put any computer in favorite machines IT WORKS!!!!

So now I'm sure it's coming from Dameware software!!!

Is there any dameware technician who read forum ? can you debug it for the next version cause a lot of people will migrate to W2K8 and I think it's really easy to solve for you!

thanks

Kevin
________________________________________
Re: Computer Comments no longer appear
by jfor26 on Thu Jun 04, 2009 2:36 pm

we have the same problem. I dont think they check this place regularly at all. we are looking at a different package for remote admin

http://www.pjtec.com Their Goverlan suite.
________________________________________
Re: Computer Comments no longer appear
by Marty on Thu Jun 11, 2009 3:12 pm

Hi guys,

With regards to Computer Comments and potentially having them displayed, DNTU has the ability to retrieve & display Computer Comments. However, understand that "Comments" are handled & maintained in many different ways (i.e. Local Machine, Windows Network Browser, Domain Controller, Active Directory, etc.) within the O/S itself, and even within the NT Utilities software.

DNTU's Active Directory section will always look to Active Directory to find the Computer Comments. Whereas, DNTU's Microsoft Network section, DNTU's Favorite Machines (formerly non-Browsable) section, and even the Tools / Computer Comments tool (and previous 4.x versions as well) always look to the local machine for the Computer Comments (i.e. Computer Description).

Therefore, if you want the Computer Comments to appear all the time under DNTU's Active Directory browser, you must add the Comments within Active Directory. This is why they appear temporarily, but then disappear when you close and restart, because DNTU once again looks to AD for them. This can also be done via DNTU within the Active Directory browser by right-clicking on the machine in the Tree View (left-hand pane), then selecting Properties, then make the necessary changes in the Description field (which are the AD comments).

If you wish for the Computer Comments to be displayed in parenthesis behind the Computer in the Favorite Machines (formerly non-Browsable) portion of DNTU or the Microsoft Windows Network section, then you would basically modify the Comments directly on the remote machine (right-click My Computer / Properties / Computer Name Tab). This can also be done via DNTU by selecting Tools / Computer Comments, which will actually retrieve & modify the Comments/Description on the actual remote machine.

I hope this helps.
Marty Bonvillain
Support Staff
DameWare Development, LLC.
http://www.dameware.com

________________________________________
Re: Computer Comments no longer appear
by bryan on Fri Jun 12, 2009 10:55 am

What I see today is if you put any computer in favorite machines IT WORKS!!!!

If this is the case then these Comments are actually stored directly on the remote machine itself (i.e. Computer Description), not in Microsoft's Windows Network Browser (i.e. NT Browser). DNTU's Favorite machines list and the Tools / Computer Comments feature retrieve the Comments directly from the remote machine itself, and these Comments will not be dynamically shown in Microsoft's Windows Network Browser.

The Microsoft Windows Network Browser portion of DNTU retrieves the information from Microsoft's Network Browser (i.e. Network Neighborhood, My Network Places) which is part of your O/S & network itself (i.e. the Master Browser). We simply ask your O/S on your local machine for it's Windows Network Browser information, and then we display what's returned back to us. This information is not modified in any way.

When using the Microsoft Windows Network portion of the Browser in our software, DNTU will not attempt to contact the machine directly to retrieve this information (like it does in Favorite Machines), because all the relavent information should already be in Microsoft's Browser. Whatever information is populated within Microsoft's Network Browser itself is the information that DNTU will display in this section of the software.

Microsoft has also documented known issues with NetBios Browsing in Server 2008 (see below).

NetBIOS Browsing and Windows Server 2008 x64 Server Core
http://blogs.technet.com/networking/archive/2008/12/16/netbios-browsing-and-windows-server-2008-x64-server-core.aspx

NetBIOS browsing across subnets may fail after upgrading to Windows Server 2008
http://blogs.technet.com/networking/archive/2008/07/25/netbios-browsing-across-subnets-may-fail-after-upgrading-to-windows-server-2008.aspx

Troubleshooting the Microsoft Computer Browser Service
http://support.microsoft.com/default.aspx?scid=kb;EN-US;188305
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com

________________________________________
Re: Computer Comments no longer appear
by Brachus on Mon Jun 15, 2009 8:10 am

Thanks for the information Bryan. This was more helpful than a copy and paste from the manual when we were trying to explain that the MS Network Browser comments stopped working despite all settings being correct.
________________________________________
Re: Computer Comments no longer appear
by kfluckiger on Thu Jun 25, 2009 7:52 am

Hello

Sorry you don't really understood what everybody wants

Sure now it's clear how it work's but what we want and I found the solution

It's to see directly computer comments in microsoft windows network

For make it simple directly when we open dameware, cause if you use it all time it's very slow to go each time in the AD, find the good "OU" and so on...

Now if you have the same issue as mine

First go to network neighberhood with a client in XP (not working with vista) and see if there's comment behind computer

If not do theses things

In Windows 2008 and AD environnement without other 2003 server you simply have to disable Computer Brower service in the DC

After little time every comments will be appears again

If you still have Win2003 server you can also transfer Master browser to it and it works!

Thanks to all for your help
________________________________________
Re: Computer Comments no longer appear
by Abbala on Fri Dec 11, 2009 2:13 am

Thanks for taking the time to help, I really apprciate it.

------------------------------------------------------------------
Re: Computer Comments no longer appear
by Marx7 on Wed Jul 07, 2010 10:05 am

I was still a little unclear on how to fix this issue on my network after reading through this discussion, but understood that the master browser was somehow the issue, so I started looking into how to find the master browser. I found the following page that explains very easily how to find your master browser: http://www.ifrankie.com/?p=45 It talks about using XP SP2 support tools, which I found here: http://www.microsoft.com/downloads/details.aspx?familyid=49ae8576-9bb9-4126-9761-ba8011fabf38&displaylang=en I followed the instructions from ifrankie and found that the computer that was the master browser was an XP box that had been on and sitting idle for about 2 months. I rebooted that computer, and everything started working again as a different computer became the master browser.
This is what worked for me. I hope it helps others.

-------------------------------
Debt is normal. Be weird.

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  

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

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.

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

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. 

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

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

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

i knew FAQ, search do not give me answers.

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

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

Re: one more time about user notify dialog

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

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

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

Your feedback is appreciated.

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

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

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

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

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

nope, no evaluation enyware.

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

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

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

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

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

Administrators:

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

Non-Admins:

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

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

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

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

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

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

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

I hope this helps.

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

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

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

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

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

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

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

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

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

Hello lufoxe,

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

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

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

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

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

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

I hope this helps.

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

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

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

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

Hi lufoxe,

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

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

Test

Hello,

I just had a look at the new dameware V11 presentation at http://go.solarwinds.com/dameware/sneakpeek/v11

It looks great and I have to figure out how much it will cost to jump to version 11.

I cannot find if the centralized server has a separate license or if the ability of installing this centralized server is "included" in the "per user" DRS or MRC licenses.

Thanks in advance.

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

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.

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

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.

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]

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.

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