7 replies
by bfilmfan
Are you logging on the system as a domain administrator or an administrator on the local system of the remote box?
I have seen issues where the adminsitrators do not have rights to scan the registry remotely that caused issues with MBSA.
Also are you using the latest edition, which is 1.2.1? http://www.microsoft.com/technet/security/tools/mbsahome.mspx
by barryvg
Poster rated this answer.
by barryvg
by d'solve it
Hi,
You must be getting a message like this:
Domain\PC (192.168.16.222) User is not an administrator on the scanned machine.
Try this:
Create a user (lets say MBSUSR) on a PC. Grant this user full admin privileges. Go to another PC and create the same user (MBSUSR) and grant full admin privileges here too.
Now go to the first PC and run MBSA and scan your local PC. Next run the scan on the other PC. If this works, you know for sure that it's a security/user rights issue.
Good Luck
by d'solve it
Another thing though, go thorough the ?readme.html? file in the ?Help? directory under the ?#firewall? section. Certain conditions must be met to allow remote scanning :
? The Server service, Remote Registry service, and File & Print Sharing services must be enabled.
? Remote machine scans are performed using TCP ports 139 and 445. In a multi-domain environment, where a firewall or filtering router separates the two networks, TCP ports 139 and 445 and UDP ports 137 and 138 must be open in order for MBSA to connect and authenticate to the remote network being scanned. You must allow these ports on the remote Windows Firewall.
Good Luck
by barryvg
Poster rated this answer.
by barryvg
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending