Hi,
I've just downloaded and install Dameware Remote Support Centralized version and installed it successfully in my VM running on my internal network.
How to perform agentless remote user connection using the Intel AMT feature ?
Most of my HP Desktop got Intel AMT feature sticker in front of it.
Thanks,
Hi
We are in the process of migrating to Dameware RS and MRC from Teamviewer. We are having a number of issues during testing that I don't really want to be landing on the support desk as its going to make a hard job harder for them.
Namely issues arise around Internet sessions. The thing is we support around 75 companies, all separate, and range in size from 5 to 100 users. Getting Dameware agent client on all those systems just isn't plausible, so the Internet session option makes full sense.
However we are getting issues with this and wondered if others have gotten over the same:
Windows Firewall - forever blocking the software, sometimes not giving the option to unblock either;
IE Popup blocker - blocking the download connection software page;
Certificate Error - Have installed a GoDaddy SSL certificate on the Internet Proxy, and it does present the certificate to the end user, but its still saying the site/certificate can't be verified, even though the URL etc. all square up.
MAC OS - Seems no way to offer Internet session to MAC OS users?
Any help/advice appreciated.
Thanks Guys.
Last year when we renewed our licenses we upgraded from ver 9 to version 11. I put together a Centralized server which everyone now logs into to use DameWare. However, when I tried to enter the keys into the License Activation program it wouldn't accept them and I had to open a service request to get it resolved so we could use DameWare. Earlier this year I expanded my license count, and again, when I tried to update using the License Activation program it wouldn't accept the keys so I had to open another service request.
I just upgraded to the new Version 11.2 and renewed my licensing again for another year. However, it is not reflecting in either the Server Admin Console or the Activation program. Both still show the license is only valid through the middle of next week and the Admin Console comes up w/ warnings that there is only 7 days left. When I click the "I Already Paid" button in the warning it just opens the web page for me to sign into. I found the License Manager out there and downloaded it. I ran the sync on that and it comes back fine, shows that I'm good through next year. Still not updating in the Admin console. I can enter the keys from my info on the customer portal in the Activation program and at least it shows that it takes them - used to always fail. However, the dates are still showing that my licensing is about to expire.
What am I missing?!! Why isn't it updating the date info for me so I'm not seeing the errors in the Admin console any longer?!
To use the unattended OTI, can someone please answer the following questions?
1. Will I need to install the centralized server?
2. Does the server need to be on at all times (determines which machine I'll be installing on)
3. Will the server be the PC I have to access the remote machines from, or will I be allowed a laptop/desktop?
4. If we are allowed a laptop or desktop, how do I notate that it's the machine that will be doing the accessing? (I'm sure I have to notate the machine somehow for licensing)
5. I will be the only person allowed to use Dameware, so we purchased 1 license and a years support and upgrades...
Is this sufficient for me to run about 100 machines in various locations, as long as I'm the only one accessing them from my machine?
Thanks for all of your help!
Unable to log onto remote machines using DameWare 5.5.0.2
by threeofspades on Thu Sep 13, 2007 5:34 am
Hi All,
We are currently having issues with logging onto some of our machines using the DameWareMini Remote Control. We recently installed some Microsoft patches on the machines and this has resulted in us having to log onto the machines using Remote Desktop rather than DameWare. Do you know of any Windows updates that may affect DameWare connection? When we try toconnect using DameWare we get the Winsock error:
Connect Error:
System Error: 10061
System Message: No connection could be made because the target machine actively refused it.
We have gone onto the DameWare help site and read through the help topics on this error but are still unable to resolve.
Any help would be greatly appreciated.
Kind regards.
Re: Unable to log onto remote machines using DameWare 5.5.0.2
by bryan on Fri Sep 14, 2007 11:13 am
Hello threeofspades,
Are you sure you're specifying the correct TCP port in your Host settings?
Is the MRC Client Agent Service already installed & running on these remote machines?
If so, have you tried stopping the Service, changing the TCP port, and then restarting the Service?
Because a Winsock 10061 error typically means the MRC Agent Service was not listening on the TCP port that you specified (default is TCP 6129). Then a subsequent attempt at interrogating the Servcie Control Manager on the remote machine failed for some reason (insufficient rights, ports blocked, file & printer sharing not enabled, etc…). This process of interrogating the Service Control manager requires the Operating System's Installed Protocols (File & Printer Sharing - UDP 137, UDP 138, TCP 139, TCP 445) to be open between the loal & remote machines, and it also requires Administrator rights within the O/S security on the remote machine.
Therefore if we cannot connect to the MRC Client Agent on the remote machine using the specified TCP port, and then we also cannot communciate with the Service Control Manager on the remtoe machine using Microsoft’s APIs, then we have no choice but to fail. Because these same ports/protocols used by Microsoft’s APIs in order to communicate with the Service Control Manager are the same ones required to install, remove, start, or stop the MRC Client Agent Service on the remote machine.
However, please also click on the Copy button on the Winsock Error Dialog, then send me this information (paste it into this email) back to me for examination. Also include a screen shot of the actual Winsock Error dialog as well so I can review it.
Your feedback is appreciated.
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
Re: Unable to log onto remote machines using DameWare 5.5.0.2
by threeofspades on Mon Sep 17, 2007 6:19 am
Hi Bryan,
Thank you for your response.
I have some additional information that may help to try to resolve this issue.
I can use MRC on the servers themselves to connect to my own machine, but am unable toconnect from my machine to the servers using MRC.
When i try ot connect to the server using MRC i first get a message saying the following:
"The DameWare Mini Remote Control is not running on onyxctx2.
Would you like to start it now?
Host: onyxctx2".
I select OK but then get the following error:
"Unable to start Service
System Error: 2
System Message:
The system cannot find the file specified"
When I RPC'ed onto the server and checked the DameWare Mini Remote Control service is was not running. When i selected to start it i get the error:
"Could not start the DameWare Mini Remote Control service on Local Computer
Error 2: The system cannot find the file specified."
When i checked the path to the executable 'C:\WINDOWS\system32\DWRCS.EXE -service' the DWRCS.EXE was not in there.
I have tried to load DameWare again but get the same errors. It seems that this executable has been deleted for some reason. How can i retrieve it or load it again?
Thank you for your time and effort.
Kind Regards
Re: Unable to log onto remote machines using DameWare 5.5.0.2
by bryan on Mon Sep 17, 2007 10:37 am
Hi threeofspades,
You're welcome and thank you for this additional information. It was very helpful...
As you have already found, Microsoft's System Error: 2 means File not found, and that's definitely due to the DWRCS.EXE file being missing in the System32 folder.
However, all you should have to do is re-copy the DWRCS.EXE file from your local DameWareInstallation folder to the System32 folder on this remote machine. Then you should be able torestart the Service again.
But you might also want to do a little extra research to find out how this file could have been deleted.
I hope this helps.
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
Re: Unable to log onto remote machines using DameWare 5.5.0.2
by threeofspades on Tue Sep 18, 2007 4:43 am
Hi Bryan,
I took your advice and copied the DWRCS.EXE file from my local machine to the WINDOWS\system32 folder on the server.
When i tried to MRC onto the server i got the request:
"The DameWare Mini Remote Control is not running on onyxctx2.
Would you like to start it now?
Host: onyxctx2".
I selected OK and it came up withthe message:
"Service Start Status:
Starting service....."
I thought that this was looking good but unfortunately it came back to the above message:
"The DameWare Mini Remote Control is not running on onyxctx2.
Would you like to start it now?
Host: onyxctx2".
It seems that the service is starting but is tehn stopping several seconds later.
I RPC'ed onto the server to check out the DameWare Mini Remote Control service. It was setto automatic and was not started. i set it to start and it did so. But about 5 seconds later it just stops.
Not sure what is going on but something is stopping the service from running.
Any ideas?
Kind regards
Re: Unable to log onto remote machines using DameWare 5.5.0.2
by bryan on Tue Sep 18, 2007 1:46 pm
Hi threeofspades,
Thanks very much for the update. This is some great information.
I believe you're right. There appears to be something else here that's stopping the Service from running. What other software do you have running on this machine? Do you have anything like CA eTrust, or Pest Patrol, or Pest Patrol remote (look for ppRemoteService.exe in Task Manager under Processes)?
If this is the cause, then additional information on how to configure the appropriate exception within Pest Patrol is also available in another thread on our forum:
The Dameware mini remote service is not running on XXX.
http://forums.dameware.com/viewtopic.php?f=8&t=47
Your feedback is appreciated.
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
Re: Unable to log onto remote machines using DameWare 5.5.0.2
by threeofspades on Thu Sep 20, 2007 5:42 am
Hi Bryan,
Thank you for all your help.
We do have eTrust running on our systems and when i placed the DameWare exception into the Management Console i got DameWare back working on all but one server. But i will check it out and see if i can figure out where the problem is. I'm sure it's just something simple but the service still seems to be stopping on that particular server.
Thanks again for all your help and it was very much appreciated.
Kind Regards
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]
When our IT remotes to our Windows PCs they leave behind the DameWare Development Mirror Driver. This driver causes problems with at least one software application, and so it needs to be removed after the remote IT session is ended. How can this be automated?
Unable to register
by Roger on Wed Jan 19, 2011 4:02 pm
Is there a trick to register this? I installed the 64bit since I'm using Win XP 64bit and my About Box is not Drag and Drop enabled (No cursor indication other than the not allowed circle with line through it). Why remove the text way of registering? I'd much rather just copy and paste the key text like before.
Roger
________________________________________
Re: Unable to register
by Roger on Wed Jan 19, 2011 4:05 pm
On another note I did remember a trick with holding Ctrl and clicking in there which in this version enables some Help Index option that appears to be a debug option for the help index number passed to help??? Not as useful as Ver6 which I think was some type of debug/logging mode.
Roger
________________________________________
Re: Unable to register
by Roger on Wed Jan 19, 2011 4:08 pm
Ok, figured it out, someone goofed and it isn't drag and drop....but the clipboard IDrop/IData object stuff. It had a paste menu option I found on right click. You don't copy the text though but the file itself then paste. Very odd.
Roger
________________________________________
Re: Unable to register
by cadamwil on Thu Jan 20, 2011 11:44 am
Roger,
I am unable to register as well. I am running 7.0.2.0. When I hit "about" I get a "Copy" and a "Close" button. Which file did you paste? I received my license number from the registration but it appears different than I was used to previously. Not a long string but just a code, kind of like Microsoft. Any help would be greatly appreciated.
Adam
cadamwil
________________________________________
Re: Unable to register
by bryan on Thu Jan 20, 2011 12:47 pm
You should have also received a dwabin.txt file attached to your registration email. Once you have your registration email, including your dwabin.txt file, there are several ways to register the software.
Option 1: Copy the dwabin.txt file into program installation folder. Then run the software and it will automatically show as registered.
Option 2: Copy the dwabin.txt file to your desktop, then open the MRC software, then drag and drop the file directly into MRC (not onto the Remote Connect dialog).
Option 3: Open the MRC software. Press Esc to close the Remote Connect dialog, then select the Help / About DameWare MRC menu. Now right-click on the dwabin.txt file and select Copy. Now right-click in the Help/About dialog and select Paste.
Addidional information can also be found on the DameWare Support YouTube Channel:
http://www.youtube.com/DameWareSupport
Here is the direct URL to the Activation Video:
http://www.youtube.com/watch?v=GWMW943gXU0
I hope this helps.
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
________________________________________
Re: Unable to register
by cadamwil on Thu Jan 20, 2011 1:05 pm
Thanks Bryan. I am up and going now.
Adam
cadamwil
________________________________________
Re: Unable to register
by bryan on Thu Jan 20, 2011 1:38 pm
Hi Adam,
You're most welcome, and thanks very much for your feedback.
It's most appreciated.
Best Regards,
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
________________________________________
Re: Unable to register
by Roger on Thu Jan 20, 2011 1:56 pm
Option 3 is how I ended up doing it. It and Option 1 werent documented. Option 2 is what wouldn't work for me. The email actually said to drag to the about box which wouldn't work and neither did dragging to the main window. I was dragging from another folder though and not the desktop. Shouldn't have made a difference though.
________________________________________
Re: Unable to register
by bryan on Thu Jan 20, 2011 3:36 pm
Thanks for your feedback Roger.
Do you have UAC enabled? Did you run the MRC software (DWRCC.EXE) "As Administrator"? If so then you're actually running under a different security context when you run elevated, which would explain why Drag and Drop didn't work, because the process didn't have access. In this scenario, it would not matter where you try to drag and drop from, it would fail. However, this is also why we implemented the Copy and Paste file routine, which did work for you. Another option would have been to not run as Administrator, and then drag and drop should have worked.
I hope this helps.
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
________________________________________
Re: Unable to register
by Roger on Fri Jan 21, 2011 2:38 am
No UAC in XP 64bit. My account isn't the Administrator user, but is a member of Administrators group. So, I'm confused now...an Administrator group account should be able to drag and drop fine anywhere. Are you saying I have to run as a basic User to be able to drag and drop??? I got it to work so not really a big deal plus the other 3rd option I know of now. I just wanted to point it out as not working for me and the email sent with the key could use updating with all 3 methods if others have issues.
Re: Unable to register
by bryan on Fri Jan 21, 2011 3:29 am
Thanks Roger.
Since you're running XP-64, the info I provided previously about UAC and "Run As Aministrator" really doesn't apply to your scenario. That info only applies to Vista, Windows 7, and 2008 Server, where the O/S actually splits your user access token into two pieces. When you login on those specific Operating Systems, you only get the regular user part of your token (even when you login with an Admin level account).
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
________________________________________
Re: Unable to register
by blanalex on Thu Jan 27, 2011 10:06 am
Is it the same licence as in version 6.x or do we have to get new licences for version 7?
Also, our purchasor didn't forward the dwabin.txt file, only the key in the body of the message. Can I copy the key (all the text between the lines begging with equal signs and the complete lines with the equal signs) into a text file and that would work?
________________________________________
Re: Unable to register
by bryan on Thu Jan 27, 2011 5:52 pm
You would need a new license for version 7.x of the software. Version 6.x licenses will not work in v7.x and vice versa.
I hope this helps.
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
________________________________________
Re: Unable to register
by rpabst on Thu Mar 10, 2011 4:31 am
Hi everybody,
we have installed version 7.4.0.0 under windows 7 SP1 (32-Bit) and received the dbawin.txt.
No way to register....
All 3 Methods not working!!!
Such idea??? Possible depends on SP1...
Thx,
Robert
Update:
I try the same dbawin.txt under fresh installation on windows xp...
Same as under windows 7. None of the methods will activate the license!!!
Corrupt dbawin.txt file????
________________________________________
Re: Unable to register
by bryan on Thu Mar 10, 2011 11:06 am
Hi rpabst,
If none of the activation methods have worked for you then its very possible something in your dwabin.txt file may have become corrupted. Just out of curiosity, what do you use for your mail server and client?
I would also suggest you send a copy of your dwabin.txt file to support@dameware.com so we can review it.
Your feedback is appreciated.
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
________________________________________
Re: Unable to register
by rpabst on Thu Mar 10, 2011 1:03 pm
Bryan wrote:Hi rpabst,
If none of the activation methods have worked for you then its very possible something in your dwabin.txt file may have become corrupted. Just out of curiosity, what do you use for your mail server and client?
I would also suggest you send a copy of your dwabin.txt file to support@dameware.com so we can review it.
Your feedback is appreciated.
Hi Bryan,
thanks for your quick response!
So i will send the dbawin.txt to support for review.
Regards,
Robert
________________________________________
Re: Unable to register
by bryan on Thu Mar 10, 2011 3:49 pm
Hi Robert,
After reviewing your dwabin.txt file, it was definitely corrupted. Most likely somewhere between your Distributor and yourself. In comparing the original file we sent out to the file you sent back to us we found multiple entries in the file were altered. This could possibly be related to an email server along the way, an email client, or even Anti-Virus scanning/altering the file.
I resent you a copy of the original file we sent out and also provided a temporary link to download it just in case.
I hope this helps. Your feedback is appreciated.
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
I am new to Dameware and have found the install/configuration very frustrating. I have called support three times in the process (last call was 2 hours), so now I will try this forum.
I got the server setup and want to deploy DRS to the techs. I found a link to this kb on using the msi to install, but I do not see the msi - only the exe (the kb was for ver 9.)
In order to keep working I just installed DRS with the gui but then it prompts me for the license (which is fine), BUT it does not give the option of pointing the install to the central server to get the license.
Can someone provide guidance? I have read the install manuals but they do not seem to be oriented to an enterprise admin. Really an Getting started / best practice document would be helpful to someone new to the product.
Thanks.
People,
How can I deploy Dameware agent to the workstations in the different subnet / VLAN from the central server in my data center ?
Each site offices and user computer objects spread across multiple different OU, so I wonder is there any outage when delivering the agent to the users with any of the way supported by Dameware ?
Thanks.
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
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
Hi All!
I was wondering if someone knew when Dameware Mini Remote Control v12 is coming out. My boss thought he saw an e-mail about it come out, but he wasn't sure. Just here to see if anyone else saw an e-mail and possibly remember a date (if possible).
Thanks!
To use the unattended OTI, can someone please answer the following questions?
1. Will I need to install the centralized server?
2. Does the server need to be on at all times (determines which machine I'll be installing on)
3. Will the server be the PC I have to access the remote machines from, or will I be allowed a laptop/desktop?
4. If we are allowed a laptop or desktop, how do I notate that it's the machine that will be doing the accessing? (I'm sure I have to notate the machine somehow for licensing)
5. I will be the only person allowed to use Dameware, so we purchased 1 license and a years support and upgrades...
Is this sufficient for me to run about 100 machines in various locations, as long as I'm the only one accessing them from my machine?
Thanks for all of your help!
Last year when we renewed our licenses we upgraded from ver 9 to version 11. I put together a Centralized server which everyone now logs into to use DameWare. However, when I tried to enter the keys into the License Activation program it wouldn't accept them and I had to open a service request to get it resolved so we could use DameWare. Earlier this year I expanded my license count, and again, when I tried to update using the License Activation program it wouldn't accept the keys so I had to open another service request.
I just upgraded to the new Version 11.2 and renewed my licensing again for another year. However, it is not reflecting in either the Server Admin Console or the Activation program. Both still show the license is only valid through the middle of next week and the Admin Console comes up w/ warnings that there is only 7 days left. When I click the "I Already Paid" button in the warning it just opens the web page for me to sign into. I found the License Manager out there and downloaded it. I ran the sync on that and it comes back fine, shows that I'm good through next year. Still not updating in the Admin console. I can enter the keys from my info on the customer portal in the Activation program and at least it shows that it takes them - used to always fail. However, the dates are still showing that my licensing is about to expire.
What am I missing?!! Why isn't it updating the date info for me so I'm not seeing the errors in the Admin console any longer?!
Hey,
We're using the latest version of Remote Support (Centralized Install method). I'm pretty sure we've not had this problem before but I can't be sure.
Basically, the mirror driver stays 'in use' even after disconnecting, so it's breaking most of the Aero features (thumbnail previews in this particular case. I tried:
connecting and disconnecting to see if it cleared
forcefully ending the processes
None of those worked - the Aero troubleshooter still said mirror drivers were in use.
I had to uninstall the mirror driver from Display Adapters in Device Manager and reboot to clear it.
I'm sure that in the past (we've only just upgraded to the latest version) it would drop to Basic theme on connect, and go back to Aero theme on disconnect. Never had mirror drivers interfering with Aero before.
Is it because we've just never used the mirror driver method? Is it on by default only in newer versions. We were quite a few versions behind before upgrading.
And is this "by design" if using the mirror driver. What does the mirror driver actually do?
Thanks!
Hi
We are in the process of migrating to Dameware RS and MRC from Teamviewer. We are having a number of issues during testing that I don't really want to be landing on the support desk as its going to make a hard job harder for them.
Namely issues arise around Internet sessions. The thing is we support around 75 companies, all separate, and range in size from 5 to 100 users. Getting Dameware agent client on all those systems just isn't plausible, so the Internet session option makes full sense.
However we are getting issues with this and wondered if others have gotten over the same:
Windows Firewall - forever blocking the software, sometimes not giving the option to unblock either;
IE Popup blocker - blocking the download connection software page;
Certificate Error - Have installed a GoDaddy SSL certificate on the Internet Proxy, and it does present the certificate to the end user, but its still saying the site/certificate can't be verified, even though the URL etc. all square up.
MAC OS - Seems no way to offer Internet session to MAC OS users?
Any help/advice appreciated.
Thanks Guys.
Hi Guys,
Having some issues with Dameware Version 7.5.6.1
Issue 1: I am always getting the authentication type to be defaulted to encrypted windows logon instead of windows NT challenge/response and tick user current logon credentials which I use to remote into the user computer. Is there a fix to default the authentication type to the selected values?
Issue 2: When I remote to a user’s computer using dame ware. The desktop background always changes to a black desktop background.
Any help would be greatly appreciated!
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]
I would drop some of my PDF guides here, leave comments and feedback on how we could improve them. Some of them will be how to's and so on and so forth.
Hope this would be able to help some of you guys!
Centralized Logging Feature - version 11.x.x.xxxx
Guide for using the MSI builder (Guide for agent.pdf)- version 11.x.x.xxxx
Guide for manually joining the internet session - version 11.x.x.xxxx - This came from a customer our thanks
many more to come!