Figure 13.14: In Windows XP and Windows Server 2003, the Uninstall button is
disabled when you select TC/IP protocol in the Local Area Connection Properties
window
What if you want to reset the TCP/IP stack by returning it to its state when the operating
system originally was installed? In Windows XP and Windows Server 2003, you can't
remove and then reinstall it. However, there is a convenient way to work around this
problem. To do so, you must use the netsh (NetShell) utility, which provides a command-
line interface for configuring and monitoring Windows XP or Windows Server 2003
networking.
In Windows XP, netsh utility provides a reset command, which rewrites registry keys
related to TCP/IP. Consequently, you will get the same result as removing the TCP/IP
stack and then reinstalling it.
To reset TCP/IP settings in the registry, go to the command line (Start | Run, type cmd,
and press <Enter> then issue the following command:
netsh interface ip reset [log_file_name]
Instead of log_file_name, use the name of the log file where the action will be recorded.
If you don't specify the full path to the log file, it will be created in the current directory.
The command will reset TCP/IP settings stored under the following registry keys:
HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\
HKLM\SYSTEM\CurrentControlSet\Services\DHCP\Parameters\

Note If a log file already exists, the new log will be appended to the end of existing file.
In addition, the contents of the log file depend on the system configuration. There
may be times when no actions will be logged. This usually happens if the TCP/IP
registry settings have not been changed since the original Windows XP or Windows
Server 2003 installation.
Troubleshooting Service Startup Problems
Sometimes, you may encounter a service that can't start because of a logon failure. If this
happens, the system might display error messages. Then, the next time you start the
system, the following error messages may be in the system event log:

servers/client workstations. If the problem takes place at the controller of an Active
Directory domain, proceed as follows:
1. Start the Active Director Users and Computers Microsoft Management Console
(MMC) snap-in.
2. Right-click the organizational unit (OU) in which the user right to log on as a
service was granted. By default, this is in the Domain Controllers OU.
3. Right-click the container, then click Properties.
4. On the Group Policy tab, click Default Domain Controllers Policy, then click
Edit. This starts Group Policy Object Editor.
5. Expand the Computer Configuration object by clicking the plus sign (+) next to
the policy object. Under the Computer Configuration object, expand Windows
Settings, then expand Security Settings.
6. Expand Local Policies and click User Rights Assignment (Fig. 13.16
).

Figure 13.16: Restoring the right for the user account to log on as service
7. In the right pane, right-click Log on as a service (Fig. 13.17
).

Figure 13.17: The Log on as service Properties dialog
8. Add the user to the policy and click OK.
9. Quit Group Policy Object Editor, close Group Policy Properties, then close the
Active Directory Users and Computers MMC snap-in.
If the problem arises at the member server or a standalone computer, take the following
steps:
1. Start the Local Security Settings MMC snap-in.
2. Expand Local Policies and click User Rights Assignment.
3. In the right pane, right-click Log on as a service, then click Properties. The Log
on as service Properties window will open.
4. Add the user to the policy and click OK.