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.
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 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>
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!
Hello!
I have an issue with the Remote option 'Show Remote Cursor' not working on many clients even though I have activated the setting under Default Host. It doesn't work even though I connect to new target PC's after the change of setting or modifying an existing client-setting.
I have changed the setting on the Host-PC to enable 'Show Remote Cursor' under Default Host. The Target PC's (Which I connect to) has Dameware Mini Remote Control Service installed.
Host PC- Mini Remote Control 12.0.4010.3
Target PC - Dameware Mini Remote Control Service 12.0.3.0
Client OS: Windows 7 x64 SP 1
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?
Hello!
I have recently deployed a customized dameware mini rc service MSI via GPO into my windows network. I am having trouble with it though. The client installs and all seems well, but it is not keeping any of my customization to the service. Things like: Allow multiple administrators to all have control, proprietary username/password, no notifications, etc. are not being deployed with the MSI. HOWEVER, if I manually install the MSI that the GPO is calling then all of the appropriate customization are being installed.
All of our servers are running Windows Server 2012 and the end-users are on everything from Windows XP to Windows 10. The customized features are not being installed on any of the Operating systems.
Any suggestions?
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?
Some times when I try to connect to PC A, I select it from my AD list in the dameware mrc but I get connected to PC B instead. On top of the windows it displays it like this PC B (PC A).
What is causing that tp happened?
Hi,
With Dameware MRC, it's possible to customize the toolbar of the main window, right-clic and "customize" menu.
But if I remove buttons on that toolbar, changes are not reported in the Full Screen Toolbar. Why ? Is there a way to customize this toolbar ? For exemple I want to remove printing and SFT buttons, useless for me.
Regards,
Seb
Running DameWare Version 11.2.0.91 (64 Bit)
Hello there everyone, had a question about DameWare and GPO options. When Reg changes are made through group policy shouldn't the DameWare Mini Remote Control take the changes in effect? I made changes to the following Reg Files: Force Encrypt Data, Force Encrypt Images, and SFT: Enable Simple File Transfer and moved my VM to test out the results. The Reg files took the changes but the application did not.
When you launch the DameWare Mini Remote Control > Remote Connect Window > Click Settings > Click Encryption Options Tab and under Remote Control box options still unchecked (Encrypt General Data and Images)?
Under Simple File Transfer: Enable Encryption Still Unchecked?
With the changes made to the reg files, shouldn't these options be checked with Reg Value of 1?
If I am doing something wrong, please let me know thank you in advance.
Josh
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!
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
Hallo zusammen,
Ich habe ein Problem beim Command Line Connect auf eine Maschine im Unternehmen.
Zunächst: Über GUI Funktioniert alles.
Folgende Angaben sind eingestellt:
Host: IP-Adresse
Authentication Type: Windows NT/Response
User ID: support
Passwort: Ein Passwort ohne Leerzeichen
Domain: Ebenfalls eine IP-Adresse
Use MRC's Mirror Driver if available ist angehakt
und der Radio-Button ist auf Use MRC Viewer gestellt
Weitere Settings sind in der GUI nicht eingestellt und so komme ich immer auf die Maschine drauf.
Wenn ich den Command Line Befehl folgendermaßen aufbaue:
DWRCC.exe -c: -h: -x: -m:192.168.202.135 -d:192.168.202.138 -u:support -p:Passwort -a:1 -md:
sollte ich die gleichen Settings eigentlich drin haben, er versucht auch sich zu Verbinden, bei der Authentifizierung bekomme ich dann nur die folgende Fehlermeldung:
DameWare Mini Remote Control - Connect
Authentication failed:
Remote Message System Error: -2146893048
System Message:
Das Token, dass der Funktion übergeben wurde, ist ungültig.
Please check event log on the remote machine for possible cause.
Kann mir das verhalten jemand erklären? Ich habe schon diverse Foreneinträge durch und auch selbst schon alles möglich Probiert und rum gebastelt, aber nichts will funktionieren.
Die Command Line Switches habe ich in der Doku gefunden: Mini Remote Control Command Line Switches
Mit freundlichen Grüßen,
Kevin van Thiel
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. 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.
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
Is there a possibility to activate the DMRC (Stand Alone Mode) without Internet Access and the usage of manual activation within the Portal?
We have thousands of licenses, I cannot do a offline activation for every client with no Internet Access.
Can i do this with the Dameware Central Server? I do not want to switch the mode to the Centralized-Mode! Outerwise i have the problem, that the server must be high available.
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?
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.