I have test the scan with the credential slave. I set it up with my local systemuser an pw. when i test the IP in the credential tab on the UI, the test is successful.

then i start a new discovery but: Result NoAccess (Host identification failure – no HostInfo)

getDeviceInfo* OK my user
getHostInfo* NoAccessMethod Discovered Host Information
getInterfaceList* NoAccessMethod 0 Discovered Network Interfaces found

what’s wrong?

Welcome to the forums.

If you look in the “How do I” forum then there are a couple of sticky posts on debugging slave access.

Generally if the credential test in the UI works but discovery does not it’s that the remote host is firewalled in some way.

With a slave a couple of other things may going on. First a slave cannot discover the host it runs on effectivelly so if the IP you are scanning is also the one the slave is running on that may be the issue – it’s a common gotcha in small test lab set ups.

Second if the target is modern windows (vista onwards) and you are using a credential slave you may have to relax some of the registry settings to get remote admin rights as they are restricted to an ad authenticated account.

If you use the search box top right of the site, click on the icon to it’s right and change it to ‘Forum’ you can search the forum. There are several slave debugging threads that will help you.

Second if the target is modern windows (vista onwards) and you are using a credential slave you may have to relax some of the registry settings to get remote admin rights as they are restricted to an ad authenticated account.

I test it on my Workstation. ADDM in a VM and my Client is a Windows 7 Pro.
No, i have done some config and the last thing doens’t work is the getInterfaceList*

the both scripts failed
psexec.exe
WMI getInterfaceList

i copied the psexec in the windows directory, but this doesn’t fix the problem?!

all other problems i find in some other topics using the search box – thank you

wiht the AD slave it work – love it:-)

Glad you got it going. The AD slave is always the preferred route for easier deployment as it works with the AD environment.