Event ID 1058, 1059 and 1030

Chicago Area Laptop for rent: $35 per day plus $10 for additional day

Event ID 1058, 1059 and 1030

Event ID 1058 is Group Policy related issue. Normally, there are two symptoms: "network path not found" and "access denied". The fixing may be different depending on the issue. To troubleshoot it, try the following suggestions first. If it doesn’t work, call Microsoft for the hotfix.

Netlogon and DFS services are started on both domain controllers and clients.
Domain controllers have the read and apply rights to the Domain Controllers Policy.
NTFS file system permissions and share permissions are set correctly on the Sysvol share.
DNS entries are correct for the domain controllers.
Make sure there are no FRS issues if you have more than one DC.
Not firewall/NAT blocks the traffic between the DC and clients.

The following Case Studies may help too.

Case 1: The client has a Windows 2003 server running Exchange 2003 as Front-End server in the different subnet connect to the DC through a Cisco router. The router blocks most ports except 25 and 110.

Case 2: The client received this error every one hour after disabled TCP/IP NetBios help service.

Case 3: One of Windows has the same issue because the Microsoft Distributed File System (DFS) client is disabled

Case 4: The client received this error every 5 minutes in event log along with error 1059 after upgraded from Windows 2000 to Windows 2003. To solve this issue, set the following attributes in the Default Domain Controller Policy:
1. Network Access: Let Everyone permissions apply to anonymous users = "Enabled".
2. Network Access: Shares that can be accessed anonymously -> Add SYSVOL to the list.

Case 5: The client got this Event error after renamed the DC. To fix the problem, run DCGPOFIX on the DC followed by a reboot.

Case 6: the client has thss issue after they setup ISA prevent LDAP requests from reaching services on the domain server.

Case 7: The client was running multihomed computer in the DC. There is a name resolution issue in the DC. Refer to Name resolution on DC

Case 8: As per Microsoft: "This behavior occurs if the SMB signing settings for the Workstation service and for the Server service contradict each other. When you configure the domain controller in this way, the Workstation service on the domain controller cannot connect to the domain controller's Sysvol share. Therefore, you cannot start Group Policy snap-ins. Also, if SMB signing policies are set by the default domain controller security policy, the problem affects all the domain controllers on the network. Therefore, Group Policy replication in the Active Directory directory service will fail, and you will not be able to edit Group Policy to undo these settings".