Any one else experiencing an issue with the DameWare SmartCard Driver failing to load on Windows 10 machines with Device Guard enabled? No issues on machines without Device Guard enabled.

Dameware v12 on Server 2012 attempting to connect to a Win7 64bit which I've unistalled and reinstalled latest client agent.

Tried connecting via Active Directory, Microsoft Windows Network and by IP address all 3 fail with this message.

"DameWare Mini Remote Control - Connect

Authenitcation failed:

Remote Message: System Error: -2146893048

System Message:

The token supplied to the function is invalid

Please check the event log on the remote machine for a possible cause"

Has anyone had this issue and solved it?

All help, hints and advise gratefully received as I can't get to the remote machine to check for a possible cause.

Thanks in advance

Hello,

I am setting up Dameware 10 Remote Control Tool on a few systems and am having an issue getting connected to remote systems using my CAC.  We have both admin and regular certs on the CAC but will be using the admin cert to do the remote control assistance.

Ill give you a rundown of what I am doing:

Right click DameWare Mini Remote Control > Run as (choose my admin Cert from CAC)

Fill in all information needed (Select Smart Card logon and fill in PIN)

Click connect and get error, after a few moments of waiting

Error:

DameWare Mini Remote Control

Smart Card Logon Failed (5.2).

System Error: 1326

System Message: Logon failure: unknown user name or bad password.

After inspecting the security logs on the client system I see that the error is because its attempting to use my regular user account, not my admin account. Even tho we are running the MRC tool using admin cert credentials.

Security Logs on client system shows the attempted connection and failure:

An account failed to log on.

Subject:

  Security ID: SYSTEM

  Account Name: %COMPUTERNAME%$

  Account Domain: %DOMAIN%

  Logon ID: 0x3e7

Logon Type: 3

Account For Which Logon Failed:

  Security ID: NULL SID

  Account Name: %REMOVEDINFO%

  Account Domain:

Failure Information:

  Failure Reason: Unknown user name or bad password.

  Status: 0xc000006d

  Sub Status: 0xc0000064

Process Information:

  Caller Process ID: 0x380

  Caller Process Name: C:\Windows\dwrcs\DWRCS.exe

Network Information:

  Workstation Name: %Computername%

  Source Network Address: -

  Source Port: -

Detailed Authentication Information:

  Logon Process: DWMRC3

  Authentication Package: Kerberos

  Transited Services: -

  Package Name (NTLM only): -

  Key Length: 0

This event is generated when a logon request fails. It is generated on the computer where access was attempted.

The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).

The Process Information fields indicate which account and process on the system requested the logon.

The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

The authentication information fields provide detailed information about this specific logon request.

  - Transited services indicate which intermediate services have participated in this logon request.

  - Package name indicates which sub-protocol was used among the NTLM protocols.

  - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.

I am a local admin on remote system and can confirm this with username and password, so we know the authentication is there.  For some reason it keeps defaulting back to the regular user cert.

Any thoughts on it?

Dameware Mini Remote Version: 12.0.2.3 64bit

Operating System: Windows 10 Pro 64bit Build 1607 OS Build 14393.693

Getting Error on newly imaged machines:

Authentication Failed Remote Message System Error -2146893048

System Message:

The token supplied to the function is invalid

Please check the event log on the remote machine for a possible cause

Event Log on the machine in question:

Log Name:      Application

Source:        dwmrcs

Date:          1/23/2017 5:01:43 PM

Event ID:      110

Task Category: Error

Level:         Error

Keywords:      Classic

User:          N/A

Computer:     

Description:

Error:

DameWare Mini Remote Control

Error setsockopt (IP_ADD_MEMBERSHIP)

System Error: 10065

System Message: A socket operation was attempted to an unreachable host.

(srv 64 bit)

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="dwmrcs" />

    <EventID Qualifiers="0">110</EventID>

    <Level>2</Level>

    <Task>2</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2017-01-24T01:01:43.599750000Z" />

    <EventRecordID>469</EventRecordID>

    <Channel>Application</Channel>

    <Computer>LA-LT-CLASS-01.hallmarkchannel.com</Computer>

    <Security />

  </System>

  <EventData>

    <Data>

DameWare Mini Remote Control

Error setsockopt (IP_ADD_MEMBERSHIP)

System Error: 10065

System Message: A socket operation was attempted to an unreachable host.

(srv 64 bit) </Data>

  </EventData>

</Event>

Hi all,

We have following scenario in our environment: If you are using Dameware Mini Remote Control in addition with a Dameware Central Server,
it would be great that the Dameware Mini Remote Control Client would be able to "cache" the checked-out license for some hours on the computer (something like Microsoft KMS is doing it, but not with 100 days )

This would be the best solution is the server breaks/reboot for updates/maintainance etc. Otherwise Dameware Mini Remote Control Client cannot be started and the IT support is blind.

Do you know any possibilities to do this?

Best Regards,

Thomas

WHen I try to install DameWare Mini Remote Control 9.0, I get  "there is a problem with this windows installer package. A program run as part of teh setup did not finish as expected." I checked teh app log and get :

Product: DameWare Mini Remote Control 9.0 -- Error 1722. 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.  Action APPDIR, location: C:\Program Files\SolarWinds\DameWare Mini Remote Control 9.0\, command: "C:\Program Files\SolarWinds\DameWare Mini Remote Control 9.0\SolarWinds.MRC.Licensor.exe"

The description for Event ID 0 from source Installer Registerer cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

ErrorReference:IECookie Error:ErrorCode:12

I tried loading version 10 qand get the same thing.  Any ideas?

Any one else experiencing an issue with the DameWare SmartCard Driver failing to load on Windows 10 machines with Device Guard enabled? No issues on machines without Device Guard enabled.

I'm getting this error when trying to dial into one specific site. All the computers at this site give me the same error. I can succesfully log into all of our other sites using Dameware with Windows NT challenge response. I have confirmed that there are other users who are having this problem as well, however strangely some users can still access this site with Dameware and Windows NT challenge response no problem. I found a post on your old forums recommending adding a few lines of code into the INI file, but that must have been for an older version of Dameware that still used one, I think it all goes into the registry now. Has anyone had this issue before? If you need any more info please let me know.

Any help is appreciated!

We have recently started using Dameware and Mini Remote.  When I use  Mini Remote to connect to a users pc I'm finding that it changes their desktop display settings. These changes are tied to mini remote because they were reported within a minute of me connecting to their pc for the first time.  And, it was reported by users in the order in which I connected to their pc's.   One right after the other.   I'm aware of two specific changes:   the color scheme changes (minor in the big picture but it's the little things that keep them happy), the task bar for example was a deep blue now it's a muted gray color.    The biggest complaint is that the windows preview when you mouse over an application icon in the task bar changes from window previews to a list.   Previously, if you had multiple word documents open and had it set to not combined icons it would show one Word icon in the task bar.  If you would mouse over the Word icon it would pop up little windows for each document you had open and as you mouse over each window preview it would temporarily display that document maximized on the screen.  Now, it only pops up a list, that's in, no interactive preview or anything.

With my previous employer I used mini remote extensively and did not see this happen.  Please help, my name is mud with several users because of this.

Your insight and expertise is appreciated.

Joatta Sayles

WHen I try to install DameWare Mini Remote Control 9.0, I get  "there is a problem with this windows installer package. A program run as part of teh setup did not finish as expected." I checked teh app log and get :

Product: DameWare Mini Remote Control 9.0 -- Error 1722. 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.  Action APPDIR, location: C:\Program Files\SolarWinds\DameWare Mini Remote Control 9.0\, command: "C:\Program Files\SolarWinds\DameWare Mini Remote Control 9.0\SolarWinds.MRC.Licensor.exe"

The description for Event ID 0 from source Installer Registerer cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

ErrorReference:IECookie Error:ErrorCode:12

I tried loading version 10 qand get the same thing.  Any ideas?

Hello,

I am able to connect to workstation on the exact subnet I am on, but not to other subnets withing the same building.

I am trying to figure out if this is a limitation of mrc or am I configuring something incorrectly?

Also, I looked up a name on a PC, tried to connect to it and somehow connected to a totally different workstation?

I doubl-checked name and IP of workstations and again, somehow connected to the incorrect workstation. Not sure how or why this may have happened.

Thank You,

Ewbh0t

Please note we have released Hotfix 1 for Dameware version 12.0. This hotfix is available on your customer portal.

Hotfix 1 addresses the following issues:

• ZDI-CAN-3125 vulnerability (Thanks to Andrea Micalizzi aka rgod, working with HP's Zero Day Initiative, for identifying this issue.)
• Upgrading MRC agents on remote machine failed.
• MRC was not able to connect to remote machine using "MRC Ping" feature.
• DRS Service installation failed in DRS.
• Event log does not show content in DRS.

Hotfix 1 requires SolarWinds DameWare Mini Remote Control version 12.0.0.509. Hotfix 1 can be applied to both 32-bit and 64-bit installations or SolarWinds DameWare Remote Support version 12.0.0.509.

You can find more details in README file included in hotfix.

Now go and download the hotfix now.

Our company has an employee IT, who is necessary to connect to the computers of other users and help them. In this case the employee does not have the rights of a domain and local administrator on the users' computers. If the officer is trying to connect to the user - the user pops up a request for acceptance of connection.

Despite the fact that the user agrees to the connection, you can only view the remote computer, without the ability to manage the session.

Tell me, is it possible to manage users' computers without domain rights and local administrator?

UPDATED

After reading the article How to: Allow automatic Remote Control for non-admin users I realized that it is sufficient to remove the label from one of the items on the agent.

The question is how it's best to remove these marks made on all computers in the network?

I have Dameware 7.5.6.1 32 bit running on 64bit Windows 7 and the remote clients are all 64bit Windows 7 machines.

It seems when I login to some of our remote computers I get an Smart Card Authentication failed error:

"System error: -2146435069, Remote Message: System Error: -2146435069. System message: the supplied handle was invalid."

The corresponding Windows Application logs show: "System error 10014, event id 110."

It seems to happen when I try to use the miniremote to remote into some computers, not all remote clients. It seems to happen after a sudden disconnect or reboot of the remote machine. It doesn't matter where I do it, so it not computer/profile specific. And I can get co-workers to login to the same remote system w/o issue, so it seems to be my issue.

I can use dameware NT utilities to access all the tools for the respective computer but a soon as I try to use MiniRemote and try to login I get the error. I can use other remote desktop apps and windows RDP w/ smart card authentication w/o errors.

I've tried uninstalling and reinstalling the program on my pc, the service and drivers on the remote PC w/ Dameware software. I've tried manually adding and removing the conents %windir%\dwrcs folder on the remote system w/o issue.

Damware sees my smart card as a JavaCard #2 if that helps.

Error (ID 110):

DameWare Mini Remote
Control

Error setsockopt
(IP_DROP_MEMBERSHIP)

System

Error: 10038

(srv 64 bit)

Get this error when trying to connect to some computers in our network, not all. Reinstalling the service sometimes help, making the user lock their computer sometimes help. What is the root cause for this problem?

Hi people

-im trying to launch mini remote control from command line as follow:

"C:\Program Files\Solarwinds\DameWare Mini Remote Control 9.0\DWRCC.exe" -c: -h: -a:1 -m:server -u:user -p:pass -d:domain

but always fail with error message about wrong credentials. ( see screen attached )

-On the other handif iusethe same credentialsfromthe GUI , successfully connects.

-The remote PC is on a workgroup not in the domain

seems like from the command line always use the logged on user credential not the passed user/pass.

What might be theproblem?

txs in advance

PD: version 9.0.0.174 32 bits

WHen I try to install DameWare Mini Remote Control 9.0, I get  "there is a problem with this windows installer package. A program run as part of teh setup did not finish as expected." I checked teh app log and get :

Product: DameWare Mini Remote Control 9.0 -- Error 1722. 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.  Action APPDIR, location: C:\Program Files\SolarWinds\DameWare Mini Remote Control 9.0\, command: "C:\Program Files\SolarWinds\DameWare Mini Remote Control 9.0\SolarWinds.MRC.Licensor.exe"

The description for Event ID 0 from source Installer Registerer cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

ErrorReference:IECookie Error:ErrorCode:12

I tried loading version 10 qand get the same thing.  Any ideas?

Does anyone know how to create a shortcut to open to a host into fullscreen?

i.e "C:\Program Files\DameWare Development\DameWare Mini Remote Control 7.5\DWRCC.exe" -c: -md: -x: -m:xxxxxxx (WHAT ELSE)

Im making a computer that auto boots, and logs into multiple virtual machines and displays them on seperate monitors. I've got everything except for figuring out how to make dameware open fullscreen. I can't find any options or anything. The closest I can get is having the screen maximized

Hi. Is there a log the computer keeps to track Dameware connections or sessions? I am new to Dameware and would like to know if this is a feature because not all staff members remember to lock the remote pc- I'm more concerned about server,) before disconnecting via Dameware.

I am running DameWare Mini Remote Control V12.0.0.509 32-bit on Windows 7 Enterprise V6.1 Build 7601 w/ SP1.

I am able to connect to a remote PC and see their desktop, along with mouse and keystroke changes; however, I am no longer able to remotely control the mouse or keyboard like I once was.

We recently upgraded to the software version shown above in order to attempt to resolve the problem. I was able to remotely control the mouse and keyboard when connected to a test PC; however, when I remoted into the PC of an internal customer who needed troubleshooting assistance, I had no mouse or keyboard control.

Suggestions?