Re: "Windows cannot access the file gpt.ini for GPO" - Events 1058 and 1030 on XP client only.
From: Kevin D. Goodknecht [MVP] (admin_at_nospam.LSAOL.COM)
Date: 02/15/04
- Next message: Ace Fekay [MVP]: "Re: "Windows cannot access the file gpt.ini for GPO" - Events 1058 and 1030 on XP client only."
- Previous message: Chris Simmons: "Re: "Windows cannot access the file gpt.ini for GPO" - Events 1058 and 1030 on XP client only."
- In reply to: Chris Simmons: ""Windows cannot access the file gpt.ini for GPO" - Events 1058 and 1030 on XP client only."
- Next in thread: Chris Simmons: "Re: "Windows cannot access the file gpt.ini for GPO" - Events 1058 and 1030 on XP client only."
- Reply: Chris Simmons: "Re: "Windows cannot access the file gpt.ini for GPO" - Events 1058 and 1030 on XP client only."
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 15 Feb 2004 14:11:32 -0600
In news:c0hv201b3nn5nsi3pg410dhg10m3a96onv@4ax.com,
Chris Simmons <newsgroup.replies@netchris.com> posted a question
Then Kevin replied below:
Follow up set to microsoft.public.win2000.dns
: Hello:
:
: I see this is a somewhat common problem, however I've seen nothing
: specific to my problem that works. I'm getting the following event
: (along with a subsequent event 1030 referencing the 1058) on the XP
: client:
:
: *** START EVENT TEXT ***
: Windows cannot access the file gpt.ini for GPO
: CN={GUID},CN=Policies,CN=System,DC=Domain,DC=com. The file must be
: present at the location
: <\\Domain.com\sysvol\Domain.com\Policies\{GUID}\gpt.ini>. (The network
: path was not found. ). Group Policy processing aborted.
:
: For more information, see Help and Support Center at
: http://go.microsoft.com/fwlink/events.asp.
: *** END EVENT TEXT ***
:
: This is a small network with a DC (W2K server), a mail server (W2K
: server), and one laptop client (XP). The error occurs only on the XP
: client.
:
: I have seen messages suggesting a problem with DNS, however nothing
: specific as to what problem to look for. The base host (A) records
: for domain.com point to the IPs of the DC's internal (192.168.1.2) and
: external NICs. When I ping domain.com from any machine, I get what I
: expect: 192.168.1.2. However, at the client, I try this:
: dir \\domain.com\SYSVOL
: and I get "The network path was not found". On the mail server and
: DC, I get what is expected:
:
: Volume in drive \\Domain.com\SYSVOL has no label.
: Volume Serial Number is XXXX-XXXX
:
: Directory of \\Domain.com\SYSVOL
:
: 06/27/2002 05:20p <DIR> .
: 06/27/2002 05:20p <DIR> ..
: 06/27/2002 05:20p <JUNCTION> Domain.com
: 0 File(s) 0 bytes
: 3 Dir(s) 20,294,721,536 bytes free
:
:
: I have re-installed the OS on the laptop client and the same issue
: remains, so I'm guessing this is something I need to fix on the domain
: side.
:
: Can someone please help?
This is one problem with Multihomed DCs in order to cure this you need to do
a couple of things.
1. Set the binding order, by going into network properties Control panel, in
the Advanced menu select Advanced Settings. Make sure the internal NIC is at
the top of the connections list and the Client for MS networks and File
sharing are only bound on the internal interface.
2. You will need to make registry entries to stop the creation of the blank
records for the external interface for both the domain name and the global
catalog record. You will then have to manually create these two blank
records. There is a KB describing this but I'm unable to find it but here is
the reg entry, you must use regedt32 to make this entry.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters
Registry value: DnsAvoidRegisterRecords
Data type: REG_MULTI_SZ
LdapIpAddress
GcIpAddress
3. On the Interfaces tab of the DNS server properties set the DNS listener
address to the internal IP.
4. On an XP Client you need to upgrade the GPO by following this KB article
Upgrading Windows 2000 Group Policy for Windows XP
http://support.microsoft.com/?id=307900
What happens is DNS returns the IP of the external interface and file
sharing is not enabled on the interface and LDAP won't pass NAT.
-- Best regards, Kevin D4 Dad Goodknecht Sr. [MVP] Hope This Helps ============================ -- When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue. To respond directly to me remove the nospam. from my email. ========================================== http://www.lonestaramerica.com/ ========================================== Use Outlook Express?... Get OE_Quotefix: It will strip signature out and more http://home.in.tum.de/~jain/software/oe-quotefix/ ========================================== Keep a back up of your OE settings and folders with OEBackup: http://www.oehelp.com/OEBackup/Default.aspx ==========================================
- Next message: Ace Fekay [MVP]: "Re: "Windows cannot access the file gpt.ini for GPO" - Events 1058 and 1030 on XP client only."
- Previous message: Chris Simmons: "Re: "Windows cannot access the file gpt.ini for GPO" - Events 1058 and 1030 on XP client only."
- In reply to: Chris Simmons: ""Windows cannot access the file gpt.ini for GPO" - Events 1058 and 1030 on XP client only."
- Next in thread: Chris Simmons: "Re: "Windows cannot access the file gpt.ini for GPO" - Events 1058 and 1030 on XP client only."
- Reply: Chris Simmons: "Re: "Windows cannot access the file gpt.ini for GPO" - Events 1058 and 1030 on XP client only."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
