Home | Site Map | Cisco How To |  Net How To | Wireless | Local Search | Forums | Services | Donations | Careers | About Us | Contact Us|

Troubleshooting administrative shares are missing

Situation:

1. You may receive the following error messages on domain computers during logon or during the times when they try to join the domain:

The domain password you supplied is not correct, or access to your logon server has been denied.

The logon server did not recognize your domain password, or access to the server has been denied.

No logon server is available to service the logon request.

The following error occurred attempting to join the domain 'Domain_Name': The network name cannot be found.

2. When you try to access or view the remote computer by using a UNC path, a mapped drive, the net use command, the net view command, or by browsing the network in Network Neighborhood or My Network Places, you may receive the following errors:

The server is not configured for transactions.

System error 53 has occurred. The network path was not found.

Domain_Name is not accessible.  

3. You may receive the following errors when you try to perform administrative tasks on a domain controller:

Naming Information cannot be located because: Login attempt failed.

Object Picker cannot open because no locations from which to choose objects can be found.

4. When you try to run Netdom.exe to find the FSMO roles, you may receive an error message that is similar to the following:

Unable to update the password. The value provided as the current password is incorrect.

5. When you try to run Dcdiag.exe, you may receive an error message that is similar to the following:

Failed with 67: The network name cannot be found

The results from Dcdiag.exe may also list LDAP bind errors that are similar to the following:

LDAP bind failed with error 1323.

6. When you try to run Netdiag.exe, you may receive an error message that is similar to the following:

DC list test . . . . . . . . . . . : Failed

Failed to enumerate DCs by using the browser. [NERR_BadTransactConfig]

7. After installing WINS, the WINS service may not start or the WINS console may display a red X, or both.

8. Event iD 4311 may be logged in Event Viewer:

Event ID: 4311

Event Source: NetBT

Event Type: Error

Description: Initialization failed because the driver device could not be created

7. The Terminal Services Licensing console may not start, and you may receive an error message that is similar to the following:

•           No Terminal Services license server is available in the current domain or workgroup. To connect to another license server, click license, click connect and click the server name.

•           The network address is invalid

8. Services for Macintosh may not start with Event ID 7024, 10001, 10021, 10027.

Event Type: Error

Event Source: MacFile

Event Category: None

Event ID: 10021

User: N/A

Description: The File Server for Macintosh service was unable to contact a domain controller to obtain domain information.

Event Type: Error

Event Source: MacFile

Event Category: None

Event ID: 10027

User: N/A

Description: An error occurred while initializing the File Server for Macintosh service. A Server Helper thread could not be initialized. The specific error code is in the data.

Event Type: Error

Event Source: MacFile

Event Category: None

Event ID: 10001

User: N/A

Description: Unable to start the File Server for Macintosh service. A system specific error has occurred. The error code is in the data

Event Type: Error

Event Source: Service Control Manager

Event Category: None

Event ID: 7024

User: N/A

Description: The File Server for Macintosh service terminated with service-specific error 1722.

Causes: These issues may occur after a malicious or spyware program removes the administrative shares on a windows computer. You can use "net share" command to check that the administrative shares are active. if yes, you must have admin$, C$ and IPC$.

Resolutions: To fix it, please follow these steps;

a.         Click Start, click Run, type regedit, and then press ENTER.

b.         Locate and then click the following registry sub-key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters

c.         If the AutoShareServer and AutoShareWks DWORD values in the LanmanServer\Parameters sub-key are configured with a value data of 0, change that value to 1.

Note If these values do not exist, you do not have to create them because the default behavior is to automatically create the administrative shares.

d.         Quit Registry Editor.

f.         Restart the computer.

Note: you may want to scan the computer for any virus or spyware.

Post your questions, comments, feedbacks and suggestions

Contact a consultant

Related Topics

Can't access sharing because of Norton