Filter
Top Products
46 Troubleshooting
• If both the server and the client system are in a domain, perform the
following steps:
– Verify that the domain administrator account has administrator
privileges for both systems.
– If you are using IT Assistant on the server system, run the IT Assistant
ConfigServices utility (
configservices.exe
found in the
/bin
directory of
the IT Assistant installation directory). Configure IT Assistant to run
under the account of the domain administrator, and verify that DCOM
and CIM are enabled. See the
IT Assistant User’s Guide
for information.
– If you are using IT Assistant, use the domain administrator account to
configure the IT Assistant subnet discovery for the client system. If
the system has already been discovered, remove the system from the
list of discovered systems, configure subnet discovery for it, and then
rediscover it. See the
IT Assistant User’s Guide
for information.
• If both the server and the client system are in a workgroup (not in a
domain), perform the following steps:
– If the client system is running the Microsoft
®
Windows
®
XP
Professional or Windows XP Professional x64 Edition operating
system and the server is running Windows 2000, verify that Service
Pack 2 or later is installed on the server.
– If the client system is running a version of Windows XP and is not part
of a domain, edit the registry to allow remote connection with
administrative privileges.
NOTICE: Back up your system data files before making changes to the
registry. Incorrectly editing the registry may render your operating system
unusable.
To make the registry change on the client system, click
Start
→
Run
,
then type
regedit
, and click
OK
. In the
Registry Editor
window,
navigate to:
My Computer\HKEY_LOCAL_MACHINE\SYSTEM\
CurrentControlSet\Control\Lsa
Set the
forceguest
value to
0
(by default it is
1
). Unless you modify
this value, the user remotely connecting to the system has guest
privileges only, even if the supplied credentials should provide
administrative privileges.