lucas.shelton@drake.edu Posted April 7, 2016 Share Posted April 7, 2016 We are having issues with VPN users connecting to a file share in our datacenter. I'm pretty confident my firewall isn't preventing access, but to prove to the server team I'd like to do some pen testing through the firewall and into the file share. Do I point the nmap to the domain controllers, EMC storage device, firewall, ?? I'm a novice at pen testing so please bare with me. Also, using Zenmap how do I scan specific ports? Quote Link to comment Share on other sites More sharing options...
lucas.shelton@drake.edu Posted April 8, 2016 Author Share Posted April 8, 2016 Well I've figured out I can use nmap to enumerate smb shares, but I'm getting error messages. See below: Host script results: | smb-enum-shares: | note: ERROR: Enumerating shares failed, guessing at common ones (NT_STATUS_ACCESS_DENIED) | account_used: <blank> | ADMIN$: | warning: Couldn't get details for share: NT_STATUS_ACCESS_DENIED | Anonymous access: <none> | C$: | warning: Couldn't get details for share: NT_STATUS_ACCESS_DENIED | Anonymous access: <none> | D$: | warning: Couldn't get details for share: NT_STATUS_ACCESS_DENIED | Anonymous access: <none> | FILES: | warning: Couldn't get details for share: NT_STATUS_ACCESS_DENIED | Anonymous access: <none> | IPC$: | warning: Couldn't get details for share: NT_STATUS_ACCESS_DENIED | Anonymous access: READ | NETLOGON: | warning: Couldn't get details for share: NT_STATUS_ACCESS_DENIED | Anonymous access: <none> | PUBLIC: | warning: Couldn't get details for share: NT_STATUS_ACCESS_DENIED | Anonymous access: <none> | USERS: | warning: Couldn't get details for share: NT_STATUS_ACCESS_DENIED |_ Anonymous access: <none> Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.