Re: Advice Needed - AD integrated DNS Zone

Per your suggestion, I am posting the Ipconfig /all and net start for one of
the users with an issue with two of my dns servers.
Nslookup for AD zone looks like:

server: ih-ad01.interhealth
address: 192.168.1.208

DNS request timed out.
timeout waas 2 seconds
*** Request to ih-ad01.interhealth timed-out

Ipconfig and net start for user with this issue:

Windows IP Configuration

Host Name . . . . . . . . . . . . : IHLAB001
Primary Dns Suffix . . . . . . . : interhealth
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : interhealth

Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . : interhealth
Description . . . . . . . . . . . : Dell Wireless WLAN 1350 WLAN
Mini-PC
I Card
Physical Address. . . . . . . . . : 00-90-96-A9-41-14
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.40
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.225
DHCP Server . . . . . . . . . . . : 192.168.1.208
DNS Servers . . . . . . . . . . . : 192.168.1.208
192.168.1.253
NetBIOS over Tcpip. . . . . . . . : Disabled
Lease Obtained. . . . . . . . . . : Tuesday, July 19, 2005 9:05:21
AM
Lease Expires . . . . . . . . . . : Wednesday, July 27, 2005 9:05:21
AM

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Broadcom 570x Gigabit Integrated
Con
troller
Physical Address. . . . . . . . . : 00-0F-1F-A1-7D-35


net start
These Windows services are started:

Application Layer Gateway Service
Ati HotKey Poller
Automatic Updates
Broadcom ASF IP monitoring service v6.0.3
Check Point SecuRemote Service
Check Point SecuRemote WatchDog
COM+ Event System
Cryptographic Services
DCOM Server Process Launcher
DHCP Client
Distributed Link Tracking Client
DNS Client
Error Reporting Service
Event Log
Help and Support
IPSEC Policy Agent
Logical Disk Manager
Machine Debug Manager
McAfee Managed Services Agent
McShield
MSSQL$MICROSOFTBCM
Net Logon
Network Configuration Service
Network Connections
Network Location Awareness (NLA)
Plug and Play
Print Spooler
Protected Storage
Remote Access Connection Manager
Remote Procedure Call (RPC)
Remote Registry
Secondary Logon
Security Accounts Manager
Server
Shell Hardware Detection
Smart Card
SSDP Discovery Service
System Event Notification
System Restore Service
Task Scheduler
TCP/IP NetBIOS Helper
Telephony
Terminal Services
Themes
WebClient
Windows Audio
Windows Firewall/Internet Connection Sharing (ICS)
Windows Image Acquisition (WIA)
Windows Management Instrumentation
Windows Time
Windows User Mode Driver Framework
Wireless Zero Configuration
WLTRYSVC
Workstation

The command completed successfully.


If I configure the user to use the other DNS Server (the one that works for
this user):
ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : IHLAB001
Primary Dns Suffix . . . . . . . : interhealth
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : interhealth

Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . : interhealth
Description . . . . . . . . . . . : Dell Wireless WLAN 1350 WLAN
Mini-PC
I Card
Physical Address. . . . . . . . . : 00-90-96-A9-41-14
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.40
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.225
DHCP Server . . . . . . . . . . . : 192.168.1.208
DNS Servers . . . . . . . . . . . : 192.168.1.206
NetBIOS over Tcpip. . . . . . . . : Disabled
Lease Obtained. . . . . . . . . . : Tuesday, July 19, 2005 9:51:15
AM
Lease Expires . . . . . . . . . . : Wednesday, July 27, 2005 9:51:15
AM

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Broadcom 570x Gigabit Integrated
Con
troller
Physical Address. . . . . . . . . : 00-0F-1F-A1-7D-35

"Kevin D. Goodknecht Sr. [MVP]" <admin@xxxxxxxxxxxxxx> wrote in message
news:u3mUSd%23iFHA.2852@xxxxxxxxxxxxxxxxxxxxxxx
> In news:uMR88S%23iFHA.3144@xxxxxxxxxxxxxxxxxxxx,
> Fredrick A. Zilz <fzilz@xxxxxxxxxxxxxxxxxxxxxxxxx> posted this:
>> Thank you,
>> Trying to trouble shoot a client DNS issue. A couple of my windows
>> XP users (all my users are windows XP sp2 users) are not resolving
>> computers in my AD zone when connecting to either of two DNS servers
>> (AD ) but resolve correctly when DNS is set the third server.
>> Unfortunately, I don't want the DNS that is correctly resolving
>> addresses to be a DC and longer.
>> The users recieve a timeout when using Nslookup. I have gone so far
>> as to remove the client computer from my domain, deleted the Computer
>> from AD and then added the client computer back to the Domain with a
>> new computer name. Same issue. The remainder of my users using
>> resolve addresses correctly when using any of the three DCs as their
>> DNS server. Note: the users correctly resolve address not in my AD
>> zone - I don't use forwarding, just root hints. So far the users with
>> this issue are laptops, but I don't know if that is coincidence or
>> significant.
>>
>> I have run Dcdiag and netdiag and everything passes. I don't know
>> what to look for. I have opened a client that is not working next to
>> a client that is and looked through thier TCP/IP configuration and do
>> not see anything different. DHCP assigns ip address and DNS for all
>> users.
>>
>> I would appreciate any ideas you could send my way.
>
> Post an ipconfig /all from the failing clients and run 'net start'
> (without
> the quotes) in a command prompt. post the results from these two commands.
>
>
>
> --?
> 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 address.
> ===================================
> 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
> ===================================
>
>


.

Relevant Pages

  • RE: Dynamic Update of A&PTR Records - Best Practice?
    ... The DNS server does not support the DNS dynamic update protocol; ... For Windows Server 2003-based computers, the primary full computer name is ... When one of these events triggers a DNS update, the DHCP Client service, ...
    (microsoft.public.windows.server.dns)
  • Re: Migration from NT4 to W2K
    ... 272594 Problems logging on to a Windows 2000-based server or a Windows ... | Full DNS domain name is now ABC1.cz, ... | before in-place upgrade of NT4 is able to logon to this W98 client. ...
    (microsoft.public.windows.server.migration)
  • Windows refuses to use DNS
    ... We are building a DHCP server, to hand out IP addresses to Windows 2000 Server SP3 clients. ... We are having difficulties getting DNS to work on the client. ... For Windows to stop using WINS/NetBIOS, it appears our application on the client has to go into the registry to 'Disable NetBIOS over TCP/IP' on each interface. ...
    (microsoft.public.development.device.drivers)
  • Re: Where to find workstation DNS settings documentation?
    ... to have the internal DNS servers ONLY... ... > client logons, domain replication from one DC to another, authentication, ...
    (microsoft.public.win2000.dns)
  • Re: Clients not registering in AD integrated DNS
    ... entries from the set of DNS servers in domA.com to the set of DNS servers in ... on the client had no effect at all. ... they do not register in DNS at any ...
    (microsoft.public.windows.server.dns)
Loading