in

Event ID 1058 (Windows cannot access the file gpt.ini)

Hello,

I am having Event ID 1058 in my log appearring many times...

----------------------------------------------------------------------
Event Type:      Error
Event Source:      Userenv
Event Category:      None
Event ID:      1058
Date:            18/4/2008
Time:            3:04:23 ¼¼
User:            NT AUTHORITY\SYSTEM
Computer:      ZEUS
Description:
Windows cannot access the file gpt.ini for GPO CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=domain,DC=local. The file must be present at the location <\\domain.local\sysvol\domain.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>. (Configuration information could not be read from the domain controller, either because the machine is unavailable, or access has been denied. ). Group Policy processing aborted.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
----------------------------------------------------------------------

I tried the solution at http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/SBS_Small_Business_Server/Q_22023184.html but nothing changed. Error still appears...

Anyone any ideas?

Thanks
Movie Stars

Solution: Event ID 1058 (Windows cannot access the file gpt.ini)

ChiefIT... I think you meant me, not Jay_Jay?

All of your background info is interesting... but its really not applicable here.  First, I don't think we're talking about a VPN connection at all.

Second, WINS is configured automatically on an SBS... it just needs to be set in the TCP/IP advanced properties.

But I think I actually see what's going on here... something I missed before...

stako_ex is using a routable IP subnet.  

stako_ex... how did you come about to be using 192.0.0.x?  That's not a legal private network IP Subnet.

The second octet MUST be "168", so you can use 192.168.0.x if you like, but I recommend that you use 192.168.16.x to avoid any possible conflicts with VPN connections which are coming from home networks that may be using 192.168.0.x.

To fix this, you should first enable NetBIOS over TCP/IP.

Then run the Change Server IP Address Wizard, found in the Internet and Email section of the Server Management Console.  
An overview of what this will accomplish is here:  
http://techsoeasy.spaces.live.com/blog/cns!AB2725BC5698FCB8!303.entry

Jeff
TechSoEasy