Win7 Domain Client accessing WinXP share

For some reason Microsoft makes it a royal piain in the ass for a Win7 domain client to attach to a
WinXP share...  I had a Win7 Enterprise client on a domain attaching to a shared WinXP Pro SP3 client on that same domain.. nothing worked.  I tried the following...

On XP shared client, disabled simple file sharing.
On Win7 attaching client, set Administrative Tools... Local Security Policy... Security Options...  Network Security LAN Manager Authentication Level to "use LM & LMNT as well as negotiate LMNTv2".  Also set Network Discovery to ON and allowed lower level encryption support.

When that all still didnt work... I did the following...

On the XP shared client, I created a new network share...
I then created a local account called shareaccess with local Administrator group priviledge and added that user to the shares access list, having with full permissions.
On the Win7 attaching client, I created a Generic Credential pointing to the IP address of the XP machine, using the shareaccess account and password I just created.

Worked like a charm.

Fix bad CDROM driver in WinXP (and other O/S)

If you encounter a situation where your CDROM hardware verifies good, but
you have a yellow triangle in device manager stating your hardware
is not available...

1) Close all open programs
2) Click on Start, Run, and type REGEDIT and press Enter
3) Click on the plus signs (+) next to the following folders
* HKEY_LOCAL_MACHINE
* SYSTEM
* CurrentControlSet
* Control
* Class
* {4D36E965-E325-11CE-BFC1-08002BE10318}

4) This folder is the DVD/CD-ROM Drive Class Description in the registry. Look for any of the following names in the right hand column.
* UpperFilters
* LowerFilters
* UpperFilters.bak
* LowerFilters.bak

5) If any of the above keys shown in step 4 are listed, right-click on them and choose Delete
6) After deleting the keys, close the Registry Editor
7) Reboot your computer



http://en.kioskea.net/forum/affich-25531-help-i-have-uninstalled-my-cd-dvd-rom-driver

Issue with boot.ini SIGNATURE entry

Windows 2000's boot.ini ARC syntax adds the signature() statement. See NT's boot.ini for a writeup of Windows NT's ARC syntax. The signature() syntax added to Windows 2000 is equivalent to the scsi() syntax, but adds support for Plug and Play architecture. For Plug and Play operating systems, the SCSI controller number instance may vary each time you start the operating system, especially if you add new SCSI controller hardware after Setup is finished. An example of the signature( ) syntax:
signature(8c468c12)disk(1)rdisk(0)partition(2)\winnt="Windows 2000"

In Windows 2000, the signature() syntax instructs the NTLDR program to locate the drive whose disk signature matches the value in the signature parentheses, no matter which SCSI controller number the drive is connected to. The signature() value is extracted from the physical disk's Master Boot Record (MBR). The signature value is a hexadecimal number that is written to the MBR during the text-mode portion of Setup, or it is written by an installation of Microsoft Windows NT version 4.0 or earlier. Yes, its that signature written to the disk the first time NT / W2K / XP accesses the hard drive using Disk Manager.

Windows 2000 / XP uses the signature( ) syntax in the boot.ini if one of the following conditions exists:

Your PC's BIOS or the IDE controller does not support int13 BIOS extensions
The int13 BIOS extensions are disabled.
The installation partition is larger than 7.8 GBs.
The ending cylinder number for the installation partition is higher than 1024.
Your SCSI controller's BIOS is disabled and thus int13 BIOS calls cannot be used during the boot process.
There is an important gotcha! if the signature gets corrupted or changed. Now the boot.ini can not find the correct partition to boot from and you get the following error:

Windows 2000 could not start because of a computer disk hardware configuration problem. Could not read from selected boot disk. Check boot path and disk hardware. Please check the Windows 2000 documentation about hardware disk configuration and your hardware disk configuration and your hardware reference manuals for additional information.

You can try replacing the signature(#####) portions of the statement with multi(0) and the disk should boot fine in most cases.

Large Drive Formatting in XP or 2000

To see a larger size hard drive >137 GB in Windows 2000 you must have SP4 installed and the EnableBigLba flag set to 1 in the registry...

http://support.microsoft.com/kb/305098

For Windows XP, you must have SP1 installed with EnableBigLba set to 1...

http://support.microsoft.com/kb/303013

Both O/Ss expect a 48bit LBA-compatible BIOS.