Re: User GPO doesn't replicate on one of my workstations
From: Feng Mao (fengmao_at_online.microsoft.com)
Date: 07/14/04
- Next message: ChrisM: "XP in 2000 Domain"
- Previous message: gopal: "Re: Create Custom PAssword filters"
- In reply to: Guillaume Tamisier: "Re: User GPO doesn't replicate on one of my workstations"
- Next in thread: Guillaume Tamisier: "Re: User GPO doesn't replicate on one of my workstations"
- Reply: Guillaume Tamisier: "Re: User GPO doesn't replicate on one of my workstations"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 14 Jul 2004 07:49:56 GMT
Hi Guillaume,
Thank you for the reply!
As disjoining and rejoing the domain cannot solve this issue, let us try
the below troubleshooting method:
*Step 1: Check the DNS settings and network properties on the servers and
client computers*
In the local area connection properties, the Client for Microsoft Networks
must be enabled on all servers and client computers, and the File and
Printer Sharing for Microsoft Networks component must be enabled on all
domain controllers. In
addition, all computers on the network must use the DNS servers for the
local domain. Check these settings on all ccmputers that are logging the
Userenv errors. Additionally, check these settings on all domain
controllers, whether they are logging Userenv errors or not.
To check DNS settings and network properties, follow these steps:
1. Click Start, point to Settings, and then click Control Panel.
2. On Windows XP, if Control Panel is in Category View, click Switch to
Classic View.
3. On Windows 2000, double-click Network and Dial-up Connections. On
Windows Server 2003 and Windows XP, double-click Network Connections.
4. Right-click the icon for the local area connection, and then click
Properties.
5. On the General tab of the connection properties, make sure that Client
for Microsoft Networks is checked in the list of components. On domain
controllers, also make sure that File and Printer Sharing for Microsoft
Networks is checked. If these components are not checked, click to check
them.
6. Click to select Internet Protocol (TCP/IP), and then click Properties
(do not un-check the box for this component).
7. If the "Use the following DNS server addresses" option is selected, make
sure that the IP addresses for the preferred and alternate DNS servers are
the IP addresses of DNS servers on the internal network. If they are not,
enter the correct IP addresses of the internal DNS servers.
8. Click Advanced.
9. Click the DNS tab.
10. Click to check the "Register this connection's addresses in DNS" option.
11. Click OK three times.
12. Run the command "ipconfig /flushdns".
13. Run the command "ipconfig /registerdns".
If client computers are configured to obtain their IP addresses
automatically, make sure that the DHCP server is assigning the correct IP
addresses of the DNS servers on the internal network. To find out what IP
addresses a computer is using for DNS, run the command "ipconfig /all". If
computers that are configured to obtain IP addresses automatically are not
using the IP addresses of the DNS servers on the internal network, see the
documentation for your DHCP server for information about how to configure
the DNS servers option.
Also, make sure that each computer can resolve the IP address of the
domain. To test this, run the command "ping domainname.local", where
domainname.local is the name of the domain that the computer is a member
of. The computer should try to ping the IP address of one of the domain
controllers on the network. If the computer cannot resolve this name, or if
it tries to ping the wrong IP address, make sure that the forward lookup
zone for the domain contains valid "(same as parent folder)" Host (A)
records. To do so, follow these steps:
1. On one of the internal DNS servers, click Start, point to Programs or
All Programs, point to Administrative Tools, and then click DNS.
2. Expand the server object, expand the Forward Lookup Zones folder, and
then click the forward lookup zone for the domain.
3. Look for Host (A) records with the name "(same as parent folder)".
4. If a Host (A) record with this name does not exist, use these steps to
create one:
a. On the Action menu, click New Host.
b. In the "IP address" text box, type the IP address of the domain
controller's local network adapter.
c. Leave the Name box empty, click Create Associated PTR Record, and then
click Add Host.
d. When you receive the "(same as parent folder) is not a valid host name.
Are you sure you want to add this record?" message, click Yes.
5. If one or more "(same as parent folder)" Host (A) records contains an
invalid IP address, double-click the invalid record to change the IP
address, or delete the invalid record. To delete a record, right-click the
record, and then click Delete. If the DNS server is a domain controller
that is also a Routing and Remote Access server, see the following KB
article:
292822 Name resolution and connectivity issues on a Routing and Remote
Access Server that also runs DNS or WINS
http://support.microsoft.com/?id=292822
6. If you add, delete, or modify DNS records, run the command "ipconfig
/flushdns" on all affected computers.
*Step 2: Make sure that Distributed File System (DFS) is enabled on all
computers*
All domain controllers must run the Distributed File System service. In
addition, the DFS client must be enabled in the registry on all computers.
To make sure that the Distributed File System service is running on the
domain controllers, follow these steps:
1. On each domain controller, click Start, point to Programs or All
Programs, point to Administrative Tools, and then click Services.
2. In the Services console, check the Status and the Startup Type value for
the Distributed File System service. The Status should be Started, and the
Startup Type should be Automatic.
3. If the Status and the Startup Type are not Started and Automatic,
right-click Distributed File System service, and then click Properties.
4. In the Distributed File System Properties, click to select Automatic in
the "Startup type" box.
5. If the service is not started, click Start to start the service, and
then click OK.
NOTE: This issue currently is documented in the following KB article:
834649 Client computers record Event ID 1030 and Event ID 1058 when DFS is
not started on a Windows 2000-based domain controller
http://support.microsoft.com/?id=834649
I hope that the above information is helpful.
Have a nice day!
Thanks & Regards,
Feng Mao [MSFT], MCSE
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
- Next message: ChrisM: "XP in 2000 Domain"
- Previous message: gopal: "Re: Create Custom PAssword filters"
- In reply to: Guillaume Tamisier: "Re: User GPO doesn't replicate on one of my workstations"
- Next in thread: Guillaume Tamisier: "Re: User GPO doesn't replicate on one of my workstations"
- Reply: Guillaume Tamisier: "Re: User GPO doesn't replicate on one of my workstations"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
