Windows sysinternals

Basic Connectivity
Chapter 6 Pstools 175
Unless you specify an IP address, name resolution needs to work. If DNS is not available,
NetBIOS over TCP (NBT) might suffice, but it requires that 137 UDP, 137 TCP, 138 UDP, and
139 TCP be opened on the firewall of the target system.
Some of the utilities require that the administrative Admin$ share be available. This requires
that file and print sharing be enabled (the Workstation service locally and the Server service
on the target system), that the firewall not block the ports that are needed to support file
and printer sharing, and also that “simple file sharing” be disabled.
Some of the utilities require that the Remote Registry service be running on the target
system. (The table at the end of the chapter lists which ones require this feature.) Note that in
the newer versions of Windows, this service is not configured for automatic start by default.
It therefore needs to be manually started or configured for automatic start before some of
these tools will work.
User Accounts
Most of the utilities require administrative rights. Before Windows Vista and User Account
Control, administrative accounts were straightforward. If the account was a member of the
Administrators group, everything run by that account also ran with full administrative rights.
Successfully authenticating to the computer with an account in the Administrators group
allowed full control over the computer.
Windows Vista introduced User Account Control, which (among other things) pioneered the
concept of a user account that could be both an administrative account and a standard user
account. This account type is sometimes called Protected Administrator. The idea is that programs
started by the user will run with standard user privileges, and that for a program to
run with full administrative rights, the user must explicitly approve the elevation. Programs
running as the user should not be able to programmatically approve the elevation for the
user or otherwise bypass the interaction. If they could, software developers would take those
shortcuts and continue to write programs that required administrative rights rather than
write software for standard users.
Network loopback is one of the automatic elevation paths that Windows Vista blocks. As
described in Knowledge Base article 951016, if a network connection is established to a
remote computer using a local account that is a member of the Administrators group, it
connects only with standard user privileges. Because it is not an interactive logon, there
is no opportunity to elevate to full administrator. Domain accounts are not subject to this
restriction.
www.it-ebooks.info