How to Log On to a "Networked" Computer

[Monty Python]

Working on a computer. Symptoms are immediately after typing username & PW, machine loads user's settings, then immediately logs off. This happens in all boot "modes" (safe, etc...)

MS has a fix that requires one to

• Log on to a networked computer.
• Run Regedit.exe
• Point your cursor to HKEY_LOCAL_MACHINE
• Select File > Connect Remote Registry
• Type computer name (infected computer)
• Navigate to the following location in registry of destination or infected computer

I can't tell if the bad computer is supposed to logon to a good one, or the other way around.

In any case, I don't know how to "log on to a networked computer"

Any help appreciated.

[johnwill]

This is a symptom of the login process being confused about what the boot drive is. There is a simple fix that doesn't require any remote registry manipulation if this is the case.

• Boot from an MS-DOS boot disk (floppy or CD).
• Type FDISK /MBR at the command prompt.
• Reboot the Windows machine.

You can obtain the required boot disk image from one of the sites below.

Some MS-DOS Boot Disks for all occasions.

NetBootDisk - Universal Network Boot Floppy

AllBootDisks

AllBootDisks ISO CD Images

BootDisk

[Monty Python]

Thanks johnwill. I thought this was going to do it but I ran into a problem.

I burned a bootable WinMe CD from an image file downloaded from one of the links provided.

Ran "fdsk /mbr" it ran without error. Rebooted; same problem. Logon, immediate logoff.

Booted again with the CD, and discovered that the DOS apparantly does not "see" the HD.

A: - WinMe (supposed to be a floppy drive)
B: - wants me to insert a floppy
C: - WinMe also
D: - Ramdrive
E: - 2nd CD/DVD device (no disk inserted)


I tried F: through J:, no HD found.

When I run just "fdisk", it shows a 15 Gbyte primary DOS partition. The HD is 160 Gbytes, and I am wondering if it's large size is a problem with WinMe DOS.

Also, there was some verbage about NTFS support, so I assume WinMe has it.

Note: This is a single, IDE HD correctly configured as (I tried both) Cable Select and/or Master, on the end of the IDE cable with the jumper set correctly.

[johnwill]

I'm not sure why you tried the ME disk, that would be my last choice.

Of course, this "fix" only deals with the specific issue I mentioned, if you have some other registry corruption issue, it may not do anything.

Have you considered a repair installation of Windows? How to Perform a Windows XP Repair Install

[Monty Python]

I chose WinMe as it was the latest boot DOS offered. I wanted to make sure that it had NTFS and large HD support.

Last night I booted from an XP CD and ran "fixmbr". Does this do the same repair as "fdisk /mbr" ? I also ran "fixboot".

Neither of which worked, the problem continues.

The client says they have an Install Disk that came with the computer. I assume it's an OEM as the computer is an eMachine. I'm reluctant to have the bring the install disk primarily due to the hassle. I'm also hoping to avoid a Repair Install. And also this is an interesting problem and since the client is in no particular hurry I'd like to use the situation as a learning experience.

The Client machine has a floppy drive, but mine is non-functional so whatever boot media I use needs to be CD. What would be the best CD-boot DOS to use to try to get the 160 Gbyte NTFS HD recognized in DOS ?

Also I'm interested in trying to run a Remote Registry edit, if that's possible. I've bee researching and cannot find any clear instruction on how to do this.

[johnwill]

None of those disks has NTFS support, but it's not needed for the task of writing the MBR.

I did the repair once using the network login. This of course presumes the target machine has networking capability and is configured correctly. If the Microsoft procedure fails, I'm not sure if you'll ever do this networked.

If you have the energy, you can build a BART-PE boot disk and edit the registry off-line: http://windowsxp.mvps.org/peboot.htm

[Monty Python]

None of those disks has NTFS support, but it's not needed for the task of writing the MBR.

How can this be ? The data has to be somewhere, and if the NTFS drive isn't recognized, how can any data be written/modified ?

I've played with Bart's before.

I've always wondered where/how the registry was stored. I have an Ubuntu Live CD; will that work ? I read a post a while back that gave some reg edits to fix a problem that has these symptoms (whether it's the exact same problem of course is the question).

What I would REALLY like to do is disable the entire logon stage of the boot process. I can't help but think that if it didn't force you to logon, it couldn't force the logoff. (Simple-minded I know but you never know.)

Does it violate forum rules to ask about how to do this ?

[johnwill]

Look at the specifications for 98/ME, NTFS is not supported. The MBR is not contained in the filesystem, it's the first sector of the first track on the disk.

I don't know that the Ubunti Live Boot CD can write to NTFS filesystems, so I'd be looking for a Windows based solution.