Click to See Complete Forum and Search --> : Connecting some clients (Windows XP Pro) to a DNS server (Windows Server 2003)


rlbrl
July 6th, 2004, 05:15 PM
I have a Windows Server 2003 Standard Edition server with Active Directory, DHCP and DNS installed. The server is a stand alone domain controller with a domain name of CITY.local. The clients are Windows XP Pro with Service Pack 1 and I have four (4) to connect to the domain. Two of the clients have connected to the domain, however two will not connect. Seams like a problem that would be simple to locate, evidently not so...

The server DHCP is as follows:
DHCP = server.city.local [192.168.0.1] Running

server.city.local [192.168.0.1] = Scope [192.168.0.0] Scope1
** Active **

Address Pool = 192.168.0.10 192.168.0.254
Address range for distribution

The server DNS SERVER Properties are as follows:
DNS
SERVER = (Interface TAB) Listen on: All IP addresses
192.168.0.1
169.254.202.112

Forward Lookup Zones
CITY.local =
(Same as parent folder) Start of Authority (SOA)
[54],server.city.local.,hostmaster.
(Same as parent folder) Name Server (NS)
server.city.local
(Same as parent folder) Host (A) 169.254.202.112
(Same as parent folder) Host (A) 192.168.0.1
(Same as parent folder) Host (A) 192.168.0.1

Reverse Lookup Zones (None)


On all clients the Network Connections > Local Area Connection > Internet Protocol (TCP/IP) > Properties are as follows:

Obtain an IP address automatically

Use the following DNS server address:
Preferred DNS server. 169.254.202.112

On all clients I connect to the domain in System Properties
Member of = Domain: CITY.local


I cannot get two (2) of the clients connected to the domain. When I attempt to do so I receive the following Computer Name Changes message:

A domain controller for the domain CITY.local could not be
contacted. Ensure that the domain name is typed correctly.
If the name is correct, click Details for troubleshooting
information.

Details are as follows:

DNS was successfully queried for the service location (SRV)
resource record used to locate a domain controller for domain
CITY.local:

The query was for the SRV record for _ldap._tcp.dc_msdcs.CITY.
local
The following domain controllers were identified by the query:

server.city.local

Common causes of this error include:
- Host (A) records that map the name of the domain controller
to its IP address are missing or contain incorrect addresses.

- Domain controllers registered in DNS are not connected to the
network or are not running.


OTHER NOTES:
All clients (although not connected to the internet (nor is the
server)) have Norton Internet Security installed with the
Personal Firewall and Ad Blocking turned OFF

All clients can ping each other and the server

All clients can use My Network Places and connect to the
server, display shared files and folders, even delete files in
shared folders.

Any suggestions would be appreciated......

rlbrl
July 6th, 2004, 05:35 PM
Sorry everone but an update that I think you need to know: Cables have been swapped to veryify validity. The responce is the same.
Again thanks for any assistance....

jmwills
July 7th, 2004, 07:54 AM
Is DNS for the clients pointing to 192.168.0.1?

Your network cards should be set to obtain an IP Addrss Automatically but set the DNS manually to the address of the server.

Try this and see if it works. Is the server also the gateway?

rlbrl
July 7th, 2004, 12:36 PM
Thanks so much for responding but the settings you requested I look at were correct.

I did resolve the problem though. I went into Add and Remove Programs then Add and Remove Windows Componets then deinstalled Networking Services. Rebooted system and reinstalled.

All is well.

I tell you what, windows can sure turn your hair gray. Thanks again for your input.

rlbrl
July 7th, 2004, 12:38 PM
Sorry, this was done only on the clients that would not connect to the Domain.