Re: DNS issues with Windows XP


badkarma
Member
#253837

Re: DNS issues with Windows XP

Jeremy,

thanks for the help!!!!

the Mac that was running DCHP server was causing problems, but the GPO stuff is still unresolved.

here is gpresult output:

Microsoft (R) Windows (R) XP Operating System Group Policy Result tool v2.0
Copyright (C) Microsoft Corp. 1981-2001

Created On 10/30/2006 at 9:06:07 AM

RSOP results for DOMAINvlong on DEV2 : Logging Mode



OS Type: Microsoft Windows XP Professional
OS Configuration: Member Workstation
OS Version: 5.1.2600
Domain Name: RSABG
Domain Type: Windows 2000
Site Name: Default-First-Site
Roaming Profile: \marleyprofiles$vlong
Local Profile: C:Documents and Settingsvlong
Connected over a slow link?: No

COMPUTER SETTINGS



Last time Group Policy was applied: 10/30/2006 at 8:26:57 AM
Group Policy was applied from: marley.DOMAIN.local
Group Policy slow link threshold: 500 kbps

Applied Group Policy Objects


Default Domain Policy
No Roaming Profiles-local

The following GPOs were not applied because they were filtered out


Local Group Policy
Filtering: Not Applied (Empty)

Folder Redirect
Filtering: Disabled (GPO)

The computer is a part of the following security groups:


BUILTINAdministrators
Everyone
BUILTINUsers
NT AUTHORITYNETWORK
NT AUTHORITYAuthenticated Users
DEV2$
Domain Computers
CERTSVC_DCOM_ACCESS

USER SETTINGS



Last time Group Policy was applied: 10/30/2006 at 8:28:00 AM
Group Policy was applied from: marley.DOAMIN.local
Group Policy slow link threshold: 500 kbps

Applied Group Policy Objects


Default Domain Policy
Folder Redirect

The following GPOs were not applied because they were filtered out


Local Group Policy
Filtering: Not Applied (Empty)

No Roaming Profiles-local
Filtering: Not Applied (Empty)

The user is a part of the following security groups:


Domain Users
Everyone
BUILTINPower Users
BUILTINUsers
NT AUTHORITYINTERACTIVE
NT AUTHORITYAuthenticated Users
LOCAL
Development

Karma

p.s. the DNS client GPO is set in the Default Domain Policy; the IP address in the policy is 134.xxx.xxx.197, but nslookup results show the DNS server as 134.xxx.xxx.2