10061 System Error
Contents |
Troubleshooting the "Connection Refused" Message - TCP/IP Error 10061 The information in this article applies to: DameWare Mini Remote Control 10061 is a TCP/IP error which implies that there is goldmine system error 10061 a TCP/IP connectivity issue between the local and remote machines. Here is a possible
Dameware System Error 10061
method of troubleshooting the 10061 error in regard to the Mini Remote Control Service. Please make sure that you have administrative rights
System Error 10061 Winsock Connection Refused
to the remote workstation. Reset the default TCP port usage(6129) on both local and remote workstations. Within DWMRC, select the desired host entry and click on the Settings button. On the Remote Options Tab, verify that
Error Code 404 System Error Code 10061
the Port number is set to 6129 (must match the Remote Client Agent Service port exactly) To ensure the default port usage(6129) on the remote workstsation: Stop the DameWare Remote Client Agent Service. Delete DWRCS.INI from the system32 directory. Delete the registry entry for the client agent HKEY_LOCAL_MACHINE\SOFTWARE\DameWare Development\DWRCS. Restart the service. Other things to consider: 1) There may be some other application using the same port. Stop the service on the dameware no connection could be made because the target machine actively refused it remote machine and run "netstat -a". There should be nothing listening on port 6129. If there is, then something else is using the port. If not, then restart the service on the remote machine and you should have something (DMRC) listening on port 6129. 2) If we have verified Step 1 and we get to this point with no resolution, then there must be a Microsoft name resolution/routing problem, because we can query and install a service using the installed protocol via Windows API but we can't communicate with the computer using plain TCP/IP via sockets. This means there is a problem with your network setup. You should be able to duplicate this problem outside of the DNTU/Mini Remote Control software. a) Verify the IP address and hostname on the remote computer are correct. b) Attempt to map to a shared resource on the remote computer. If it fails, then resolve any network connectivity problems, and try the Mini Remote Control again. Additional information: General Network Configuration & Implementation Issues http://www.dameware.com/support/kb/article.aspx?ID=300005 Using DameWare Development Products in Conjunction with Windows XP Service Pack 2 http://www.dameware.com/support/kb/article.aspx?ID=300068 Troubleshooting the "Connection Refused" Message - TCP/IP Error 10061 http://www.dameware.com/support/kb/article.aspx?ID=300006 Knowledgebase Article: #300006 Category: Troubleshooting O/S Info: Microsoft Windows 95/98/Me Microsoft Windows NT4/2000/Xp/2003/Vista/2008/Windows 7 Last Revised: Wednesday, September 29, 2004 Keywords:
Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time error 10061 sql server Help Create a Freelance Project Hire for a Full Time Job Ways error 10061 connection refused to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor tcp connection refused error Services Groups Website Testing Store Headlines Experts Exchange > Questions > Dameware System Error: 10061 Want to Advertise Here? Solved Dameware System Error: 10061 Posted on 2012-05-08 Networking http://support.dameware.com/kb/article.aspx?ID=300006 1 Verified Solution 6 Comments 2,855 Views Last Modified: 2012-05-10 I'm having an issue remotely connecting to a laptop on my internal network through Dameware. I am receiving this error: System Error: 10061 System Message: No connection could be made because the target machine actively refused it. I can ping it and see it on the https://www.experts-exchange.com/questions/27708164/Dameware-System-Error-10061.html network and have already disabled the firewall and enable file and printer sharing on the remote laptop. Both Windows 7 OS can anyone help? 0 Question by:crp0499 Facebook Twitter LinkedIn Google LVL 6 Best Solution byairborne1128 You can also try this... 10061 is a TCP/IP error which implies that there is a TCP/IP connectivity issue between the local and remote machines. Here is a possible method of troubleshooting the 10061 Go to Solution 6 Comments LVL 6 Overall: Level 6 Networking 2 Message Expert Comment by:airborne11282012-05-08 Check the agent settings on the client. 0 Message Active today Author Comment by:crp04992012-05-08 And what should these setting be? I have verified the port and looks to be correct. 0 LVL 6 Overall: Level 6 Networking 2 Message Expert Comment by:airborne11282012-05-08 If those settings are correct, check to see that the dameware agent is started on the client. If it is and still not working, remove and re-add the agent. 0 LVL 6 Overall: Level 6 Networki
Manager (IPAM)ipMonitorKiwi CatToolsKiwi Syslog ServerLog & Event Manager (LEM)Mobile AdminNetFlow Traffic Analyzer (NTA)Network Configuration Manager (NCM)Network Performance Monitor (NPM)Network Topology Mapper (NTM)Patch ManagerServer & Application Monitor (SAM)Serv-U FTP & MFTStorage Resource Monitor (SRM)User Device Tracker (UDT)Virtualization ManagerVoIP & Network Quality Manager (VNQM)Web https://thwack.solarwinds.com/thread/57185 Help Desk (WHD)Web Performance Monitor (WPM)Blogs & GroupsGroupsCommunity ConversationsEvents & WebcastsFederal & GovernmentFun & GeekyJob BoardSolarWinds Certified ProfessionalsSpread the WordTHWACK EMEAUser ExperienceBlogsAnnouncementsGeek SpeakProduct BlogSolarWinds User GroupsSolarWinds LabContests & MissionsThwack StoreFree Tools http://help.globalscape.com/help/cuteftp8/Socket_errors_10060_10061_10064_10065.htm & Trials Log inRegisterGetting StartedSearchSearchCancelBrowseContentPeopleForums & GroupsStoreHomeNewsPeopleError: You don't have JavaScript enabled. This tool uses JavaScript and much of it will not work correctly without it enabled. Please turn JavaScript back on system error and reload this page. Please enter a title. You can not post a blank message. Please type your message and try again. More discussions in DameWare DRS All PlacesApplication & ServerDameWare DRS 0 Replies Latest reply on Jun 11, 2013 8:58 AM by neetha.edwin Unable to log onto remote machines using DameWare 5.5.0.2 neetha.edwin Jun 11, 2013 8:58 AM Note: This is a system error 10061 topic brought over from DameWare Forums which has been closed. If you wish to engage in this discussion, just comment here.Unable to log onto remote machines using DameWare 5.5.0.2by threeofspades on Thu Sep 13, 2007 5:34 amHi 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: 10061System 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.2by bryan on Fri Sep 14, 2007 11:13 amHello threeofspades,Are you sure you're specifying the correct TCP port in your Host settings?Is the MRC Client Agent Service already installed & r
the presence of firewall or anti-virus software on the local computer or network connection. Either can block the ports needed to make a successful FTP connection to the remote server. For a regular FTP session, either disable the firewall or anti-virus software or configure them to allow CuteFTP to establish an FTP session over ports 20 and 21. Consult the documentation or help file for your specific firewall or antivirus software product for instructions. Usually the manufacturer of the device or software will also have specific instructions available on their Web site. If you continue to receive the same error after insuring ports 20 and 21 are open, contact the administrator of the site you are trying to connect to. For more error code information, refer to Knowledge Base article 10140 at http://kb.globalscape.com. WSAETIMEDOUT (10060) 10060 is a connection-timeout error that usually appears when the client does not receive a response from the server for a specific command. This error often occurs when you try to connect in PASV mode to a server that prefers PORT for data connections. If you see an error log similar to the one below, in the Site Properties of the problem site, click the Type tab, then change the Data Connection Type to Use PORT. COMMAND:> PASV 227 Entering Passive Mode (xxx,xx,xxx,xx,x,xxx). COMMAND:> LIST STATUS:> Connecting ftp data socket xxx.xx.xxx.xx:xxxx... ERROR:> Can't connect to remote server. Socket error = #10060. ERROR:> Failed to establish data socket. If you still receive a 10060 error, the server may be trying to send a listing for a very large directory (with many thousands of files) causing the client to time-out while waiting. Try increasing the time-out value in the Global Options dialog box (Tools > Global Options > Transfer > Reconnect and resume in [ n ] seconds if nothing received ) to a higher value, such as 45 or 60 seconds. The connection fails due to an error or timeout. Verify that the destination IP address is correct. Increase the connection timeout threshold under Global Settings > Connection. Switch to the opposite data connection type (PASV or PORT) under Site Settings > Type tab. Verify that the problem is not local by trying to connect to an alternate server. If a server name was used, verify it resolves to the correct address. If using a local server table for server name resolution, check to see that it doesn't resolve to an obsolete address. Try pinging the address. (See Troubleshooting Tips for details.) If you are using a router, verify the router is up and ru