Im trying to use Nview or Hydravision to easily space out multiple instances of Dameware MRC 10.0.0.372. If I run the program like you normally would I can snap the MRC windows to the grid no problem. However in my work environment Im forced to "run as administrator" from my normal account in order for the program to have proper privileges to connect to other computers on our network here. When I run it as an admin there are no Nview or Hydravision option available when I right click the top of the window. If I log in to my admin account and start MRC it works fine but I cant run my office eautomation software on my admin account as we are not allowed to do so in our environment here. Is this just a limitation of the software or is there something special that has to be done in order to allow it to work?

We currently use this software as a way to connect to users. Most of the time we are making changes to issues that if the user say and tried to recreate they would do major damage. Is there a way to display a splash screen that the user sees while I do what I need to and connected? We are currently using Dameware MRC Version 10.0.0.372.

Thanks

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?

I'm unable to launch my DMRC console, I can't get past the login. I get an "Internal server error." message. However, I'm able to get into the Dameware Server Administration Console without a hitch.

I've restarted the Dameware Server service and the whole server and it changed nothing, except the first time I tried to log in I got "SOAP parsing error occured. It might be due to incompatible versions of the Server and Console." as the error message and Internal server error afterwards.

Here's the service log entry that appears on each unsuccessful login (server host is in french, so some messages are translated):

2014-09-11 09:09:03,535 [19] ERROR DameWare.Server.Executive.SettingsCache - SettingsCache.GetSetting could not retrieve Setting with name 'CentralServer_TcpServerIpAddress'. Error: La clé donnée était absente du dictionnaire.,
StackTrace: à System.Collections.Generic.Dictionary`2.get_Item(TKey key)   à DameWare.Server.Executive.SettingsCache.GetSetting(String settingName)
2014-09-11 09:09:03,535 [19] ERROR DameWare.Server.RoleCentralServer.Executive.ExecutiveSubSystems - CentralServer.Authenticate service - Unexpected error occured. Error: La clé donnée était absente du dictionnaire.,
StackTrace:    à System.Collections.Generic.Dictionary`2.get_Item(TKey key)   à DameWare.Server.Executive.SettingsCache.GetSetting(String settingName)   à DameWare.Server.RoleCentralServer.Services.Implementation.CentralServer..ctor(ISettingsCache settingsCache, ISWLogger logger)   à DameWare.Server.RoleCentralServer.Services.Implementation.CentralServiceManager.<ConfigureServiceHost>b__1()   à DameWare.Server.Common.WcfServiceHelpers.CustomWcfServiceInstanceProvider.GetInstance(InstanceContext instanceContext, Message message)   à System.ServiceModel.Dispatcher.InstanceBehavior.GetInstance(InstanceContext instanceContext, Message request)   à System.ServiceModel.InstanceContext.GetServiceInstance(Message message)   à System.ServiceModel.Dispatcher.InstanceBehavior.EnsureServiceInstance(MessageRpc& rpc)   à System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage41(MessageRpc& rpc)   à System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage4(MessageRpc& rpc)   à System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)   à System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage3(MessageRpc& rpc)   à System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage2(MessageRpc& rpc)   à System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage11(MessageRpc& rpc)   à System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage1(MessageRpc& rpc)   à System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)

Some translation:

Error: La clé donnée était absente du dictionnaire. = Given key was missing from the dictionnary

I’m thrilled to announce that Dameware 12.0 is now publicly available. In this release we focused all our efforts to finalise the remote support story with unattended over the internet sessions. Dameware now allows to assist remotely without presence of the end-user, who is not in the intranet but travelling. Technicians can now support end-user in company network as well as in Internet anytime.

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

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

Dameware 12.0 is available for download on your customer portal for those customers under current maintenance.

If you are not a Dameware user yet, now go and download new version from www.dameware.com now!

Good morning, we are having an issue using DameWare when
using the screen it will cut off the right and left side of the display. This
is happening on a Dell 3510 Precision PC. Even after adjusting the resolution
and restarting, it goes back to that display. We would like to get the laptop
back to its normal display. Please advise.

Thank you

When I'm using Dameware V10 to remote into a client's machine, it always starts with the following message "Configuring the remote system for first time use. This may take as much as two minutes. Please wait..."  It allows me to get to the client's machine but then the CTRL-ALT-DELETE function doesn't work and I can't log in. I've also tried to use the Send "CTRL+ALT+DELETE" option.  I've installed and re-installed the Dameware Software at least 3 times but it still has the same issue. What would be causing this problem? Thanks.

I have a user laptop with a strange issue. Noticed in Event Viewer, that one particular error pops up very frequently. This error occurs roughly every 3 minutes.

Log Name:      Application

Source:        dwmrcs

Date:          6/21/2016 11:39:25 AM

Event ID:      110

Task Category: Error

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      **********************

Description:

Error:

DameWare Mini Remote Control

Error setsockopt (IP_DROP_MEMBERSHIP)

System Error: 10038

System Message: An operation was attempted on something that is not a socket.

(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="2016-06-21T18:39:25.000000000Z" />

    <EventRecordID>14385</EventRecordID>

    <Channel>Application</Channel>

    <Computer>***************</Computer>

    <Security />

  </System>

  <EventData>

    <Data>

DameWare Mini Remote Control

Error setsockopt (IP_DROP_MEMBERSHIP)

System Error: 10038

System Message: An operation was attempted on something that is not a socket.

(srv 64 bit) </Data>

  </EventData>

</Event>

This is on a newly imagined laptop.

Any insight on what could be causing this or how I can prevent this from happening?

Sometime when connecting to high resolution clients, my dameware mrc does not let me move the window on my screen.  I am connected to two clients right now for example.  One is at 1024x768.  The dameware "window" has a menu bar (File, Send, Monitor...) and buttons, and the display of this remote machine is integrated within this window.  I can minimize, maximize, close or drag this window around no problem.

The other machine I am connected to is 1920x1080.  The view of this remote machine is separated from the dameware toolbar in the top middle of my screen.  The window border around the view of the remote machine is so thin that there is nothing to grab ahold of to move this window around my screens.  I can only really awkwardly resize it to move it to another monitor or another place on my screen.  How could I get the view of this remote machine attached with the menu bar and tool bar, like the other machine?  There's no way to disconnect either.  Well one would have to close it from the taskbar.  If you click the little X in the top anchored, centered toolbar that is detached from the remote PC view, that toolbar goes away permanently . unless you close dameware and reopen it.

I am using MRC 9.0

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?

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

Let the community know how impressed you are with DameWare MRC 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?

I upgraded to Dameware v 10 and every single time I connect to a remote client it asks me if I want to upgrade it.  I want this to stop happening.  I'm not going to upgrade any clients until the rest of the team upgrades their Dameware from 9 to 10 or 8 to 10 in some cases.

How can I make Dameware stop being so annoying and intrusive every single time?

I'm trying to find out if the "Encrypted Windows Logon" is using Kerberos as the underlying protocol. I'm assuming the "NT Challenge/Response" is using NTLM but it would be great to know if that is the case for sure.

Second part of the question would be if there is a way to turn on Pass-Through authentication for "Encrypted Windows Logon". It grays out the check box for "Use Current Logon Credentials" when I choose it.

I am trying to figure out what the authentication requirements are to use dameware across multiple domains.

I am in Domain1.com and I need to be able to support Domain2.com, but I have to create an account in Domain2.com to be able to support these users.

I want to be able to use my Domain1.com account to manage all users in Domain2.com. I have made my account part of Domain2.com 's built in administrators group but still no luck.

Help please!

Good Morning,

I have been using DameWare MRC for quite some years now and all of a sudden I get the following error:

Winsock Connect Error:

System Error 10060

System Message:

A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

I believe there were settings changed in the group policy that does not allow a client to respond to the remote calls because it stopped working from 1 day to the next.

Still the same OS Windows 7.

I do not have any problems at all to install/uninstall the service via network on the client computers thru the MRC.

Using it on my servers it works perfectly.

Since my domain administrators are glueless what change they could have done with the group policy to prevent the clients from responding and I do not know either I would like to find out thru this route if anyone is outthere that would have idea which setting needs to be switched on the client computers.

Thank you for your time and possible assistance.

Regards.

          Hoagie

This issue started about a month ago with a group of machines. There is no apparent link to these machines which did not have the issue prior. I have read many forums and discussions relating to a firewall issue, but there is no firewall turned on internally. There are other machines on the same switches which work without issues, as well as other states and building which have no issues. We have tried to uninstall the software and service, remove all related folders,  and reinstall everything fresh with the same issue following.

When we encounter this issue on a machine, we use the remove service feature in Dameware, then close the application and open again and try to connect. We are then prompted to reinstall the service, which will then allow us to connect, and will continue working correctly until the machine is restarted. This does not fix the problem, and each time we must do the same steps to connect to the problem machines.

The service is currently set to automatic on all machines. When we tried to set it to manual, we could connect but would have to install or start the service first, which does not work well. When we set it to delayed start, we are able to connect after 2 few minutes after reboot. we have also tried to register the service again and it did not help.

When looking in the event logs for the problem machines, the following data shows in the failure entry.

"

Error:

DameWare Mini Remote Control

No Link-Local or Site-Local Cloud Available (Local).

System Error: 10091

System Message: WSAStartup cannot function at this time because the underlying system it uses to provide network services is currently unavailable.

(srv 64 bit)

"

Any help on why this is happening or what could be the cause would be greatly appreciated.

I had a Dameware batch file I used to remote into computers. I have updated dameware and now my batch file no longer works. I did change the the path so the path is correct. When I run this, I get an error saying Authentication Failed Remote Message: System Error: 87 The parameter is incorrect.

I use this because I have a Local Admin account on all computers on our Network, but I wasn't able to Remote into the machines when I was logged in with my Domain user account. So I ran this batch file, and entered my local admin username, and it would ask me for a password, and then it would conect.

Can someone tell me what I need to do?

Here is the Batch File:

@echo Dameware Login
@Echo --------------
@Echo Off

Set /p PC="Connect To:"

set /p inputone="Username:"
C:\Windows\System32\runas.exe /user:%inputone% "C:\Program Files\SolarWinds\DameWare Mini Remote Control 11.0 x64\DWRCC.exe -c -h -a:2 -m:"%PC%

Thanks for your help!

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

I tried to connect with MRC 9 and got the below error. I tried again on 11 and got the same thing. Another PC with MRC is having the same issue. Other remote PCs are fine. I removed the remote service and the issue persists. Any ideas?

Please try one of the other authentication types or please check the remote machine's authentication settings.

Disconnecting.

Date: 08/11/2014 12:22:18

Computer Name: XXXX

User ID: XXXX

Logon As ID:

Domain:

Desktop User ID: XXXX\XXXX

Desktop Name:

Connect via Proxy: No

Desktop State: User is logged on

Permission Required: No

Access Approved By: N/A

Access Declined By: N/A

Access Request Timeout: N/A

Access Request Disconnected: N/A

OS Product ID: 00392-918-5000002-85187

OS Registered Owner: XXXX

OS Registered Organization:

Host Name from Peer: XXXX

IP Address(es) from Peer: XXXX

Peer Host Name:

Peer IP Address: XXXX

Protocol Version - DWRCC.EXE: 10.000000-0.000000

Protocol Version - DWRCS.EXE: 10.000000-0.000000

Product Version - DWRCS.EXE: 11.0.0.1003

Product Version - DWRCC.EXE: 11.0.0.1003

Authentication Type: NT Challenge/Response

Last Error Code: 0

Last Error Code (WSA): 0

Host Port Number: 6129

Host IP Address: XXXX

Host Name: XXXX

Absolute timeout setting: 0 minutes

Connect/Logon timeout setting: 90000 milliseconds

Access Check:

Registered: Yes

WTS Session: No

Used Diffie-Hellman Key Exchange.

Used Shared Secret: No

Registration: XXXX

(srv 64 bit)