Re: Still strange not fully working DNS server
- From: Meinolf Weber <meiweb(nospam)@gmx.de>
- Date: Thu, 9 Oct 2008 12:57:39 +0000 (UTC)
Hello Harmjan,
netdiag /v >c:\output.txt
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
the netdiag /v did not fit on screen at all so that's only givven me
half of the info...
"Meinolf Weber" wrote:
Hello Harmjan,
On the server make sure the DHCP client service is started. The run
ipconfig /registerdns on the server.
The suptools.msi is located on the server installation disk under
support\tools. All tools are inlcuded here.
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and
confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
DCdiag:
C:\Program Files\Support Tools>dcdiag /v
Domain Controller Diagnosis
Performing initial setup:
* Verifying that the local machine dc01, is a DC.
* Connecting to directory service on server dc01.
* Collecting site info.
* Identifying all servers.
* Found 1 DC(s). Testing 1 of them.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\DC01
Starting test: Connectivity
* Active Directory LDAP Services Check
DC01's server GUID DNS name could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(6379012e-2c39-4d39-b96d-06b9ae726697._msdcs.maddogs.local)
couldn't
be resolved, the server name (dc01.maddogs.local) resolved to
the IP
address (192.168.2.101) and was pingable. Check that the IP
address
is registered correctly with the DNS server.
......................... DC01 failed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\DC01
Skipping all tests, because server DC01 is
not responding to directory service requests
Test omitted by user request: Topology
Test omitted by user request: CutoffServers
Test omitted by user request: OutboundSecureChannels
Running enterprise tests on : maddogs.local
Starting test: Intersite
Skipping site Default-First-Site-Name, this site is outside
the scope
provided by the command line arguments provided.
......................... maddogs.local passed test Intersite
Starting test: FsmoCheck
GC Name: \\dc01.maddogs.local
Locator Flags: 0xe00003fd
PDC Name: \\dc01.maddogs.local
Locator Flags: 0xe00003fd
Time Server Name: \\dc01.maddogs.local
Locator Flags: 0xe00003fd
Preferred Time Server Name: \\dc01.maddogs.local
Locator Flags: 0xe00003fd
KDC Name: \\dc01.maddogs.local
Locator Flags: 0xe00003fd
......................... maddogs.local passed test FsmoCheck
The netdiag.exe I got was wrong version so need to find the right
one
(2003 R2)
Best regards
Harmjan
"Meinolf Weber" wrote:
Hello Harmjan,
Please run dcdiag /v, netdiag /v and post the output here.
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties,
and
confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
sorry it's all in dutch but should quite unterstandable:
Windows IP-configuratie
Host-naam . . . . . . . . . . . .: bar05
Primair DNS-achtervoegsel. . . . .: maddogs.local
Knooppunttype . . . . . . . . . . : hybride
IP-routering ingeschakeld. . . . .: nee
WINS-proxy ingeschakeld . . . . . : nee
DNS-achtervoegselzoeklijst. . . . : maddogs.local
maddogs.local
Ethernet-adapter LAN-verbinding:
Verbindingsspec. DNS-achtervoegsel: maddogs.local
Beschrijving . . . . . . . . . . .:
Realtek RTL8139 Family PCI Fast Ethernet NIC #2
Fysiek adres. . . . . . . . . . . : 00-02-44-22-D0-93
DHCP ingeshakeld. . . . . . . . . : ja
Autom. configuratie ingeschakeld. : ja
IP-adres. . . . . . . . . . . . . : 192.168.2.6
Subnetmasker. . . . . . . . . . . : 255.255.255.0
Standaardgateway. . . . . . . . . : 192.168.2.1
DHCP-server . . . . . . . . . . . : 192.168.2.101
DNS-servers . . . . . . . . . . . : 192.168.2.101
Primaire WINS-server. . . . . . . : 192.168.2.101
Lease verkregen . . . . . . . . . : donderdag 9 oktober 2008
13:15:15
Lease verlopen . . . . . . . . . : vrijdag 17 oktober 2008
13:15:15
If nothing helps I guess the only optuin is to reinstall server,
completely create a new domain and AD and import all the GPO's but
that wil take quite a long time and I still don't know what went
wrong, it all seems ok but DNS is not working as it should...
"Meinolf Weber" wrote:
Hello Harmjan,
Just do it. Let's see again.
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties,
and
confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!!
http://www.blakjak.demon.co.uk/mul_crss.htm
Hi Meinolf,
I have just done that but I doubt if that helps.
Ive removed that just a few hours ago and the GPO and DNS
problem
exists for
about 2 weeks now.
Can I help by posting a unedited copy/paste of an ipconfig /all
from
a
client?
Best regards
"Meinolf Weber" wrote:
Hello Harmjan,
Readd it's own ip address to the NIC as preferred DNS.
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no
warranties,
and
confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!!
http://www.blakjak.demon.co.uk/mul_crss.htm
Dear Meinolf,
this is the ipconfig /all from the DC:
Windows IP Configuration
Host Name . . . . . . . . . . . . : dc01
Primary Dns Suffix . . . . . . . : maddogs.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : maddogs.local
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel 8255x-based PCI
Ethernet
Adapter (10/100)
Physical Address. . . . . . . . . : 00-02-B3-50-67-03
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.2.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
I don't use a secondary zone, it's the zone created when
installing
DNS
Best regards
"Meinolf Weber" wrote:
Hello Harmjan,
Please post an unedited ipconfig /all from the DC. Do you use
AD integrated zones? Or is this a secondary zone?
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no
warranties,
and
confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!!
http://www.blakjak.demon.co.uk/mul_crss.htm
Dear Meinorf,
I use standard secure dynamic updates only on the
zone properties yes.
On none of the computers (both DC and clients) no firewall
software
is
running, only standard antivirus software.
Registered in de DNS is only SOA, WINS lookup and NS. For
the
rest
nothing happens in the DNS forward lookup zone.
Best regards
"Meinolf Weber" wrote:
Hello Harmjan,
But still not registered in DNS?
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no
warranties,
and
confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!!
http://www.blakjak.demon.co.uk/mul_crss.htm
extra information:
I also have disjoined and rejoined the client to the
domain with no problem at all.
Maby that info could also be helpfull.
"Meinolf Weber" wrote:
Hello Harmjan,
If the clients are domain members they have to be
registered in your DNS server. Did you run ipconfig
/registerdns on a client to check if they will
registrate?
Is the new server Global catalog? You didn't mention it.
During your migration i assume you added the new server
as a member to the domain and then run dcpromo on it? Or
did you just install a new domain with the same old name?
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no
warranties,
and
confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!!
http://www.blakjak.demon.co.uk/mul_crss.htm
Dear Meinolf,
None of the clients are registered in DNS (forgot to
mention that). That is the main reason why I think the
problem is in the DNS settings.
We had an old server and I migrated everything to the
new
server.
The old server was demoted succesfully and the new DC
has
all
the
master
roles, DNS and DHCP server.
with gpresult /v I also get an error about not having
"RVB"
information.
gpupdate /force does not give an error but no result
aswell
(gpupdate and gpresult are the first things I always
check,
even
when the GPO's does work).
Best regards
"Meinolf Weber" wrote:
Hello Harmjan,
Also check that the policy is applied on the client
with gpresult /v. If the output is to big for the
command window pipe it to textfile:
.
- References:
- Re: Still strange not fully working DNS server
- From: Harmjan Olthoff
- Re: Still strange not fully working DNS server
- Prev by Date: Re: Still strange not fully working DNS server
- Next by Date: Re: Still strange not fully working DNS server
- Previous by thread: Re: Still strange not fully working DNS server
- Index(es):
Relevant Pages
|
