No i was asking about Hydra throwing false positives for web forms and telnet Does it occur frequently because i have faced instances where where hydra throws like two or three valid user names and passwords for a web form or telnet and then when i put them in they are not valid.
Second, your choice of the http-get module may be invalid for the target. Looking at Hydra's source code, http-get will use HTTP basic authentication by default. If the target web server does not use basic authentication and returns a non-error HTTP status code (e.g. 200 OK) when Hydra attempts authentication, Hydra will think that the authentication was successful. It's also possible that while no authentication exists on '/', another path may require it.
In some cases, Nessus can test default accounts and known default passwords. This can cause the account to be locked out if too many consecutive invalid attempts trigger security protocols on the operating system or application. By default, this setting is enabled to prevent Nessus from performing these tests.
If an admin has completed the first two steps and the remote desktop connection credentials are still not working, the next step is to make sure the administrator account has not been locked out. Most organizations configure their Active Directory environments to automatically lock accounts after too many invalid login attempts as an RDP security measure. 153554b96e