Common error messages

Last modified by Sabrina V. on 2025/05/20 09:40

Error messages

Possible causes

"Network path not found"
  • The target computer is not enabled
  • The computer name is not resolved correctly
  • Firewall blocks access/locks port or firewall should be enabled correctly:
    • RPC: 135 (TCP/UDP)
    • SMB/CIFS: 137 - 139, 445 (TCP/UDP)
  • Administrative share (Admin$) does not exist
  • Interprocess communication share (IPC$) does not exist
  • Share service is not started
  • WinSock or TCP/IP stack defective (e.g. due to uninstalling a firewall)
    • Microsoft KB entry
"Connection refused"
  • Access denied, either no listening service or locked port (2107 TCP)
  • If necessary, check whether the port is being used by another program (e.g., Messaging Queue)
"System Error. Code: 5."
  • This error can occur in Windows Vista and later if a client is not in a domain and UAC is enabled.
    • To use the local user via the network without a domain, you must create a new key in the registry. Open the command prompt (with administrator rights) and enter Regedit. In the registry editor, navigate to:
    • HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\system and add the DWORD value (32-bit) LocalAccountTokenFilterPolicy with the value 1. After restarting, you can now use the local user via the ACMP Console and, for example, install the ACMP Agent.
    • Alternatively, you can also enter the following command via a command prompt (with administrator rights):
    • reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\system /v LocalAccountTokenFilterPolicy /t REG_DWORD /d 1 /f

 

© Aagon GmbH 2025
Besuchen Sie unsere neue Aagon-Community