I also miss the zones _ msdcs, _ sites, _tcp etc.

  • Thread starter Thread starter Michael
  • Start date Start date
M

Michael

I miss the zones _ msdcs, _ sites, _
TCP and _ UDP DNS on my DC.

I have replication problems between my W2K server DC and
my W2K3 server that is an additonal DC in the domain.

I have run dcdiag on both servers with the following
result.

**********************************************************
This is from an additional dc with windows 2003 server

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\SOLW2K3S-MAIL1
Starting test: Connectivity
The host 705db1a2-ee4c-48e6-a7a2-
bce375db418c._msdcs.SOL could not be r
esolved to an
IP address. Check the DNS server, DHCP, server
name, etc
Although the Guid DNS name
(705db1a2-ee4c-48e6-a7a2-bce375db418c._msdcs.SOL)
couldn't be
resolved, the server name (solw2k3s-mail1.SOL)
resolved to the IP
address (192.168.1.5) and was pingable. Check
that the IP address is
registered correctly with the DNS server.
......................... SOLW2K3S-MAIL1 failed
test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\SOLW2K3S-MAIL1
Skipping all tests, because server SOLW2K3S-MAIL1 is
not responding to directory service requests

Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test
CheckSDRefDom

Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed
test CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed
test CheckSDRefDom

Running partition tests on : SOL
Starting test: CrossRefValidation
......................... SOL passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... SOL passed test
CheckSDRefDom

Running enterprise tests on : SOL
Starting test: Intersite
......................... SOL passed test
Intersite
Starting test: FsmoCheck
......................... SOL passed test
FsmoCheck
***********************************************************
***********************************************************

And this is from the first Windows 2000 server dc in the
domain.

DC Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial non skippeable tests

Testing server: Default-First-Site-Name\SOLW2KS01
Starting test: Connectivity
SOLW2KS01'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
(69a18c8c-5745-4d68-9415-b23e71404465._msdcs.SOL)
couldn't be
resolved, the server name (solw2ks01.SOL)
resolved to the IP address
(192.168.1.1) and was pingable. Check that the
IP address is
registered correctly with the DNS server.
......................... SOLW2KS01 failed test
Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\SOLW2KS01
Skipping all tests, because server SOLW2KS01 is
not responding to directory service requests

Running enterprise tests on : SOL
Starting test: Intersite
......................... SOL passed test
Intersite
Starting test: FsmoCheck
......................... SOL passed test
FsmoCheck
***********************************************************

These servers can´t replicate between each other and the
event viewer points out that it´s some DNS problem and
that i can´t deny;-)
Could i get some idéas plz and i would be very greatful..
 
In Michael <[email protected]> posted a question
Then Kevin replied below:
: I miss the zones _ msdcs, _ sites, _
: TCP and _ UDP DNS on my DC.
:
: I have replication problems between my W2K server DC and
: my W2K3 server that is an additonal DC in the domain.
:
: I have run dcdiag on both servers with the following
: result.
:
: **********************************************************
: This is from an additional dc with windows 2003 server
:
: Domain Controller Diagnosis
:
: Performing initial setup:
: Done gathering initial info.
:
: Doing initial required tests
:
: Testing server: Default-First-Site-Name\SOLW2K3S-MAIL1
: Starting test: Connectivity
: The host 705db1a2-ee4c-48e6-a7a2-
: bce375db418c._msdcs.SOL could not be r
: esolved to an
: IP address. Check the DNS server, DHCP, server
: name, etc
: Although the Guid DNS name
: (705db1a2-ee4c-48e6-a7a2-bce375db418c._msdcs.SOL)
: couldn't be
: resolved, the server name (solw2k3s-mail1.SOL)
: resolved to the IP
: address (192.168.1.5) and was pingable. Check
: that the IP address is
: registered correctly with the DNS server.
: ......................... SOLW2K3S-MAIL1 failed
: test Connectivity
:
: Doing primary tests
:
: Testing server: Default-First-Site-Name\SOLW2K3S-MAIL1
: Skipping all tests, because server SOLW2K3S-MAIL1 is
: not responding to directory service requests
:
: Running partition tests on : Schema
: Starting test: CrossRefValidation
: ......................... Schema passed test
: CrossRefValidation
: Starting test: CheckSDRefDom
: ......................... Schema passed test
: CheckSDRefDom
:
: Running partition tests on : Configuration
: Starting test: CrossRefValidation
: ......................... Configuration passed
: test CrossRefValidation
: Starting test: CheckSDRefDom
: ......................... Configuration passed
: test CheckSDRefDom
:
: Running partition tests on : SOL
: Starting test: CrossRefValidation
: ......................... SOL passed test
: CrossRefValidation
: Starting test: CheckSDRefDom
: ......................... SOL passed test
: CheckSDRefDom
:
: Running enterprise tests on : SOL
: Starting test: Intersite
: ......................... SOL passed test
: Intersite
: Starting test: FsmoCheck
: ......................... SOL passed test
: FsmoCheck
: ***********************************************************
: ***********************************************************
:
: And this is from the first Windows 2000 server dc in the
: domain.
:
: DC Diagnosis
:
: Performing initial setup:
: Done gathering initial info.
:
: Doing initial non skippeable tests
:
: Testing server: Default-First-Site-Name\SOLW2KS01
: Starting test: Connectivity
: SOLW2KS01'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
: (69a18c8c-5745-4d68-9415-b23e71404465._msdcs.SOL)
: couldn't be
: resolved, the server name (solw2ks01.SOL)
: resolved to the IP address
: (192.168.1.1) and was pingable. Check that the
: IP address is
: registered correctly with the DNS server.
: ......................... SOLW2KS01 failed test
: Connectivity
:
: Doing primary tests
:
: Testing server: Default-First-Site-Name\SOLW2KS01
: Skipping all tests, because server SOLW2KS01 is
: not responding to directory service requests
:
: Running enterprise tests on : SOL
: Starting test: Intersite
: ......................... SOL passed test
: Intersite
: Starting test: FsmoCheck
: ......................... SOL passed test
: FsmoCheck
: ***********************************************************
:
: These servers can´t replicate between each other and the
: event viewer points out that it´s some DNS problem and
: that i can´t deny;-)
: Could i get some idéas plz and i would be very greatful..

Looks like this is a single label domain name did you apply the registry
values from this KB article?
300684 - Information About Configuring Windows 2000 for Domains with
Single-Label DNS Names
http://support.microsoft.com/default.aspx?scid=kb;en-us;300684&FR=1

Win2k3 moved the _msdcs.dnsdomain to its own forward lookup zone.
817470 - HOW TO: Reconfigure an _msdcs Subdomain to a Forest-wide DNS
Application Directory Partition When You Upgrade from Windows 2000 to
Windows Server 2003
http://support.microsoft.com/default.aspx?scid=kb;en-us;817470&Product=winsvr2003

You also stated the Win2k3 was an additional DC on the Win2k domain so I
assume you followed this KB.
278875 - Cannot Promote a Windows Server 2003 Domain Controller into a
Windows 2000 Forest
http://support.microsoft.com/default.aspx?scid=kb;en-us;278875&Product=winsvr2003
 
Okay, Kevin.

I think the story is like this.

1. The w2k3 server was added to the w2k domain. Before it
was done frostprep and domainprep was done.

2. RPC problems with replication was explored and that
pointed towards dns problems.

3. An MCSE consult told me to delete the DNS zone on the
first w2k server and reinstall the zone. After that was
done i could se that the problems was more worse than
before. The zones _msdcs etc was gone. He has no solution
towards the problem and now I don´t trust him to touch the
servers.

Your help is most welcome to me, Kevin.
 
In
Okay, Kevin.

I think the story is like this.

1. The w2k3 server was added to the w2k domain. Before it
was done frostprep and domainprep was done.

2. RPC problems with replication was explored and that
pointed towards dns problems.

3. An MCSE consult told me to delete the DNS zone on the
first w2k server and reinstall the zone. After that was
done i could se that the problems was more worse than
before. The zones _msdcs etc was gone. He has no solution
towards the problem and now I don´t trust him to touch the
servers.

Your help is most welcome to me, Kevin.
Click to expand...

Michael, if you don't mind me jumping in (Kevin too), your consultant should
know what he's doing and know how to get that data back if advising you to
do such a thing.

FYI: A Forestprep and Domainprep is an Exchange procedure to update the
Schema for Exchange and add two domain groups to each domain for Exchange
and has nothing to do with an ADPREP to update the Schema if you are going
to add a W2k3 AD DC. Did you run an ADPREP?

Here are some steps to follow to get the SRVs back:

1. Make sure all the DCs are using the internal DNS only. It is suggested
since you are going to W2k3, to use the W2k3 as your DNS server, since it
supports new features to support W2k3 AD. Don't bother using the W2k server.

Also this is very important: Do not use your ISP's. Remove them immediately
if they are in there.

2. Create your zone name in DNS. Hopefully this name must be spelled exactly
the same as your AD DNS Domain name (as it shows in ADUC) and the Primary
DNS Suffix of the machine.
If the domain name is a single label name, then make the necessary registry
changes that Kevin suggested as per article:
http://support.microsoft.com/?id=300684.

3. Set Dynamic Updates to YES in the zone properties.

4. Once that is done, goto a command prompt and type these commands:
ipconfig /registerdns
net stop netlogon
net start netlogon

5. Once the netlogon service starts, refresh the DNS console and you should
see the SRVs show up.

If this doesn't work, then we'll need more information. If you can post:

1. An UNEDITED ipconfig /all from the two DCs (W2k and W2k3).
2. The AD DNS Domain name (as it shows up in your ADUC).
3. What Service Pack the W2k DC is on.

Hope this helps


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
I have tried to made the keys in registry. On the W2K3 it
did well but on the W2K i couldn´t even open the
key "Parameters". I get an error message that told me
following - "Cannot open parameters. Error while opening
key."
So it feels like a moment 22 here.
 
In
Michael said:
I have tried to made the keys in registry. On the W2K3 it
did well but on the W2K i couldn´t even open the
key "Parameters". I get an error message that told me
following - "Cannot open parameters. Error while opening
key."
So it feels like a moment 22 here.
Click to expand...

Hmm, hard to say why. Maybe permissions?

Also, as per my previous post, like to see that info I requested.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Hello Ace Fekay.

Im greatfull over your help.

I have got these zones in place now but only from w2k3
servern. I still can´t replicate over sites.
I get an RPC error.

I have done adprep/forestprep and adprep/domainprep on the
w2k3 servern there is also exchange 2003 installed.

On the w2k serven i have sp4 applied.

Bellow you can se IPconfig/all from both servers.
**********************************************************
IPconfig /all

W2K3

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator.SOL>ipconfig /ALl

Windows IP Configuration

Host Name . . . . . . . . . . . . : solw2k3s-mail1
Primary Dns Suffix . . . . . . . : SOL
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : SOL

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : sol
Description . . . . . . . . . . . : HP NC7760 Gigabit
Server Adapter
Physical Address. . . . . . . . . : 00-0B-CD-AF-FF-6F
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.5
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.20
DNS Servers . . . . . . . . . . . : 192.168.1.5
192.168.1.1

C:\Documents and Settings\Administrator.SOL>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : solw2k3s-mail1
Primary Dns Suffix . . . . . . . : SOL
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : SOL

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : sol
Description . . . . . . . . . . . : HP NC7760 Gigabit
Server Adapter
Physical Address. . . . . . . . . : 00-0B-CD-AF-FF-6F
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.5
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.20
DNS Servers . . . . . . . . . . . : 192.168.1.5
192.168.1.1

C:\Documents and Settings\Administrator.SOL>

**********************************************************
IPconfig /all
W2K

Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.

C:\Documents and Settings\Administrator>ipconfig /all

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : solw2ks01
Primary DNS Suffix . . . . . . . : SOL
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : SOL

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : sol
Description . . . . . . . . . . . : HP NetServer
10/100TX PCI LAN Adapter
Physical Address. . . . . . . . . : 00-E0-18-C6-7E-
44
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.20
DNS Servers . . . . . . . . . . . : 127.0.0.1

C:\Documents and Settings\Administrator>
**********************************************************

I still can´t access the parameters change on w2k servern.
In DNS on both servers i can only se w2k3 sever on the
created srv zones now.
 
In
Michael said:
Hello Ace Fekay.

Im greatfull over your help.

I have got these zones in place now but only from w2k3
servern. I still can´t replicate over sites.
I get an RPC error.

I have done adprep/forestprep and adprep/domainprep on the
w2k3 servern there is also exchange 2003 installed.

On the w2k serven i have sp4 applied.

Bellow you can se IPconfig/all from both servers.
**********************************************************
IPconfig /all

W2K3

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator.SOL>ipconfig /ALl

Windows IP Configuration

Host Name . . . . . . . . . . . . : solw2k3s-mail1
Primary Dns Suffix . . . . . . . : SOL
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : SOL

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : sol
Description . . . . . . . . . . . : HP NC7760 Gigabit
Server Adapter
Physical Address. . . . . . . . . : 00-0B-CD-AF-FF-6F
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.5
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.20
DNS Servers . . . . . . . . . . . : 192.168.1.5
192.168.1.1

C:\Documents and Settings\Administrator.SOL>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : solw2k3s-mail1
Primary Dns Suffix . . . . . . . : SOL
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : SOL

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : sol
Description . . . . . . . . . . . : HP NC7760 Gigabit
Server Adapter
Physical Address. . . . . . . . . : 00-0B-CD-AF-FF-6F
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.5
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.20
DNS Servers . . . . . . . . . . . : 192.168.1.5
192.168.1.1

C:\Documents and Settings\Administrator.SOL>

**********************************************************
IPconfig /all
W2K

Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.

C:\Documents and Settings\Administrator>ipconfig /all

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : solw2ks01
Primary DNS Suffix . . . . . . . : SOL
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : SOL

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : sol
Description . . . . . . . . . . . : HP NetServer
10/100TX PCI LAN Adapter
Physical Address. . . . . . . . . : 00-E0-18-C6-7E-
44
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.20
DNS Servers . . . . . . . . . . . : 127.0.0.1

C:\Documents and Settings\Administrator>
**********************************************************

I still can´t access the parameters change on w2k servern.
In DNS on both servers i can only se w2k3 sever on the
created srv zones now.
Click to expand...

Thank you Michael for posting that information.

I see a few things wrong. Let's see....

******
First, your W2k (solw2ks01) ipconfig shows that it is using 127.0.0.1 for
DNS:
DNS Servers . . . . . . . . . . . : 127.0.0.1
Click to expand...

That should actually be setup this way with the actual IP address and NOT
the loopback (127.0.0.1):
DNS Servers . . . . . . . . . . . : 192.168.1.5
DNS Servers . . . . . . . . . . . : 192.168.1.1
Click to expand...


******
Second, the W2k3 server (solw2k3s-mail1) shows this for DNS:
DNS Servers . . . . . . . . . . . : 192.168.1.5
192.168.1.1
Click to expand...

It should show as (reverse the entries):
DNS Servers . . . . . . . . . . . : 192.168.1.1
192.168.1.5
Click to expand...

Third, and the BIGGEST problem is that the domain is a single label name.
That is NOT good at all and creates mutliple problems. Your domain name is
called "SOL". It should be in the form of "sol.com" or "sol.net" or
"sol.michael", but not just "SOL". The single name does not follow the
hierarchal tree structure of DNS.

A single label named domain was probably due to (with all due respect) lack
of research and knowledge with the way AD and DNS must be designed PRIOR to
an upgrade/migration. It's very important to do your homework on this
because it becomes difficult to change. However, since you have W2k3 being
used, you may be able to change the name. But in order to do this, you must
upgrade the W2k server frst to W2k3 and raise the Forest Functional Level to
Native Mode. Here's a link on how to do that with W2k3:

Forest andDomain Functional Levels Explained:
http://www.microsoft.com/technet/tr...server2003/proddocs/datacenter/sag_levels.asp

Renaming domains - rendom.exe found in valueadd-msft-mgmt-domren folder on
CD:
http://www.microsoft.com/technet/tr...rver2003/proddocs/datacenter/domainrename.asp

SP4 changed/stopped the fact of letting registrations work because MS found
that excessive DNS traffic was hitting the ISC Root servers with any machine
that had a single label name. It was just too much. So they stopped it. Now,
you can use a regsitry entry to force registration but this must be done on
ALL the machines in your domain.

Here is the fix that you can use for now. It's more of a bandaid, but will
not totally solve certain issues, but it will force registration of the SRV
records:
http://support.microsoft.com/?id=300684

This has to be done on all machines.

One BIG problem, however, if using single label names, GPOs will not work,
whether you use the registry entry metioned in that link above or not. This
is because they look for the domain name when the GetGPOList function runs
on a client when it tries to "find" the GPO. The path it looks for is such
as this because the policies are found in the domain share:
\\domain.com\sysvol\domain.COM\Policies

In your case, it would be querying for:
\\SOL\sysvol\SOL\policies

In that case, it will not be able to find that domain name because it;s
treating it as a HOST name. You can try to force this by ensuring there is a
blank HOST name called SOL with the IP addresses of one of the DCs, but from
other posters and tests, it doesn;t appear to really work correctly. Also,
XP clients have difficulty querying this method, whether you put the
registration fix in it or not.

Sorry to be the bearer of bad news. I hope this helps in understanding your
dilemma and what your options are.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Thanks again Ace Fekay!

I did a few changes before this answer and that is the
following.

1. I applied the fix for singel label domain on the w2k3
server and that one replicated it to the w2k server. But
you could only see the w2k3 server in the srv zones. This
did the site replication error over rpc.

2. I added in _msdcs a CNAME with the GUID name for w2k
servern. And that replicated over to the w2k3 servern. Now
RPC replication between the site connectors functions well.

Now when i test with dcdiag it seems to be okay.

I will change the order of dns that you writes about.
(I think thats one of the way i had it but i have changed
and test every way i could think about).

I still have the problems with adding "parameters" on w2k
server and w2k pro workstations. To solve this i think i
have to start an upgrade to native mode and get to
your "bad news" ;-)

Once again thx m8 i needed that extra brain >(-_-)<
-----Original Message-----
In Michael <[email protected]> posted their thoughts, then I
offered mine
Hello Ace Fekay.

Im greatfull over your help.

I have got these zones in place now but only from w2k3
servern. I still can´t replicate over sites.
I get an RPC error.

I have done adprep/forestprep and adprep/domainprep on the
w2k3 servern there is also exchange 2003 installed.

On the w2k serven i have sp4 applied.

Bellow you can se IPconfig/all from both servers.
**********************************************************
IPconfig /all

W2K3

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator.SOL>ipconfig /ALl

Windows IP Configuration

Host Name . . . . . . . . . . . . : solw2k3s-mail1
Primary Dns Suffix . . . . . . . : SOL
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : SOL

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : sol
Description . . . . . . . . . . . : HP NC7760 Gigabit
Server Adapter
Physical Address. . . . . . . . . : 00-0B-CD-AF-FF-6F
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.5
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.20
DNS Servers . . . . . . . . . . . : 192.168.1.5
192.168.1.1

C:\Documents and Settings\Administrator.SOL>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : solw2k3s-mail1
Primary Dns Suffix . . . . . . . : SOL
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : SOL

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : sol
Description . . . . . . . . . . . : HP NC7760 Gigabit
Server Adapter
Physical Address. . . . . . . . . : 00-0B-CD-AF-FF-6F
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.5
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.20
DNS Servers . . . . . . . . . . . : 192.168.1.5
192.168.1.1

C:\Documents and Settings\Administrator.SOL>

**********************************************************
IPconfig /all
W2K

Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.

C:\Documents and Settings\Administrator>ipconfig /all

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : solw2ks01
Primary DNS Suffix . . . . . . . : SOL
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : SOL

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : sol
Description . . . . . . . . . . . : HP NetServer
10/100TX PCI LAN Adapter
Physical Address. . . . . . . . . : 00-E0-18-C6- 7E-
44
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.20
DNS Servers . . . . . . . . . . . : 127.0.0.1

C:\Documents and Settings\Administrator>
**********************************************************

I still can´t access the parameters change on w2k servern.
In DNS on both servers i can only se w2k3 sever on the
created srv zones now.
Click to expand...

Thank you Michael for posting that information.

I see a few things wrong. Let's see....

******
First, your W2k (solw2ks01) ipconfig shows that it is using 127.0.0.1 for
DNS:
DNS Servers . . . . . . . . . . . : 127.0.0.1
Click to expand...

That should actually be setup this way with the actual IP address and NOT
the loopback (127.0.0.1):
DNS Servers . . . . . . . . . . . : 192.168.1.5
DNS Servers . . . . . . . . . . . : 192.168.1.1
Click to expand...


******
Second, the W2k3 server (solw2k3s-mail1) shows this for DNS:
DNS Servers . . . . . . . . . . . : 192.168.1.5
Click to expand...
192.168.1.1

It should show as (reverse the entries):
DNS Servers . . . . . . . . . . . : 192.168.1.1
Click to expand...
192.168.1.5

Third, and the BIGGEST problem is that the domain is a single label name.
That is NOT good at all and creates mutliple problems. Your domain name is
called "SOL". It should be in the form of "sol.com" or "sol.net" or
"sol.michael", but not just "SOL". The single name does not follow the
hierarchal tree structure of DNS.

A single label named domain was probably due to (with all due respect) lack
of research and knowledge with the way AD and DNS must be designed PRIOR to
an upgrade/migration. It's very important to do your homework on this
because it becomes difficult to change. However, since you have W2k3 being
used, you may be able to change the name. But in order to do this, you must
upgrade the W2k server frst to W2k3 and raise the Forest Functional Level to
Native Mode. Here's a link on how to do that with W2k3:

Forest andDomain Functional Levels Explained:
http://www.microsoft.com/technet/treeview/default.asp? url=/technet/prodtechnol/windowsserver2003/proddocs/datacen
ter/sag_levels.asp

Renaming domains - rendom.exe found in valueadd-msft-mgmt- domren folder on
CD:
http://www.microsoft.com/technet/treeview/default.asp? url=/technet/prodtechnol/windowsserver2003/proddocs/datacen
ter/domainrename.asp

SP4 changed/stopped the fact of letting registrations work because MS found
that excessive DNS traffic was hitting the ISC Root servers with any machine
that had a single label name. It was just too much. So they stopped it. Now,
you can use a regsitry entry to force registration but this must be done on
ALL the machines in your domain.

Here is the fix that you can use for now. It's more of a bandaid, but will
not totally solve certain issues, but it will force registration of the SRV
records:
http://support.microsoft.com/?id=300684

This has to be done on all machines.

One BIG problem, however, if using single label names, GPOs will not work,
whether you use the registry entry metioned in that link above or not. This
is because they look for the domain name when the GetGPOList function runs
on a client when it tries to "find" the GPO. The path it looks for is such
as this because the policies are found in the domain share:
\\domain.com\sysvol\domain.COM\Policies

In your case, it would be querying for:
\\SOL\sysvol\SOL\policies

In that case, it will not be able to find that domain name because it;s
treating it as a HOST name. You can try to force this by ensuring there is a
blank HOST name called SOL with the IP addresses of one of the DCs, but from
other posters and tests, it doesn;t appear to really work correctly. Also,
XP clients have difficulty querying this method, whether you put the
registration fix in it or not.

Sorry to be the bearer of bad news. I hope this helps in understanding your
dilemma and what your options are.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
--
=================================


.
Click to expand...
 
In
Michael said:
Thanks again Ace Fekay!

I did a few changes before this answer and that is the
following.

1. I applied the fix for singel label domain on the w2k3
server and that one replicated it to the w2k server. But
you could only see the w2k3 server in the srv zones. This
did the site replication error over rpc.

2. I added in _msdcs a CNAME with the GUID name for w2k
servern. And that replicated over to the w2k3 servern. Now
RPC replication between the site connectors functions well.

Now when i test with dcdiag it seems to be okay.

I will change the order of dns that you writes about.
(I think thats one of the way i had it but i have changed
and test every way i could think about).

I still have the problems with adding "parameters" on w2k
server and w2k pro workstations. To solve this i think i
have to start an upgrade to native mode and get to
your "bad news" ;-)

Once again thx m8 i needed that extra brain >(-_-)<
Click to expand...



No prob for the help, just hate to bear bad news as has been lately with
this single label name issue and SP4. Apply that reg fix on your workstation
too, but can't guarantee anything on that since single label names are
problematic.

I wish you luck in your endeavors. At least you know what direction you need
to go.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Back
Top