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!
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
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'm having an issue getting MAC Discovery and WOL working over multiple VLANs in our environment. I have close to 40 VLANs. I just tried to do a MAC discovery for WOL and I basically can't discover a single MAC address for anything outside of my own VLAN. Same is true when manually putting a MAC in and trying to do a WOL on a different VLAN. Has anyone else been able to get this to work?
We've updated the DameWare - Updated February 17, 2015 support page. This serves as a one-stop shop for all your DameWare documentation, how-to's, troubleshooting, and more. You can add the page to your "links" or bookmark the page so you'll always have it handy.
Hope this helps, as always!
Danielle!
Note: This is a topic brought over from DameWare Forums which has been closed. If you wish to engage in this discussion, just comment here.
Your logon request was declined. Disconnecting...
by fabvit on Fri Jan 14, 2011 4:23 am
I'm using the invitation mechanism in DWMRCS v7.
I've noticed that if I leave checked the Require Permission while creating an invitation, later on when I try to connect to this machine I got a dialog:
Your logon request was declined.
Disconnecting...
Request for permission to remote control encountered an error.
- [0]
If I remove the check from Require Permission while creating an invitation, later I can connect to this machine.
What is the purpose and how to setup the Require Permission mechanism.
--
tanks, fabio
Re: Your logon request was declined. Disconnecting...
by bryan on Fri Jan 14, 2011 3:47 pm
Thanks very much for your feedback on this.
We were able to reproduce this issue and we should have it fixed shortly.
Best Regards,
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
Re: Your logon request was declined. Disconnecting...
by bryan on Fri Jan 14, 2011 5:51 pm
Hello Fabio,
We wanted to let you know we just finished updating all the files on our website. Since this is only a minor update, you will have to remove the old MRC Client Agent from your remote machine, then remove your current MRC v7 install on your local machine. Next, download and install the most current files from our website. Then you can reinstall this newer Client Agent Service onyour remote machine.
Your feedback is appreciated.
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
Re: Your logon request was declined. Disconnecting...
by Siggi on Wed Feb 23, 2011 4:22 am
I have the same problem while trying to connect to one specific client running Windows 7 x64. After a few seconds I get the message "Your logon request was declined", but there was norequest shown on the users screen.
I'm running DameWare Mini Remote Control 7.2.0.0 x64 and I have installed the latest agent on the client. I have enabled the option "Permission required" on the client agent.
In some cases in the past, it worked to restart the DameWare MRC Service on the client or to reinstall the service. In this case, it didn't At the moment, I can advise the user to lock his screen, then I can connect to the desktop without requiring a permisson.
Re: Your logon request was declined. Disconnecting...
by Siggi on Tue Mar 01, 2011 10:45 am
No ideas?
It's a big problem for us at the moment and we're thinking about going back to v6...
Re: Your logon request was declined. Disconnecting...
by bryan on Tue Mar 01, 2011 11:09 am
Have you tried the most current version of the software, which is 7.3 not 7.2 ? You must also update the Client Agent on the remote machine to v7.3 as well.
It souds to me like the DWRCST.EXE (SysTray Icon) process is not running on the remote machine for some reason. You can open Task Manager and check for this process. It should be running anytime there is a user currently logged into the desktop on a remote machine, and the remote machine is not currently at the Logon Desktop or Lock Screen.
Your feedback is appreciated.
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
Re: Your logon request was declined. Disconnecting...
by Siggi on Thu Mar 03, 2011 3:40 am
I've just tried the 7.3 today. I also removed the old Client Agent on the remote machine and installed the current one. I checked the DWRCST.EXE process in the task manager, it is running.
The problem stays the same.
Re: Your logon request was declined. Disconnecting...
by bryan on Thu Mar 10, 2011 4:45 pm
Please try downloading and installing v7.4 of the MRC software, and then please make sure you update the MRC Client Agent Service on the remote machien to v7.4 as well. We found an issue with a socket API that could return different results on some OS’s.
Your feedback is appreciated.
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
Re: Your logon request was declined. Disconnecting...
by Siggi on Fri Mar 11, 2011 4:35 am
It does not work with 7.4 Same problem.
Re: Your logon request was declined. Disconnecting...
Marty on Fri Mar 11, 2011 12:21 pm
Hi Siggi,
We are still unable to reproduce this behavior in our environment, however we would very much like to resolve this issue. With that said, can you email support@dameware.com so we can provide you with some customized troubleshooting steps for your environment?
Also, if there are any DWMRCS application event log entries on the remote machine, forward those back to us in your email as well.
Thanks so much and we appreciate your help!
Marty Bonvillain
Support Staff
DameWare Development, LLC.
http://www.dameware.com
Re: Your logon request was declined. Disconnecting...
by bryan on Wed Mar 16, 2011 10:00 am
With the help of one of our customers (Thank You Frank !!!) we have confirmed this issue will be resolved with the release of v7.5 of the software.
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
Re: Your logon request was declined. Disconnecting...
by Siggi on Thu Mar 17, 2011 9:55 am
It works!!! Thank you so much, Bryan (and Frank )
Very little new issue: The version number in the NT Utilities application is shown as "7.4" even in the 7.5 package, so we were a little confused with the update process.
Re: Your logon request was declined. Disconnecting...
by bryan on Thu Mar 17, 2011 2:06 pm
Hi Siggi,
You're most welcome, and thanks very much for your feedback on this. We really appreciate it.
With regard to the version, please try this out for me. First remove your existing install of DNTU via Add/Remove programs. Then download and install v7.5 again from our website to see if you can still reproduce this behavior.
Your feedback is appreciated.
Best Regards,
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
Re: Your logon request was declined. Disconnecting...
by Adrian on Mon Nov 28, 2011 10:56 am
Hi, I am having the same problems as this. The slight difference is my PC is Windows 7 64 bit and the client is 32bit XP. If I use a Windows 7 32 bit it works fine
Thanks
Two issues - I had DRS installed on my Windows 7 Pro workstation, but was experiencing some unexplained weirdness, so thought that I'd remove and reinstall just to rule that out. I can't get it reinstalled - keep getting the message "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.".
So far, I've tried:
I've also tried installing on a difference Windows 7 Pro machine, and on this computer, the installation starts but just hangs. I can see two DRS10... processes running in task manager, but they never do anything.
Not sure what to try next.
Ideas?
If possible change standalone client of DRS to client / server version?
Im new to DameWare, is there a way to list all computers in an organization that have dameware currently installed?
How do I uninstall DameWare DRS (V. 11.1) and recover the license for another machine
I notice after installing the client for DameWare Remote Support that the Remote Support Service 2.6 (DameWare NT Utilities) isn't also installed and has to be manually installed and started on my clients in order to do remote commands etc. Anyway to include that service and automatic start when I'm rolling our clients?
I just upgraded my centralized server to version 11.1 and I'm trying to get all of my techs client machines upgraded but the silent install isn't working. It just hangs forever. Any idea if there are some changed arguments for version 11.1 .exe install.
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!
Can we leverage the central server to enforce technicians to remove MRC service upon disconnect from client machine? And can the central server manage and log all remote sessions for audit?
There are many useful tools inside DRS. I use them often and I am happy that my boss paid the DRS-licenses.
But lately I became aware, that (after some relocations of whole departments inside our company) our Windows 7 licenses got mixed up. Some PCs were renamed, some were moved to other places and so on.
Now I tried to tidy up. Sadly we still have workgroups instead of domains and we have no license-server, only single keys, not pinned on the PC-hull, but lying in a cabinet.
Now I have found some free tools on the inet, that can read the key, but I dont intend to walk to every pc and start the tool there.
Is there a solution for this problem inside DRS? If not, do oyu intend to put this function in one of the next updates?
Thanks in advance for the answer.
Marcel
Hello DameWare users!
Here is a brief guide to shows how to gather information from computers in your network or domain using the DameWare Exporter tool included with DameWare Remote Support.
Objectives:
1- Get "Installed Software" data from computers in my network to create a report.
2- Get the information in a CSV file format so it can be easily imported into an Excel spreadsheet
3- Get the information from several computers in a single file
First, you have to launch the tool. You can find it in the same location as the main DameWare Remote Support application (Start > Programs > SolarWinds > DameWare Remote Support 9.0 > DameWare Exporter). You can recognize it easily by the colors in the icon (blue/yellow) :
In the Exporter tool you must change the settings so the files created have the CSV format instead of XML (which is used by default). In this example we want to get "Standard" information (which basically means we are pulling data from the machine instead of Active Directory) so that's the tab we need to modify:
NOTE: The "Single File" option here indicates that a single file will be made per-machine including all properties selected. It DOES NOT mean a single file will include each computer.
Once the output file type is set, do the following:
1- Under "Task List" uncheck everything except for Standard Properties - Software.
2- Click the "Add Machines" button to include the computers you want to survey.
3- Make sure all the systems in the "Computer List" are checked
4 - Click on "Start Exporting"
After this you will end up with a .csv file for each computer you surveyed. Unfortunately, DameWare Exporter doesn't feature an option to generate a single file for all the computers. However, CSV files are easily merged using the Windows copy command. Place all the files in the same folder and run the following command in the Command Prompt:
copy *.csv allcomputers.csv
This line will create a new file, "allcomputers.csv" (you may use the name of your choice) that will be a merging of all .csv files found in that folder.
Two issues - I had DRS installed on my Windows 7 Pro workstation, but was experiencing some unexplained weirdness, so thought that I'd remove and reinstall just to rule that out. I can't get it reinstalled - keep getting the message "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.".
So far, I've tried:
I've also tried installing on a difference Windows 7 Pro machine, and on this computer, the installation starts but just hangs. I can see two DRS10... processes running in task manager, but they never do anything.
Not sure what to try next.
Ideas?
Platform: HP ProBook 4420s, Windows 7(x64) pro SP1, DRS v10.0 installed
Use-Case: In the DRS opening window, select Tools, Search, enter text string, click "Search"
Failure: An unhandled win32 exception occurred in DNTU.exe
Event is repeatable.
------------------
Application Event Log Properties:
-----------------
Log Name: Application
Source: Application Error
Date: 3/19/2014 10:00:15 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: IT-PROBOOK1.dcgc.net
Description:
Faulting application name: DNTU.exe, version: 10.0.0.372, time stamp: 0x51796d95
Faulting module name: DNTU.exe, version: 10.0.0.372, time stamp: 0x51796d95
Exception code: 0xc0000409
Fault offset: 0x00148ce9
Faulting process id: 0x2748
Faulting application start time: 0x01cf4394a6a9415a
Faulting application path: C:\Program Files (x86)\SolarWinds\DameWare Remote Support 10.0\DNTU.exe
Faulting module path: C:\Program Files (x86)\SolarWinds\DameWare Remote Support 10.0\DNTU.exe
Report Id: f0a5e089-af87-11e3-b55a-3c4a9252f274
Hi,
i just want to try Dameware and it would be important that I can offer remote support on client machines that are not in our lan. So I figured that Dameware Proxy could be the right solution, but unfortunatetly I find the provided documentation is lacking some practicable examples on how to setup the firewall properly. I found some kind of documentation http://ramgesoft.com/index.php/de/hersteller/solarwinds/dameware-mini-remote/technikhowtofaq-s/497-dameware-server-11-installation-und-konfiguration in which it says, that all traffic on port 443 and 80 must be forwarded to the server which ist hosting dameware proxy. Well, our firewall itself ist listening on port 443 and 80 so I suppose it would not be advisable to redirect that traffic to the Dameware Proxy, wouldn't it? What about ports 6132 and 6133? Must they be redirceted too?
Right now all Dameware Servers are running locally on one single machine, just for testing purposses.. There is on Firewall with multiple WAN, one of which should accept incomming traffic which should then be redirected to the Proxy.
Could anyone give me a few hints on how to achieve my goal of a working Proxy?
regards, heinzelrumpel
Note: This is a topic brought over from DameWare Forums which has been closed. If you wish to engage in this discussion, just comment here.
Your logon request was declined. Disconnecting...
by fabvit on Fri Jan 14, 2011 4:23 am
I'm using the invitation mechanism in DWMRCS v7.
I've noticed that if I leave checked the Require Permission while creating an invitation, later on when I try to connect to this machine I got a dialog:
Your logon request was declined.
Disconnecting...
Request for permission to remote control encountered an error.
- [0]
If I remove the check from Require Permission while creating an invitation, later I can connect to this machine.
What is the purpose and how to setup the Require Permission mechanism.
--
tanks, fabio
Re: Your logon request was declined. Disconnecting...
by bryan on Fri Jan 14, 2011 3:47 pm
Thanks very much for your feedback on this.
We were able to reproduce this issue and we should have it fixed shortly.
Best Regards,
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
Re: Your logon request was declined. Disconnecting...
by bryan on Fri Jan 14, 2011 5:51 pm
Hello Fabio,
We wanted to let you know we just finished updating all the files on our website. Since this is only a minor update, you will have to remove the old MRC Client Agent from your remote machine, then remove your current MRC v7 install on your local machine. Next, download and install the most current files from our website. Then you can reinstall this newer Client Agent Service onyour remote machine.
Your feedback is appreciated.
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
Re: Your logon request was declined. Disconnecting...
by Siggi on Wed Feb 23, 2011 4:22 am
I have the same problem while trying to connect to one specific client running Windows 7 x64. After a few seconds I get the message "Your logon request was declined", but there was norequest shown on the users screen.
I'm running DameWare Mini Remote Control 7.2.0.0 x64 and I have installed the latest agent on the client. I have enabled the option "Permission required" on the client agent.
In some cases in the past, it worked to restart the DameWare MRC Service on the client or to reinstall the service. In this case, it didn't At the moment, I can advise the user to lock his screen, then I can connect to the desktop without requiring a permisson.
Re: Your logon request was declined. Disconnecting...
by Siggi on Tue Mar 01, 2011 10:45 am
No ideas?
It's a big problem for us at the moment and we're thinking about going back to v6...
Re: Your logon request was declined. Disconnecting...
by bryan on Tue Mar 01, 2011 11:09 am
Have you tried the most current version of the software, which is 7.3 not 7.2 ? You must also update the Client Agent on the remote machine to v7.3 as well.
It souds to me like the DWRCST.EXE (SysTray Icon) process is not running on the remote machine for some reason. You can open Task Manager and check for this process. It should be running anytime there is a user currently logged into the desktop on a remote machine, and the remote machine is not currently at the Logon Desktop or Lock Screen.
Your feedback is appreciated.
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
Re: Your logon request was declined. Disconnecting...
by Siggi on Thu Mar 03, 2011 3:40 am
I've just tried the 7.3 today. I also removed the old Client Agent on the remote machine and installed the current one. I checked the DWRCST.EXE process in the task manager, it is running.
The problem stays the same.
Re: Your logon request was declined. Disconnecting...
by bryan on Thu Mar 10, 2011 4:45 pm
Please try downloading and installing v7.4 of the MRC software, and then please make sure you update the MRC Client Agent Service on the remote machien to v7.4 as well. We found an issue with a socket API that could return different results on some OS’s.
Your feedback is appreciated.
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
Re: Your logon request was declined. Disconnecting...
by Siggi on Fri Mar 11, 2011 4:35 am
It does not work with 7.4 Same problem.
Re: Your logon request was declined. Disconnecting...
Marty on Fri Mar 11, 2011 12:21 pm
Hi Siggi,
We are still unable to reproduce this behavior in our environment, however we would very much like to resolve this issue. With that said, can you email support@dameware.com so we can provide you with some customized troubleshooting steps for your environment?
Also, if there are any DWMRCS application event log entries on the remote machine, forward those back to us in your email as well.
Thanks so much and we appreciate your help!
Marty Bonvillain
Support Staff
DameWare Development, LLC.
http://www.dameware.com
Re: Your logon request was declined. Disconnecting...
by bryan on Wed Mar 16, 2011 10:00 am
With the help of one of our customers (Thank You Frank !!!) we have confirmed this issue will be resolved with the release of v7.5 of the software.
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
Re: Your logon request was declined. Disconnecting...
by Siggi on Thu Mar 17, 2011 9:55 am
It works!!! Thank you so much, Bryan (and Frank )
Very little new issue: The version number in the NT Utilities application is shown as "7.4" even in the 7.5 package, so we were a little confused with the update process.
Re: Your logon request was declined. Disconnecting...
by bryan on Thu Mar 17, 2011 2:06 pm
Hi Siggi,
You're most welcome, and thanks very much for your feedback on this. We really appreciate it.
With regard to the version, please try this out for me. First remove your existing install of DNTU via Add/Remove programs. Then download and install v7.5 again from our website to see if you can still reproduce this behavior.
Your feedback is appreciated.
Best Regards,
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
Re: Your logon request was declined. Disconnecting...
by Adrian on Mon Nov 28, 2011 10:56 am
Hi, I am having the same problems as this. The slight difference is my PC is Windows 7 64 bit and the client is 32bit XP. If I use a Windows 7 32 bit it works fine
Thanks