Home / server / Questions / 379376
Accepted
makerofthings7
Asked: 2012-04-14 19:30:55 +0800 CST

ADMIN$ and other shares not working remotely on XP machines

  • 772

I'm trying to use ADMT to migrate several XP machines to a new domain and the utility (nor command line) is able to access the admin$ share or any drive share.

I've added the required registry key (HKCurrent\Services\LanMan\Param) for both servers and workstation admin sharing, rebooted the PC and still am unable to access it.

How can I access the admin share on these PCs?

If it helps, this machine used to have McAfee installed, and the Windows firewall enabled. I stoppped both of them and the machine is still not allowing me to access it remotely by a drive$ share.

firewall migration windows-server-2003 windows-xp admt

2 Answers

  1. Best Answer

    First, as silly as it might sound, consider running an offline virus scan using a boot CD such as Kaspersky's rescue CD. Any time administrative shares go missing, especially when the proper registry keys exist, my radar is immediately tweaked for some kind of malicious software. It can't hurt to pop a CD in and let it sit, crunching away for a few minutes or hours.

    Second, go into your adapter's properties and make sure that "File and Printer Sharing for Microsoft Networks" is enabled.

    Third, let the flailing begin! You can reset your TCP/IP stack which sometimes clears up weirdness like this. As administrator, run netsh int ip reset resetlog.txt to reset the TCP/IP stack. Next reset winsock2 with netsh int reset or just reset the catalog with netsh winsock reset catalog. I will leave a thorough investigation of what those things to as an exercise for the reader.

    Fourth, if you don't have the time to spend tracking down the root cause, consider an XP repair install. Note that you will need to reapply updates after the repair install. Existing files are kept in tact, however a backup before this is performed can't hurt.

    • 2
    1. Add the registry key to the HKEY_LOCAL_MACHINE (HKLM) hive instead of HKEY_CURRENT_USER.
    2. Make sure the Server service is started. Try to restart it if it is already running.
    3. To make sure Windows Firewall is not blocking anything, enable logging of dropped packets and try to access the shares again. Examine the firewall log to see if anything gets dropped.
      (Run -> firewall.cpl -> Advanced -> Security Logging -> Settings -> Log dropped packets)

    If the ADMIN$ share exists but is still unavailable, try removing it and reboot (this should recreate it).

    • 1