GuidesLearn Windows XP Professional: Troubleshooting the Windows XP Professional Setup (Page 4)...

Learn Windows XP Professional: Troubleshooting the Windows XP Professional Setup (Page 4) Page 4




WindowsdebugNetSetup.log
Logs activity when computers join domains or workgroups. (This entire log
was only 7KB, so I copied all of it)

01/07 23:40:03
—————————————————————–
01/07
23:40:03 NetpValidateName: checking to see if ‘WORKGROUP’ is valid as type 2
name
01/07 23:40:03 NetpCheckNetBiosNameNotInUse: for ‘WORKGROUP’ returned:
0x858
01/07 23:40:03 NetpCheckNetBiosNameNotInUse for ‘WORKGROUP’ [ Workgroup
as MACHINE] returned 0x858
01/07 23:40:03 NetpValidateName: name ‘WORKGROUP’
is valid for type 2
01/07 23:40:03
—————————————————————–
01/07
23:40:03 NetpValidateName: checking to see if ‘WORKGROUP’ is valid as type 2
name
01/07 23:40:03 NetpCheckNetBiosNameNotInUse: for ‘WORKGROUP’ returned:
0x858
01/07 23:40:03 NetpCheckNetBiosNameNotInUse for ‘WORKGROUP’ [ Workgroup
as MACHINE] returned 0x858
01/07 23:40:03 NetpValidateName: name ‘WORKGROUP’
is valid for type 2
01/07 23:40:03
—————————————————————–
01/07
23:40:03 NetpValidateName: checking to see if ‘WORKGROUP’ is valid as type 2
name
01/07 23:40:03 NetpCheckNetBiosNameNotInUse: for ‘WORKGROUP’ returned:
0x858
01/07 23:40:03 NetpCheckNetBiosNameNotInUse for ‘WORKGROUP’ [ Workgroup
as MACHINE] returned 0x858
01/07 23:40:03 NetpValidateName: name ‘WORKGROUP’
is valid for type 2
01/07 23:40:03
—————————————————————–
01/07
23:40:03 NetpDoDomainJoin
01/07 23:40:03 NetpMachineValidToJoin:
‘P42GH’
01/07 23:40:03 NetpGetLsaPrimaryDomain: status: 0x0
01/07 23:40:03
NetpMachineValidToJoin: status: 0x0
01/07 23:40:03 NetpJoinWorkgroup: joining
computer ‘P42GH’ to workgroup ‘WORKGROUP’
01/07 23:40:03 NetpValidateName:
checking to see if ‘WORKGROUP’ is valid as type 2 name
01/07 23:40:03
NetpCheckNetBiosNameNotInUse: for ‘WORKGROUP’ returned: 0x858
01/07 23:40:03
NetpCheckNetBiosNameNotInUse for ‘WORKGROUP’ [ Workgroup as MACHINE] returned
0x858
01/07 23:40:03 NetpValidateName: name ‘WORKGROUP’ is valid for type
2
01/07 23:40:03 NetpSetLsaPrimaryDomain: for ‘WORKGROUP’ status:
0x0
01/07 23:40:03 NetpControlServices: open service ‘NETLOGON’ failed:
0x424
01/07 23:40:03 NetpJoinWorkgroup: status: 0x0
01/07 23:40:03
NetpDoDomainJoin: status: 0x0
01/07 23:40:46
—————————————————————–
01/07
23:40:46 NetpValidateName: checking to see if ‘P42GH’ is valid as type 1
name
01/07 23:40:46 NetpCheckNetBiosNameNotInUse for ‘P42GH’ [MACHINE]
returned 0x0
01/07 23:40:46 NetpValidateName: name ‘P42GH’ is valid for type
1
01/08 01:00:12
—————————————————————–
01/08
01:00:12 NetpValidateName: checking to see if ‘DRINKOFTEN’ is valid as type 2
name
01/08 01:00:15 NetpCheckNetBiosNameNotInUse for ‘DRINKOFTEN’ [ Workgroup
as MACHINE] returned 0x0
01/08 01:00:15 NetpValidateName: name ‘DRINKOFTEN’
is valid for type 2
01/08 01:00:15
—————————————————————–
01/08
01:00:15 NetpValidateName: checking to see if ‘DRINKOFTEN’ is valid as type 2
name
01/08 01:00:18 NetpCheckNetBiosNameNotInUse for ‘DRINKOFTEN’ [ Workgroup
as MACHINE] returned 0x0
01/08 01:00:18 NetpValidateName: name ‘DRINKOFTEN’
is valid for type 2
01/08 01:00:18
—————————————————————–
01/08
01:00:18 NetpValidateName: checking to see if ‘DRINKOFTEN’ is valid as type 2
name
01/08 01:00:21 NetpCheckNetBiosNameNotInUse for ‘DRINKOFTEN’ [ Workgroup
as MACHINE] returned 0x0
01/08 01:00:21 NetpValidateName: name ‘DRINKOFTEN’
is valid for type 2
01/08 01:00:21
—————————————————————–
01/08
01:00:21 NetpDoDomainJoin
01/08 01:00:21 NetpMachineValidToJoin:
‘P42GH’
01/08 01:00:21 NetpGetLsaPrimaryDomain: status: 0x0
01/08 01:00:21
NetpMachineValidToJoin: status: 0x0
01/08 01:00:21 NetpJoinWorkgroup: joining
computer ‘P42GH’ to workgroup ‘DRINKOFTEN’
01/08 01:00:21 NetpValidateName:
checking to see if ‘DRINKOFTEN’ is valid as type 2 name
01/08 01:00:24
NetpCheckNetBiosNameNotInUse for ‘DRINKOFTEN’ [ Workgroup as MACHINE] returned
0x0
01/08 01:00:24 NetpValidateName: name ‘DRINKOFTEN’ is valid for type
2
01/08 01:00:24 NetpSetLsaPrimaryDomain: for ‘DRINKOFTEN’ status:
0x0
01/08 01:00:24 NetpJoinWorkgroup: status: 0x0
01/08 01:00:24
NetpDoDomainJoin: status: 0x0
01/26 09:14:56
—————————————————————–
01/26
09:14:56 NetpValidateName: checking to see if ‘WORKGROUP’ is valid as type 2
name
01/26 09:14:59 NetpCheckNetBiosNameNotInUse for ‘WORKGROUP’ [ Workgroup
as MACHINE] returned 0x0
01/26 09:14:59 NetpValidateName: name ‘WORKGROUP’ is
valid for type 2
01/26 09:14:59
—————————————————————–
01/26
09:14:59 NetpDoDomainJoin
01/26 09:14:59 NetpMachineValidToJoin:
‘P42GH’
01/26 09:14:59 NetpGetLsaPrimaryDomain: status: 0x0
01/26 09:14:59
NetpMachineValidToJoin: status: 0x0
01/26 09:14:59 NetpJoinWorkgroup: joining
computer ‘P42GH’ to workgroup ‘WORKGROUP’
01/26 09:14:59 NetpValidateName:
checking to see if ‘WORKGROUP’ is valid as type 2 name
01/26 09:15:02
NetpCheckNetBiosNameNotInUse for ‘WORKGROUP’ [ Workgroup as MACHINE] returned
0x0
01/26 09:15:02 NetpValidateName: name ‘WORKGROUP’ is valid for type
2
01/26 09:15:02 NetpSetLsaPrimaryDomain: for ‘WORKGROUP’ status:
0x0
01/26 09:15:02 NetpJoinWorkgroup: status: 0x0
01/26 09:15:02
NetpDoDomainJoin: status: 0x0
01/26 09:15:28
—————————————————————–
01/26
09:15:28 NetpValidateName: checking to see if ‘DRINKOFTEN’ is valid as type 2
name
01/26 09:15:31 NetpCheckNetBiosNameNotInUse for ‘DRINKOFTEN’ [ Workgroup
as MACHINE] returned 0x0
01/26 09:15:31 NetpValidateName: name ‘DRINKOFTEN’
is valid for type 2
01/26 09:15:31
—————————————————————–
01/26
09:15:31 NetpDoDomainJoin
01/26 09:15:31 NetpMachineValidToJoin:
‘P42GH’
01/26 09:15:31 NetpGetLsaPrimaryDomain: status: 0x0
01/26 09:15:31
NetpMachineValidToJoin: status: 0x0
01/26 09:15:31 NetpJoinWorkgroup: joining
computer ‘P42GH’ to workgroup ‘DRINKOFTEN’
01/26 09:15:31 NetpValidateName:
checking to see if ‘DRINKOFTEN’ is valid as type 2 name
01/26 09:15:34
NetpCheckNetBiosNameNotInUse for ‘DRINKOFTEN’ [ Workgroup as MACHINE] returned
0x0
01/26 09:15:34 NetpValidateName: name ‘DRINKOFTEN’ is valid for type
2
01/26 09:15:35 NetpSetLsaPrimaryDomain: for ‘DRINKOFTEN’ status:
0x0
01/26 09:15:35 NetpJoinWorkgroup: status: 0x0
01/26 09:15:35
NetpDoDomainJoin: status: 0x0
01/26 09:16:30
—————————————————————–
01/26
09:16:30 NetpValidateName: checking to see if ‘P42GHZ’ is valid as type 1
name
01/26 09:16:33 NetpCheckNetBiosNameNotInUse for ‘P42GHZ’ [MACHINE]
returned 0x0
01/26 09:16:33 NetpValidateName: name ‘P42GHZ’ is valid for type
1
01/26 09:16:33
—————————————————————–
01/26
09:16:33 NetpValidateName: checking to see if ‘P42GHZ.’ is valid as type 5
name
01/26 09:16:33 NetpValidateName: name ‘P42GHZ.’ is valid for type
5

Windowsrepairsetup.log
Provides information that is used by the Recovery Console. A subsection of
mine is below. (The full size was 204KB)

[Paths]
TargetDirectory =
“WINDOWS”
TargetDevice =
“DeviceHarddisk0Partition3”
SystemPartitionDirectory =
“”
SystemPartition =
“DeviceHarddisk0Partition1”
[Signature]
Version =
“WinNt5.1”
[Files.SystemPartition]
NTDETECT.COM =
“NTDETECT.COM”,”b28f”
ntldr =
“ntldr”,”3a7b2″
[Files.WinNt]
WINDOWSsystem32driverskbdclass.sys =
“kbdclass.sys”,”e756″
WINDOWSsystem32driversmouclass.sys =
“mouclass.sys”,”8cd9″
WINDOWSsystem32driversusbuhci.sys =
“usbuhci.sys”,”11ded”
WINDOWSsystem32driversusbport.sys =
“usbport.sys”,”22ffd”
WINDOWSsystem32driversusbd.sys =
“usbd.sys”,”40af”
WINDOWSsystem32drivershidparse.sys =
“hidparse.sys”,”acd7″
WINDOWSsystem32drivershidclass.sys =
“hidclass.sys”,”88de”
WINDOWSsystem32driversusbhub.sys =
“usbhub.sys”,”ee45″
WINDOWSsystem32driversintelide.sys =
“intelide.sys”,”dec0″
WINDOWSsystem32driverspci.sys =
“pci.sys”,”1a257″
WINDOWSsystem32driversoprghdlr.sys =
“oprghdlr.sys”,”b001″

(The whole remainder of the file
looked as it does above, detailing drivers and path information for the whole
system).

Well, that’s a wrap for this
week.

In next week’s installment I will
begin focusing the weekly articles on the next section of material which centers
on Implementing and Conducting Administration of Resources of Windows XP
Professional, the first of which will cover monitoring, managing, and
troubleshooting access to files and folders.

Until then, best of luck in your
studies and please feel free to contact me with any questions on my column, and
remember,

“Weak passwords trump strong security.”


Jason Zandri
[email protected]


www.2000trainers.com

Latest Posts

Related Stories