Superdata
asked on
Group Policy issue - Event ID 1058
Hi,
Have several machines on a network (less than half of them) that are having issues with group policy.
Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1058
Date: Date
Time: Time
User: User_Name
Computer: Computer_Name
Description: Windows cannot access the file gpt.ini for GPO CN={31B2F340-016D-11D2-945 F-00C04FB9 84F9},CN=P olicies,CN =System,DC =domainnam e,DC=com . The file must be present at the location <\\domainname.com\sysvol\d omainname. com\Polici es\{31B2F3 40-016D-11 D2-945F-00 C04FB984 F9}\gpt.ini>. (Error_Message). Group Policy processing aborted. For more information, see Help and Support Center at http://support.microsoft.com.
If i try and browse from the affected PC to that share location, i get: The network path was not found.
If i replace the domainname with the IP address of the SBS server, it works fine....
So DNS issue... well, i put a static entry into the hosts file, when i ping the domain name it resolves fine. Still cannot access the share by UNC.
Other network shares by UNC work fine, so that has me a little confused....
Thoughts?
Have several machines on a network (less than half of them) that are having issues with group policy.
Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1058
Date: Date
Time: Time
User: User_Name
Computer: Computer_Name
Description: Windows cannot access the file gpt.ini for GPO CN={31B2F340-016D-11D2-945
If i try and browse from the affected PC to that share location, i get: The network path was not found.
If i replace the domainname with the IP address of the SBS server, it works fine....
So DNS issue... well, i put a static entry into the hosts file, when i ping the domain name it resolves fine. Still cannot access the share by UNC.
Other network shares by UNC work fine, so that has me a little confused....
Thoughts?
ASKER
"Is the SBS server is set to use itself for primary DNS,"
yes, with forwarders for external resolution.
"Are the affect clients using the SBS server for primary DNS? "
All clients on the network use the SBS Server for DNS. Many are not having issues.
"Are the non-affected clients and affected clients getting different group policies?"
No
On the SBS server, go to C:\Windows\SYSVOL\domain\P olicies and verify the policy files exist.
They exist and as stated from the clients, browsing to \\ip address\sysvol\ etc works fine.
"Having to use the IP address makes me think the problem clients are not using the SBS as their DNS server."
DHCP is giving out the correct address, i have also statically set the DNS Server to the correct address and no change.
I have pulled one off the affected PCs off the domain and put it back on after deleting the computer account also, no change.
I have logged into the PC with domain administrator priv in a new profile, also no change.
What gets me, is that i can ping the domain name and it resolves to the server correctly. Slap in a UNC path into explorer and it cant resolve. This pointed me to file and print sharing, but its enabled, netbios is enabled too. Other UNC paths work.... whiskey tango foxtrot...
yes, with forwarders for external resolution.
"Are the affect clients using the SBS server for primary DNS? "
All clients on the network use the SBS Server for DNS. Many are not having issues.
"Are the non-affected clients and affected clients getting different group policies?"
No
On the SBS server, go to C:\Windows\SYSVOL\domain\P
They exist and as stated from the clients, browsing to \\ip address\sysvol\ etc works fine.
"Having to use the IP address makes me think the problem clients are not using the SBS as their DNS server."
DHCP is giving out the correct address, i have also statically set the DNS Server to the correct address and no change.
I have pulled one off the affected PCs off the domain and put it back on after deleting the computer account also, no change.
I have logged into the PC with domain administrator priv in a new profile, also no change.
What gets me, is that i can ping the domain name and it resolves to the server correctly. Slap in a UNC path into explorer and it cant resolve. This pointed me to file and print sharing, but its enabled, netbios is enabled too. Other UNC paths work.... whiskey tango foxtrot...
I have also faced the same issue in our environment and below link resolved my issue. You can also try this its safe and really usefull but must take a backup of the registry before applying these registry settings.
http://technet.microsoft.com/en-us/library/cc758453%28WS.10%29.aspx
http://support.microsoft.com/kb/314494
http://technet.microsoft.com/en-us/library/cc758453%28WS.10%29.aspx
http://support.microsoft.com/kb/314494
ASKER
did not fix :(
noticed the netbios helper service is completely missing from the pc, not sure if this has something to do with it? netbios is enabled under the TCP/IP section.
noticed the netbios helper service is completely missing from the pc, not sure if this has something to do with it? netbios is enabled under the TCP/IP section.
ASKER
Tried both parts, rebooted, no change :(
ASKER
Fully patched windows manually, killed the antivirus, killed windows firewall, updated the driver for the wireless card.
What gets me, is that \\domaincontroller\sysvol = fine, \\ip\sysvol\ = fine, \\domain\sysvol\ doesnt work.
but when you ping the domain name it resolves. what does using the domain name in the unc path do differently?
The machine in question was in the last few months moved to a new domain name, from blehdom.local to bleh.local
after some testing tonight i have some new symptoms. It can only browse unc paths on machines that existed on the old domain (the DC has the same server name as the old server in the previous domain) our new SQL and TS Server shares cannot be seen by anything other than IP Address.
This has to be some form of strange DNS Issue.
Here is the print out of DNS from the machine:
Windows IP Configuration
Host name . . . . . . . . . . . . . : PC05
Primary DNS Suffix . . . . . . . : bleh.local (correct)
Node Type. . . . . . . . . . . . . . : Hybrid
IP Routing . . . . . . . . . . . . . . : No
WINS Proxy Enabled . . . . . : No
DNS Suffix Search List . . . . : bleh.local
. BLEH.local (why its got both has me a little confused, possibly the issue?)
Ethernet adapter Wireless Network Connection:
Connection-specific DNS Suffix . : BLEH.local
Description . . . . . . . . . . . . . . . . . : Linksys Wireless-G PCI Adaptor
Physical Address . . . . . . . . . . . . : 00-12-17-8A-A5-37
Dhcp Enabled . . . . . . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . . : Yes
IP Address . . . . . . . . . . . . . . . . . : 10.0.0.105
Subnet Mask . . . . . . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . . . . . : 10.0.0.1
DHCP Server . . . . . . . . . . . . . . . . : 10.0.0.3
DNS Servers . . . . . . . . . . . . . . . . : 10.0.0.3
Primary WINS Server. . . . . . . . . . : 10.0.0.3
I have cleaned out the hosts file, lmhosts etc
What gets me, is that \\domaincontroller\sysvol = fine, \\ip\sysvol\ = fine, \\domain\sysvol\ doesnt work.
but when you ping the domain name it resolves. what does using the domain name in the unc path do differently?
The machine in question was in the last few months moved to a new domain name, from blehdom.local to bleh.local
after some testing tonight i have some new symptoms. It can only browse unc paths on machines that existed on the old domain (the DC has the same server name as the old server in the previous domain) our new SQL and TS Server shares cannot be seen by anything other than IP Address.
This has to be some form of strange DNS Issue.
Here is the print out of DNS from the machine:
Windows IP Configuration
Host name . . . . . . . . . . . . . : PC05
Primary DNS Suffix . . . . . . . : bleh.local (correct)
Node Type. . . . . . . . . . . . . . : Hybrid
IP Routing . . . . . . . . . . . . . . : No
WINS Proxy Enabled . . . . . : No
DNS Suffix Search List . . . . : bleh.local
. BLEH.local (why its got both has me a little confused, possibly the issue?)
Ethernet adapter Wireless Network Connection:
Connection-specific DNS Suffix . : BLEH.local
Description . . . . . . . . . . . . . . . . . : Linksys Wireless-G PCI Adaptor
Physical Address . . . . . . . . . . . . : 00-12-17-8A-A5-37
Dhcp Enabled . . . . . . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . . : Yes
IP Address . . . . . . . . . . . . . . . . . : 10.0.0.105
Subnet Mask . . . . . . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . . . . . : 10.0.0.1
DHCP Server . . . . . . . . . . . . . . . . : 10.0.0.3
DNS Servers . . . . . . . . . . . . . . . . : 10.0.0.3
Primary WINS Server. . . . . . . . . . : 10.0.0.3
I have cleaned out the hosts file, lmhosts etc
ASKER
Sorry for the semi incoherent post, its getting late :P
Maybe the WINS server got messed up. In most cases there is no more need to use WINS. For a test remove the WINS server config from a PC and recheck.
If its the problem and you can live without WINS, remove it from your DHCP config and remove WINS server from your SBS server.
If not, delete all entries the WINS database or at least check if the domain name netries point to the correct servers..
If its the problem and you can live without WINS, remove it from your DHCP config and remove WINS server from your SBS server.
If not, delete all entries the WINS database or at least check if the domain name netries point to the correct servers..
ASKER
Removed wins settings, re-added, checked the entries were all correct on the server and no issue there that i can see.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
no other answer comes close.
Are the non-affected clients and affected clients getting different group policies? On the SBS server, go to C:\Windows\SYSVOL\domain\P
Having to use the IP address makes me think the problem clients are not using the SBS as their DNS server.