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 Mini Remote Control Service, DameWare SmartCard Driver and Windows 10 Device Guard
↧
DameWare v12.0 HotFix 1
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.
↧
↧
Dameware Centralized Server - Useless?
Hi all,
i am sorry but i have to say i really expected more from Dameware Centralized Server. I installed the Centralized Server today (no proxy, no gateway), but this tool is just useless in my opinion.
Installation was easy yes, but after an hour i have to say: It is only usefull for centralized license management, thats all! If you have just a few licenses, dont waste your time and manage them manually.
Things i am really missing (and i think i am not alone requesting such features)
- only AD User Import, no real AD integration. Hence you have to manage your users manually.
- no Rights Managment - only admin or no admin
- no centralized config management
- no autologin with DRMC or DRMS
Global host list:
- No rights management (user only should have access to a few hosts / folders)
- no centralized and advanced settings for hosts entries (only connect with RDP to a specific host) settings will be ignored if you connect via DRMC
- its just a list of your favourites, not more not less.
Is there a wishlist for product improvement? When is the next update planned?
Thanks
Peter
↧
Dameware Mini Remote version 6.9.0.0 now Requesting permission to log onto remote computer.
We recently moved Domains.. And in doing so I had to change my profile. So I decided reinstall my Dameware Mini Remote. Out
of 60 Users 3 are now Requesting permission to log onto their computer? I have tried uninstalling then reinstalling the Dameware Client on those computers to no avail? Could someone help me? I'm the IT Systems Administrator and one of my duties, if requested by Management, is to shadow users without their knowledge and with it requesting access that defeats the purpose.
Thank you
Mark W. Gabby
↧
Dameware 10 Mini Remote Control Tool - Admin Cert on CAC
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?
↧
↧
Error connecting to client (Event ID 110, System Error 10038)
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?
↧
Error: Current server settings require specific authentication type to connect.
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)
↧
Authentication Failed Remote Message System Error -2146893048
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>
↧
"The token supplied to the function is invalid"
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!
↧
↧
DameWare Exporter
I am trying to export the AD Computer name and the Last logged in user to the same .csv file instead of seperate files even though I have it selected for same output file is set to true. Can anyone tell me how to export those two things into the same .csv file so I dont have to manually find the information in DameWare??
Thanks Robert
↧
Dameware MRC Connection from Outside Work Domain
Hi all,
First time MRC user here. Our company would like to use MRC so some designers can work remotely on the weekends. Stupid question, but do I ABSOLUTELY need to use a VPN to access the MRC Centralized Server? To my understanding, I don't see a need for MRC if I am forced to use a VPN into our domain. I would just use Windows RDC as a free solution.
↧
DameWare Mini Remote Control - Connect Authenitcation failed:
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
↧
Welcome to the DameWare MRC space on thwack!
Welcome to the DameWare MRC space on thwack! If this is your first time here, you’ll find a wealth of information available to you on DameWare MRC as well as other SolarWinds products. thwack is an active community where SolarWinds customers can share ideas and tips, ask questions, discuss feature requests, and find out what’s in the latest release and what’s coming next. SolarWinds Product Management, Development, and Support staff all regularly monitor and post to thwack. We look forward to hearing your feedback and ideas!
↧
↧
Dameware remote control is slow to connect.
When Windows Firewall is enabled stealth mode is enabled by default and there is no supported method to turn this off.
Is there any way to fix this problem on the client side without installing dameware on every single computer.
So what happens is you connect to a computer with dameware the connection spends several very noticable seconds before it promts you to install the client. This is because it seems to assume the client is always installed. And this is why stealth mode causes a problem.
Is there any way for the dameware client to do a check for the client service first and then connect or install the client?
Is this problem solved in any of the recent versions of the software? I belive we are a few versions behind.
↧
Dameware-Icon (Mini Remote Control) in Systray bleibt gelb-grün während ein Supporter aufgeschaltet ist / Systray-Icon stays yellow-green
Hallo,
wir nutzen DameWareMiniRemoteControl unter Win7 SP1.
Während einer Remotesitzung wird das Systray-Icon nicht rot, sondern bleibt auf gelb-grün. Nach einer Neuinstallation des Dienstes am Client wechselt das Icon bei der nächsten Remotesitzung korrekterweise auf rot, nach einem
Reboot und einer erneuten Sitzung ist es aber wieder gelb-grün. Der User am Client sieht so nicht, ob der Supporter noch aktiv aufgeschaltet ist.
Betriebssystem User: Win7 SP1 / DWMRC Version 7.5.0.0 (64bit)
Betriebssystem Supporter: Win7 SP1 / DMMRC Appl. 7.5.0.1 (32bit)
Problem tritt nur sporadisch auf.
Hello,
we use Dameware Mini Control Server 7.5.0.0 on our Windows7-Clients with SP1.
We pre-install the Dameware Mini Remote Service on every client with our
software deployment software DSM (Frontrange).
Here my problem:
In many cases the dameware icon in the taskbar stays yellow-green on the client
when I connect with Dameware Mini Remote Control Application 7.5.0.1, 32 and
doesn’t change to red.
The user now doesn’t know if I’m still connected.
When I manually “remove service” and “install service” in the file menu before
I start a connection, then the icon will change for the next remote session to
red on the remote client, but a day later, it’s yellow-green again during a
remote session on the same client.
Do you have an idea what goes wrong or how I can activate that the icon in the
taskbar is permanently red when a supporter is connected.
Jeder Hinweis ist willkommen ....
Danke.
↧
MRC client agent not connecting. But, both sides are the same version
I get the message - The version of Dameware Mini Remote Control application you are using is not supported by the MRC client agent......
Both sides are activated and have the same version installed -- 6.9.0.4.
What is the problem?
↧
Dameware service not installing
Hello
We have a problem on a W2K8 R2 STD server. The Dameware Mini Remote Control service is not installing automatically. All files are copied to the local folder but it seems that registry entries are missing in
HKEY_LOCAL_MACHINE\SOFTWARE\DameWare Development
In the logfile "..\All Users\DameWare Development\Logs" we see following error:
2015-12-29 15:05:54,870 main@1136 INFO [DWRCS] ************************** DWRCS version is: 11.0.0.1003 **************************
2015-12-29 15:09:03,827 main@2064 INFO [DWRCS] ************************** DWRCS version is: 11.0.0.1003 **************************
2015-12-29 15:11:14,612 ERROR [RegistryMonitorThread] Exit Registry Monitor Thread. 0
2015-12-29 15:11:14,612 ERROR [PnrpThread] Exit PNRP Thread. 0
2015-12-29 15:11:52,449 main@2944 INFO [DWRCS] ************************** DWRCS version is: 11.0.0.1003 **************************
2015-12-29 15:11:52,496 main@2944 ERROR [Service] LogErrorMsg dwErr=1063: StartServiceCtrlDispatcher failed.
The Dameware console (trying to install it) shows us an error, asking for a user and a password. After clicking cancel it gives the error "unable to install service. System Error: 5, System Messagae: Access is denied"
We have checked if the admin has all needed rights and it seems so. We have tried with a local administrator and a domain administrator. It isn't working either way. We could install it on another server with the local administrator (with identical rights), it seems that only this server has an issue.
Is this a known problem?! Is there a way to solve it? Or is there even a way to install the Dameware "host" manually? We found only an installation programm for the full version.
Thanks in advance for your help
Balu
↧
↧
DameWare Mini Remote Control Service, DameWare SmartCard Driver and Windows 10 Device Guard
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.
↧
Mirror Driver in DameWare Mini Remote Control is outdated
Is there a planned update for the mirror driver included with the v12.0.3.0 DameWare Mini Remote Control Service. Not only does it no display correctly in Windows 10 Device Manager, the driver date is over 8 years old. There is also some concern that it is causing issues with displaylink connected displays using HumanScale USB 3.0 docking stations.
↧
MRC with central server
Hello,
is it possible to use MRC with Central Server? I am asking because when I click on "buy now" at Download Remote Administration Software l DameWare it takes me to Remote Support buy page Store | SolarWinds - DameWare Remote Support - Buy Now
Also how much do I have to pay for Central Server? How is the licencing? I have 3 licences (seats) of MRC. Do I have to buy 3 licences of Central server also? Where do I have to install central server? On DC server? What happenes when my DC HDD fails, do I lose Central server licence? In that case do I lose MRC licences as well?
Is it possible to have Central server on two servers? So when one fails, the other takes over, so my colleagues can connect and use MRC? How many licences I need in this case?
↧