In
CecilWilliams said:
I tried emailing this to you Ragini, but the email bounced back
undeliverable. Here is the ipconfig /all info:
*****************
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : XXXX-XXX
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : losaca.adelphia.net
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : losaca.adelphia.net
Description . . . . . . . . . . . : 3Com EtherLink 10/100 PCI NIC
(3C905-TX) #3 Physical Address. . . . . . . . . : 00-XX-XX-XX-XX-XX
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 68.65.16.162
68.65.16.165
Lease Obtained. . . . . . . . . . : Friday, August 08, 2003 5:37:06 AM
Lease Expires . . . . . . . . . . : Monday, August 11, 2003 5:37:06 AM
*****************
spam to: (e-mail address removed)
email to: cecilw at cecilw dot com
Thanks, Cecil
Hi Cecil,
Thanks for posting that information.
I see a couple problems.
1. Your Primary DNS Suffix is missing. A DC must have a Primary DNS Suffix.
From the looks of it, unless you edited the ipconfig /all to remove it so as
not to post it, it should probably be: losaca.adelphia.net. But that depends
on what your AD domain name is. If the AD domain name is something else,
then it should be that name, and it should not be of a single name style,
such as "losaca". It should be at least adelphia.net or losaca.adelphia.net,
depending on what your domain name is.
2. You are using your ISP's DNS servers. In an AD environment, that's a
no-no. Please do remove them and point ONLY to your own internal DNS server.
Then on your internal DNS server, for more efficient Internet name
resolution, use a Forwarder. Outlined below step 3 in this article below. If
the option is grayed out, delete your Root zone, also shown below that in
the same article:
http://support.microsoft.com/?id=300202
The reason is that AD stores it's information in DNS. If you use someone
else;s DNS, AD flies south since they don't have the information that AD is
looking for.
This should also be true for ALL your machines, clients, member servers,
etc.
Then in your DNS, make sure the zone, losaca.adelphia.net, is created and
you have updates set to at least YES. Then run this procedure:
ipconfig /registerdns
net stop netlogon
net start netlogon
Then insure that the SRV records get created. You can use this guide to help
you out:
241515 - How to Verify the Creation of SRV Records for a Domain Controller:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;241515
If they don't appear, post back and let us know.
The empty Primary DNS suffix can be fixed, provided that the AD domain name
is losaca.adelphia.net. I have a script that can fix that. But I need to
know what the AD domain name is please, as it shows up in your ADUC.
--
Regards,
Ace
Please direct all replies to the newsgroup so all can benefit.
Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory