Quantcast
Channel: THWACK: Popular Discussions - DameWare DRS
Viewing all 14036 articles
Browse latest View live

No Active Directory Administration Interfaces Detected

$
0
0

I recently upgraded to Windows 10 and DRS 12. Since then I have been getting this in the information tab. On the Browser tab I don't get anything under the Microsoft Windows Network like I used to.

I am new to this forum and trying to search didn't seem to bring anything up. I appreciate any help anyone can be as I don't think I am getting full usage of DRS 12 because of this issue.

Thank You.


Dameware mini remote control - invisible mode(without the user knowledge)?

$
0
0

HI. there is any option in Dameware mini remote control to perform operation on other machine in invisible mode(without his knowledge)?

Automate DameWare Development Mirror Driver removal

$
0
0

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?

DameWare v12.0 HotFix 1

$
0
0

Please note we have released Hotfix 1 for Dameware version 12.0. This hotfix is available on your customer portal.

Hotfix 1 addresses the following issues:

  • ZDI-CAN-3125 vulnerability (Thanks to Andrea Micalizzi aka rgod, working with HP's Zero Day Initiative, for identifying this issue.)
  • Upgrading MRC agents on remote machine failed.
  • MRC was not able to connect to remote machine using "MRC Ping" feature.
  • DRS Service installation failed in DRS.
  • Event log does not show content in DRS.

 

Hotfix 1 requires SolarWinds DameWare Mini Remote Control version 12.0.0.509. Hotfix 1 can be applied to both 32-bit and 64-bit installations or SolarWinds DameWare Remote Support version 12.0.0.509.

 

You can find more details in README file included in hotfix.

 

Now go and download the hotfix now.

Disable automatic saved hosts

$
0
0

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.

 

Disable automatic saved hosts
by boucherjeanfra on Fri Jan 21, 2011 2:06 pm


Hi,

 

In the version 7 of Mini-Control, is it possible to disable the "automatic" save to a new host ?
I verified twice in the settings but found nothing.

 

Thanks for your help,

Cheers,


Re: Disable automatic saved hosts
by bryan on Mon Jan 24, 2011 4:01 pm


Hi boucherjeanfra,

 

Anytime you start typing while the Host field is selected the New Host dialog will be displayed, to allow you to create a new Saved Host entry. If you're trying to modify an existing entry, select the desired entry in the Saved Host List, then right-click on this entry and select Rename Host. This will allow you to modify the existing entry without creating a new one.

I hope this helps.

 

Best Regards,
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com

Re: Disable automatic saved hosts
by Siggi on Wed Jan 26, 2011 5:18 am


Hello there,


I just installed the MRC7 and have the same problem as boucherjeanfra. I also want to get the "automatic-saving-a-new-host" feature disabled because in the past I always connected to a remote host by only typing in the adress. The hosts don't need to be saved. It's faster for me than selecting the host from a list.

Hope you got what I mean.


Re: Disable automatic saved hosts
by williaa on Wed Jan 26, 2011 4:01 pm


@Bryan, what we're wanting to know is if there's any way to disable the New Host dialog from displaying anytime you start typing while the host field is selected. It's more convenient for this to not happen when using the Mini Remote Control.


Re: Disable automatic saved hosts
by bryan on Wed Jan 26, 2011 5:36 pm


Thanks everyone for your feedback.

Presently there is no way to turn this functionality off. MRC v7 will automatically create a new Host Entry when you start typing, whereas v6 would create a (Temporary) entry. (Temporary) entries no longer exist in v7.

 

Kind Regards,
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com

Re: Disable automatic saved hosts
by Siggi on Thu Jan 27, 2011 3:12 am


Perhaps, it could be an idea to add a "Quick connect" adressbar to the next version of MRC for those who want to connect in that specific way?


Re: Disable automatic saved hosts
by bryan on Mon Jan 31, 2011 5:35 pm


Hi Everyone,

 

Just FYI, we're looking into adding some new functionality in the next release of the software, which will be 7.1.0.0, where you can turn off the Host Entry "Auto Save" feature. I will udpdate everyone as more information becomes available.

 

Best Regards,
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
 

Re: Disable automatic saved hosts
by KCarney on Tue Feb 08, 2011 2:14 pm


So has it been added?


Re: Disable automatic saved hosts
by bryan on Tue Feb 08, 2011 3:17 pm


The new "Disable Auto Save" functionality was implemented in v7.1.0.0. On the MRC Remote Connect dialog (not from the main menu) first select the Edit menu, then enable the "DisableAuto Save" setting. This will instruct the software not to display the "new host" dialog when you modify the HostName/IP-Address of an existing Host Entry. Instead, a new temporary entry will be created, designated by a red circle with an x in the icon's lower right corner. If you close the MRC Remote Connect dialog, or simply Connect then Disconnect, this temporary entry will now be gone.

I hope this helps.


Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
 

Re: Disable automatic saved hosts
by KCarney on Tue Feb 08, 2011 4:57 pm


When "Disable Auto Save" option is enabled "reconnect" no longer functions properly, it now displays the last computer I connected to when the option was disabled. Please fix this


Re: Disable automatic saved hosts
by bryan on Tue Feb 08, 2011 5:35 pm


This is exactly how the reconnect option is designed to function, and this is the same way it worked in v6.x as well. By default only Saved Host entries are added to the Reconnect list, because we only have settings stored for the entries in your Saved Host list. There are no settings stored for any type of "temporary" entries, therefore, they are not added to the Reconnect list. If you need custom settings stored for any remote machine, then you must save it to your Saved Host List.

With that being said, there is a setting on the Local Global Options dialog called "Add only savedhost entries to Reconnect list". If you choose to disable this setting, then any machine you connect to will be added to the Reconnect list. However, since no custom settings exist for any of these non-saved machines, you may not be able to successfully reconnect.

If all of these non-saved machines use the same default credentials & settings, then you should be able to add these default credentials and settings to the Default Host Properties dialog. These Default Host settings are used when you create a new Host Entry. However, if you highlight an existing Saved Host Entry and then change the HostName or Ip-Address, then the settings from this Original Host Entry (not default) are used to create your new Temporary entry.

I hope this helps.


Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com

Re: Disable automatic saved hosts
by KCarney on Wed Feb 09, 2011 2:39 pm


and this is the same way it worked in v6.x as well.

No, it didn't. It randomly picked a host that was connected to by any number of open DMRC windows, it was a little annoying at times but worked. This new version seems a lot cleaner


If you need custom settings stored for any remote machine, then you must save it to yourSaved Host List.

That makes sense.


With that being said, there is a setting on the Local Global Options dialog called "Add onlysaved host entries to Reconnect list". If you choose to disable this setting, then any machine you connect to will be added to the Reconnect list. However, since no custom settings exist for any of these non-saved machines, you may not be able to successfully reconnect.

That is exactly how it worked in 6x, I will give that a try. Thanks for explaining! 


Re: Disable automatic saved hosts
by KCarney on Mon Feb 14, 2011 1:24 pm


Works great now in 7.2.0.0, thank you!


Re: Disable automatic saved hosts
by KCarney on Fri Feb 18, 2011 11:10 am


Correction, this works *sometimes*. After a week of using it disconnecting from a host and attempting to reconnect results in blanked out connection options. I have to enter the previous host manually to reconnect.


Re: Disable automatic saved hosts
by bryan on Fri Feb 18, 2011 3:02 pm


Just because you connected the first time doesn't mean you can immediately Reconnect to any machine when it's not saved in the Saved Host List. This is exactly why we did away with this feature initially for version 7.x, for all machines not saved to the Saved Host List.

When a machine is saved in the Saved Host List, we have all the settings necessary to Reconnect (UserID, Password, Port, etc...). However, when a machine is not saved to the SavedHost List, there are no settings we can use to Reconnect. Once you click on Disconnect, all those settings are now gone. We no longer have any settings for this machine. Therefore, by design, they will be blank settings exactly as you mentioned previously when you try to Reconnect, and the connection will fail.

The only way "Reconnecting" to a machine that's not explicitly saved to the Saved Host List will ever work would be if you enter the correct settings (UserID, PW, Port, etc..) under the Default Host Properties dialog (i.e. View / Default Host Properties from the main menu). Just keep in mind that these default settings would be the same settings used for all "Reconnect" attempts when a machine is not explicitly saved to the Saved Host List.

I hope this helps.

 

Best Regards,
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com

Re: Disable automatic saved hosts
by KCarney on Mon Feb 21, 2011 9:18 am


When a machine is saved in the Saved Host List, we have all the settings necessary to Reconnect (UserID, Password, Port, etc...). However, when a machine is not saved to theSaved Host List, there are no settings we can use to Reconnect. Once you click on Disconnect, all those settings are now gone. We no longer have any settings for this machine. Therefore, by design, they will be blank settings exactly as you mentioned previously when you try to Reconnect, and the connection will fail.


I would agree with you, however, I have set my default settings to "NT Challenge/Response" and "Use Current Logon Credentials" selected. *Sometimes* when I launch DMRC all settings are blank and "Encrypted Windows Logon" is selected with no machine name as host. So as you can see I don't need any saved settings, I don't want hosts automatically saved, and this should be working but is not.


Re: Disable automatic saved hosts
by bryan on Mon Feb 21, 2011 2:04 pm


Based upon the screen shots you sent to support, the software is working exatly as it should.

In your screen shot there is no Host Entry selected, instead, the Root folder (i.e. Saved Host List) was selected. When MRC starts up it will try to locate and highlight the last entry you connected to. However, when that entry cannot be found (i.e. it was not saved), then the root folder is selected. Therefore, by design, since a folder is currently selected and not a host entry, MRC will not go through all the work of pulling the default host properties just to populate the RC dialog. So the fact that you see Encrypted Windows Logon shown in the RC dialog while a folder is selected when you’ve selected NT Challenge/Response as default doesn’t mean there is an issue with the software.

Also, the fact that you say this only happens *sometimes* means that these other times when this does not happen, there must be an existing host entry already with this same name. So when you click on reconnect, those settings from the existing entry will be used and not default settings.

I hope this helps.


Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
 

Re: Disable automatic saved hosts
by TrafficTech on Fri Mar 04, 2011 11:09 am


I have a few comments to make on the Saved Host List of version 7.3.0. I currently have my settings to "Disable Auto Save" and I have disabled the "Add Only Saved Host Entries to Reconnect List". I seem to have found a little bug in the process.

 

1) If I enter a new temporary entry, it indeed populates in the reconnect list. I can go back and connect to another temporary address and that also goes into the reconnect list. I notice the reconnect list has only unique entries (If I reconnect to a previous entry using the Connect button and not the reconnect button. However, if I use the reconnect drop-down, the entries are no longer unique. Furthermore, when I close and reopen the application, my reconnect entries have vanished, the button is grayed out. This happens every time I use the reconnect button.

2) If I leave the Auto Save feature on, I would like to have an option to have unique entries in the Host List. The list can get long and I don't necessarily want to go through it every time, but I do not want to duplicate my entries either

3) I can understand that if I select a Saved Host entry and decide afterwards I want to connect to a temporary host instead, the Alias from the previous entry is still shown. What I don't like is that if I inadvertently left the alias there and connected, the entry listed in the reconnect drop down shows as ALIAS (HOST). I am more interested in the host and don't really want to see the alias entry (especially since I mistakenly left it in during the temporary entry previously).

 

David M
Systems Admin
Traffic Tech


Re: Disable automatic saved hosts
by bryan on Thu Mar 10, 2011 11:10 am


Hi David,

 

Thanks very much for all the info you provided. This should be now be resolved in v7.4.

Your feedback is appreciated.


Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com

No PDC Icon

$
0
0

Yes, I've seen the June 2011 discussion blaming Microsoft for this same problem but I'm wondering if anything has changed since then. Here's why.

 

Since I upgraded to DRS v9.0.1.247 last week, I have been unable to use it. I continually show No PDC. Yes, when I use Hyena v9.2 and open Computers, they all show.

 

Does this not indicate a problem within DRS? If the problem was due to NETBIOS browsing in Windows Server 2008 shouldn't both DRS and Hyena be unable to access the computer browser?

 

Thanks,

 

Phil

System error: 2184 when checking user logon/logoff informaiton

$
0
0

When I try to use the "display user logon/logoff information" I receive an error:  "Failed to Get User Information.  System Error:2814 System Message: The service has not been started:" 
Error2184.PNG

Dameware install in linux?

$
0
0

Dameware install in linux? If not, have hold map for new version for this system operation. ?


Microsoft Windows Network Empty

$
0
0

Until recently, DRS has been working great. Then I applied the November update to Windows 10 and no the Microsoft Windows Network no longer displays anything in DRS.  I am using version 12 with both hot patches applied.  Other than applying the update nothing had changed in our environment.  I can still find computers through the Active Directory, but it isn't nearly as convenient.  It is particularly troublesome to find the few computers that are not part of the domain.

 

Any suggestions for a fix?

 

Thanks,

Chris

Dameware WIN7 Task Scheduler

$
0
0

Hello everybody,

 

I have in my Dameware Remote Support some Windows 7 clients. If i open the Task Schedueler it won't show me the tasks which are already running on my client.

If I create a task over Dameware it will be shown in Dameware in the Task and Job scheduler and on the client. But it won't show me the already existing tasks on the client neither the ones I create new on the client.
Can someone help how I can see the tasks in Dameware ?

The Dameware mini remote service is not running on XXX

$
0
0

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.


The Dameware mini remote service is not running on XXX.
by Jodi on Mon Jul 09, 2007 5:28 pm


The full text of the message is The Dameware mini remote service is not running on xxx. Would you like to start it now? I answer OK and get "Unable to Start Service; System Error 2; The system cannot find the file specified. It started on a server this morning. After doing a random check of the computers on our domain I have found that it is random. Some machines are ok, some I can't access. It is not dependent on a specific operating system. Can anyone help?

 

Thanks.
________________________________________
Re: The Dameware mini remote service is not running on XXX.
by bryan on Mon Jul 09, 2007 6:02 pm


Hello Jodi,

 

Exactly what version of the MRC Client Agent Service do you have installed on these remote machines (right-click on DWRCS.EXE, then select the Version Tab)?

Also, what Operating System and Service Pack level is installed on these remote machines? Are these 64-bit Operating Systems?

Also, did you recently install, or update definitions for any type of Anti-Virus or Anti-Spyware software? Because it could be that this software is mistakenly flagging some of the files within the MRC CLient Agent Service.

 

Microsoft's System Error: 2 basically means File Not Found. So based upon this error it appears that some of the necessary files for the MRC CLient Agent Service may have been deleted on these remote machines somehow. They also could have been mistakenly flagged and deleted by some type of Anti-Virus or Anti-Spyware software on your machine or your network as well.

Therefore, the first thing you need to do is verify that all the files are still there in the System32 folder on the remote machine (SYSWOW64 for 64-bit Operating Systems). If any files are missing, then this is the source of your issues, and you'll have to track down exactly what deleted these files on these machines.

 

For a listing of necessary files, you can take a look at the following KB article on our website:

 

How To Manually Install or Remove the Mini Remote & NT Utilities Client Agents
http://www.dameware.com/support/kb/article.aspx?ID=100000

Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com

________________________________________
Re: The Dameware mini remote service is not running on XXX.
by Jodi on Mon Jul 09, 2007 7:12 pm


Bryan,

 

The DWRCS.exe file is version 5.1.1.0. We are using 32 bit computers running Windows 2000 SP4 and Windows XP SP2.

One of the machines we can't access has the DWRCS.exe file but it has been renamed to DWRCS.exe.manifest. Some of the machines don't have the file at all.

Our AntiVirus software is Computer Associates and it checks for updates each day and will download them to the individual computers if needed on a daily basis.

Thanks for your help.

 

Jodi
________________________________________
Re: The Dameware mini remote service is not running on XXX.
by bryan on Tue Jul 10, 2007 3:30 am


Hi Jodi,

 

You're welcome.
One of the machines we can't access has the DWRCS.exe file but it has been renamed to DWRCS.exe.manifest
Actually, the manifest file is a valid file, so it appears your DWRCS.EXE file has been deleted, not renamed. So this is most likely due to your CA eTrust software, either within the Anti-Virus portion of the software, or within the Pest Patrol portion of the software.

Therefore, all you should have to do is define an exception for our software in either portion of the CA software (AV or Pest Patrol) so it does not delete any files for our software.

I hope this helps.


Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com

________________________________________
Re: The Dameware mini remote service is not running on XXX.
by bryan on Tue Jul 10, 2007 9:33 am


Hi again Jodi,

 

Here is some additional information I received from another customer on this. Many thanks go out to Zac T. for this information. Hopefully this will help you out:
Here is what worked for me…

 

1. Log into the E-Trust management console
2. click on the policy management tab at the top of the page
3. under the policies section, change the application dropdown to eTrust PestPatrol and the Type dropdown to Pest Exclusion
4. on the right side of the page change the tab to “Pests” and click the change button.
a. In the box type DameWare and click search.
b. Highlight “DameWare Mini Remote Control” and hit the over arrow so it moves to the Excluded Pests box on the right
c. To close click the “Set Exclude List” button at the bottom
d. Click apply in the Policy Management tab to save those settings
5. Change the tab to “Paths”
a. Click Add
b. Type “Program Files\DameWare Development\DameWare NT Utilities” in the box and click “Set Exclude Path”. (I also added “c:\windows\system32\dwrcs.exe” but I don’t know if that is necessary)
c. Click apply in the Policy Management tab to save the settings
6. the last step is to assign the group to these policies
a. click the “Assign” button
b. navigate to the organization to assign the policy to, move the group to the right and click “assign branches”

that should do it…

This is what worked for us and I hope it helps someone else out that might experience similar issues.

 

Zac T
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com

________________________________________
Re: The Dameware mini remote service is not running on XXX.
by Jodi on Tue Jul 10, 2007 12:11 pm


Thanks Bryan and Zac T,

We excluded the dwrcs.exe in Pest Patrol and everything is back to normal (at least on the computers we have copied the file back to). Your help has been much appreciated.

Jodi
________________________________________
Re: The Dameware mini remote service is not running on XXX.
by bryan on Wed Jul 11, 2007 6:53 pm


Hi Jodi,

 

You're absolutely welcome, and thanks so much for letting us know this resolved your issues.
I'm glad we were able to help out.

 

Best Regards,
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com

________________________________________
Re: The Dameware mini remote service is not running on XXX.
by wuliping0011 on Fri Apr 16, 2010 8:39 pm


Bryan wrote:Hello Jodi,

 

Exactly what version of the MRC Client Agent Service do you have installed on these remote machines (right-click on DWRCS.EXE, then select the Version Tab)?

Also, what Operating System and Service Pack level is installed on these remote machines? Are these 64-bit Operating Systems?

Also, did you recently install, or update definitions for any type of Anti-Virus or Anti-Spyware software? Because it could be that this software is mistakenly flagging some of the files within the MRC CLient Agent Service.

Microsoft's System Error: 2 basically means File Not Found. So based upon this error it appears that some of the necessary files for the MRC CLient Agent Service may have been deleted on these remote machines somehow. They also could have been mistakenly flagged and deleted by some type of Anti-Virus or Anti-Spyware software on your machine or your network as well.

Therefore, the first thing you need to do is verify that all the files are still there in the System32 folder on the remote machine (SYSWOW64 for 64-bit Operating Systems). If any files are missing, then this is the source of your issues, and you'll have to track down exactly what deleted these files on these machines.

For a listing of necessary files, you can take a look at the following KB article on our website:

 

How To Manually Install or Remove the Mini Remote & NT Utilities Client Agents
http://www.dameware.com/support/kb/article.aspx?ID=100000Replica chanle handbags

though that i know a lot.thanks

Logged in Users to the machine

$
0
0

Hello everybody,

 

we are running the actual version of DameWare 11.1.0.170 for our Administrators to have some smooth remote support ability.

There is only one problem/missed function, we want to have.

 

We want to see which user is logged into a machine, when we are checking our "Active Computer list" in DameWare.

Also I know this can be done via the Active Directory (add to the description field on the computer), but then we have some double maintenance.

 

Is there any functionality on DameWare to check which user is logged into. For example is DameWare able to readout the "User and Groups" of Windows or the registry to check whether which user has logged in today?

 

 

 

Thanks for any answer.

Hopefully you can help me.

 

Best Regards,

Philipp

No Active Directory Administration Interfaces Detected

$
0
0

I recently upgraded to Windows 10 and DRS 12. Since then I have been getting this in the information tab. On the Browser tab I don't get anything under the Microsoft Windows Network like I used to.

I am new to this forum and trying to search didn't seem to bring anything up. I appreciate any help anyone can be as I don't think I am getting full usage of DRS 12 because of this issue.

Thank You.

System error: 2184 when checking user logon/logoff informaiton

$
0
0

When I try to use the "display user logon/logoff information" I receive an error:  "Failed to Get User Information.  System Error:2814 System Message: The service has not been started:" 
Error2184.PNG

System Error: 5 Acces is Denied ??? [I PUT LOGS]

$
0
0

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.

 

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


Microsoft Windows Network Empty

$
0
0

Until recently, DRS has been working great. Then I applied the November update to Windows 10 and no the Microsoft Windows Network no longer displays anything in DRS.  I am using version 12 with both hot patches applied.  Other than applying the update nothing had changed in our environment.  I can still find computers through the Active Directory, but it isn't nearly as convenient.  It is particularly troublesome to find the few computers that are not part of the domain.

 

Any suggestions for a fix?

 

Thanks,

Chris

DRS Client Agent service by MSI or GPO?

$
0
0

Hello,

 

We just recently upgraded from DameWare Remote Control 7 to DRS 9 with DRC 10. I'm enjoying the potential here, but some features don't work without the DRS Client Agent service running on the remote machine.

 

This seems to be installed OK on some of our straggler Win XP workstations, but on Win 7 workstations, trying to use features like RCmd Console doesn't work, and the automatic service activation feature doesn't work, either.

 

I have just seen this howto for using the batch feature to install/activate the DRS agent service, and it worked when I tested it on some of the problem Win 7 workstations.

 

However, we'd much prefer to be able to activate this by Group Policy, so we don't need to micromanage workstations as we deploy them.

 

I've searched around through the MSI Builder settings for anything to add "install DRS client agent service" or "activate" it, and done my best with Google, too, but I can't figure out if there's a way to do this. Does anyone have a way to install & activate the DRS Client Agent service by Group Policy and/or MSI? We already have a policy set up to install the Mini Remote agent with a built MSI, and that works great.

 

Thanks!


Errors while viewing event log on remote station

$
0
0

While attempting to review event details on the event log feature for a client on the same subnet in the office, DRS crashes. I believe I have installed the hotfix correctly.

 

This event is from the DRS server:

 

Log Name:      Application

Source:        Application Error

Date:          11/2/2015 11:17:54 AM

Event ID:      1000

Task Category: (100)

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      Sigma169

Description:

Faulting application name: DNTU.exe, version: 12.0.0.514, time stamp: 0x5625287f

Faulting module name: ntdll.dll, version: 6.1.7601.18939, time stamp: 0x55afd843

Exception code: 0xc0000005

Fault offset: 0x00044649

Faulting process id: 0x6c4

Faulting application start time: 0x01d1118796e2ecd2

Faulting application path: C:\Program Files (x86)\SolarWinds\DameWare Remote Support\DNTU.exe

Faulting module path: C:\Windows\SysWOW64\ntdll.dll

Report Id: a6b14526-8185-11e5-8a8f-1013ee0693f7

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Application Error" />

    <EventID Qualifiers="0">1000</EventID>

    <Level>2</Level>

    <Task>100</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2015-11-02T17:17:54.000000000Z" />

    <EventRecordID>25778</EventRecordID>

    <Channel>Application</Channel>

    <Computer>Sigma169</Computer>

    <Security />

  </System>

  <EventData>

    <Data>DNTU.exe</Data>

    <Data>12.0.0.514</Data>

    <Data>5625287f</Data>

    <Data>ntdll.dll</Data>

    <Data>6.1.7601.18939</Data>

    <Data>55afd843</Data>

    <Data>c0000005</Data>

    <Data>00044649</Data>

    <Data>6c4</Data>

    <Data>01d1118796e2ecd2</Data>

    <Data>C:\Program Files (x86)\SolarWinds\DameWare Remote Support\DNTU.exe</Data>

    <Data>C:\Windows\SysWOW64\ntdll.dll</Data>

    <Data>a6b14526-8185-11e5-8a8f-1013ee0693f7</Data>

  </EventData>

</Event>

 

Any idea what may be causing this? I am not sure where to report a possible bug.

Dameware and RDC/Terminal Service Sessions

$
0
0

Hi All,

 

Currently evaluating Dameware DRS 11.0.0.1003 for our environment. In past employments I have relied heavily on Dameware for my Team's support operations. I was hoping to employ this tool here in my current role, but I have come across something that may be a deal breaker. The majority(about 2/3) of our staff here use WYSE terminals and login to a session on our Terminal Servers (WIndows 2008 R2). We have been connecting via RDC to the Terminal Server, login then using the TS Admin Tools launch a remote session to the Staff member. I was hoping to use Dameware DRS to actively connected to the session directly. Does anyone know if this is possible and if so how?

 

Many thanks.

 

Logan

Dameware 11.2 - Authentication

$
0
0

We are currently testing deployment of Dameware Mini Remote Control to the client systems.

 

With the previous version (11.1), we were able to add a new line to the registry location [HKEY_LOCAL_MACHINE\Software\DameWare Development\Mini Remote Control Service\Settings]

"UseCurrentLogonCredentials"=dword:00000001

This would automatically select 'Windows NT Challenge/Response' and check the 'Use Current Logon Credentials'

 

This is not seems to be the case with the new version 11.2. When I add the link, nothing seems to happen.

 

Can anyone suggest solution?


Thanks.

Viewing all 14036 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>