replication problem

  • Thread starter Thread starter ad
  • Start date Start date
A

ad

i got problem with replication - "the rpc server in unavailable"
i check possibilities and i found that problem is in dns - "subfolders"
_MSDCS _SITES _TCP and _UDP points to old server that doesn't exists now.
can i modify those manually (change name from old server to new)? or is this
other way to do it?

tia
Ad
 
In
ad said:
i got problem with replication - "the rpc server in unavailable"
i check possibilities and i found that problem is in dns -
"subfolders" _MSDCS _SITES _TCP and _UDP points to old server that
doesn't exists now. can i modify those manually (change name from old
server to new)? or is this other way to do it?

tia
Ad

If everything is working properly, the SRVs should have updated normally
with the current info. If a server had been removed improperly (such as
yanking it/unplugging it out of the network instead of demoting it properly)
then the old server reference would still be in AD the AD databse and the
netlogon service is registering that information into the SRVs, which is
normal.

You can also try:
1 Delete the system32\config\netlogon.dns and netlogon.dnb files.
2 ipconfig /registerdns
3 net stop netlogon
4 net start netlogon

That will refresh the SRV records. If the old reference is still there, then
I would suspect an improper demotion of a server.

This is of course, all assuming that you are only pointing to your internal
DNS server and do not have any listing of an ISP's DNS server in your IP
properties (DCs or clients for that matter), which is the proper
recommendation for an AD infrasstructure, no matter what size.

Hope that 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
 
You can also try:
1 Delete the system32\config\netlogon.dns and netlogon.dnb files.
2 ipconfig /registerdns
3 net stop netlogon
4 net start netlogon

i have already done it but it doesn't work.
That will refresh the SRV records. If the old reference is still there, then
I would suspect an improper demotion of a server.

yes this server was improperlly demote. what else can i do?

tia
 
can anyone help me? i got to clean the mess left by previous administrator
and i just got no idea what to do (i try every procedures i found on the
microsoft site and in newsgroups and one last thing i am thinking of is
manually correct this entries).

TIA
 
In
Ad said:
can anyone help me? i got to clean the mess left by previous
administrator and i just got no idea what to do (i try every
procedures i found on the microsoft site and in newsgroups and one
last thing i am thinking of is manually correct this entries).

TIA

Post an unedited ipconfig /all and your domain name from ADU&C so we can
start.
 
Post an unedited ipconfig /all and your domain name from ADU&C so we can

sorry but i cant make oe to keep original format of file


Windows 2000 IP Configuration



Host Name . . . . . . . . . . . . : rd21
Primary DNS Suffix . . . . . . . : xixixxum
Node Type . . . . . . . . . . . . : Broadcast

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : kprk.pl
xixixxum

Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82540EM Based Network
Connection
Physical Address. . . . . . . . . : 00-C0-9F-25-C4-C8

DHCP Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 10.1.4.28

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 10.1.1.1

DNS Servers . . . . . . . . . . . : 10.1.4.28
10.4.1.4
 
In
This is fine thanks for the post of your ipconfig. The most serious problem
which is probably causing most of your issues is the single label domain
name "xixixxum" IF this is your actual domain name (I asked for that, but
you did not give it), this causes registration problems for Win2kSP4, Win XP
and Win2k3
If "xixixxum" is not your domain name in ADU&C then this is a disjointed
name space for which I can provide you with a script to fix but, I need
verification of yiour domain name before I can recommend changing your
primary DNS suffix.

If "xixixxum" is your domain name from ADU&C, you will have to make the
registry entries from this KB article to allow your DCs to register in DNS,
you will also have to make registry entries on the afformentioned clients to
allow them to find the DCs in this domain.
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

Your only other choice is to demote your DCs and promote them with a good
DNS name with a "." in the name. You will lose all accounts when you demote
your DC so you really do not have much of a choice but to make the reg
entries on all domain members. if you have a lot of machines you may want to
create a registry file for each OS to save time.

I also notice you have this name in your search list kprk.pl, if your local
DNS server does not have this zone I recommend removing that because that
name will be appended to all DNS queries which will greatly increase DNS
traffic to your forwarder and to the internet root servers.


Windows 2000 IP Configuration



Host Name . . . . . . . . . . . . : rd21
Primary DNS Suffix . . . . . . . : xixixxum
Node Type . . . . . . . . . . . . : Broadcast

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : kprk.pl <---If your DNS does not have
this zone you should remove this it cauuses many extra queries to go out.
xixixxum

Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82540EM Based Network
Connection
Physical Address. . . . . . . . . : 00-C0-9F-25-C4-C8

DHCP Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 10.1.4.28

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 10.1.1.1

DNS Servers . . . . . . . . . . . : 10.1.4.28
10.4.1.4 <--Another DC is
hope? If not remove this.
 
In
Ad said:
sorry but i cant make oe to keep original format of file


Windows 2000 IP Configuration



Host Name . . . . . . . . . . . . : rd21
Primary DNS Suffix . . . . . . . : xixixxum
Node Type . . . . . . . . . . . . : Broadcast

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : kprk.pl
xixixxum

Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82540EM Based Network
Connection
Physical Address. . . . . . . . . : 00-C0-9F-25-C4-C8

DHCP Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 10.1.4.28

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 10.1.1.1

DNS Servers . . . . . . . . . . . : 10.1.4.28
10.4.1.4

Sorry it took so long to get back to you. Busy...

Now I see why you're having problems. The single label name. Follow Kevin;s
suggestions.

--
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
 
Now I see why you're having problems. The single label name. Follow Kevin;s
suggestions.


thnx for help i try it tommorow at job

this is my domain name - i know it is "strange" single label and but it was
already when i start working :)

i completely forgot to say one importand thing - some time ago replication
was working fine with this domain - i think problem start when old DC was
improperly demote (i can't be sure cause i wasn't administering this serwer
that time) . maybe this help You to find another solution if that fail - i
will report what has happend tommorow.

best regards
Ad
 
In
Ad said:
thnx for help i try it tommorow at job

this is my domain name - i know it is "strange" single label and but
it was already when i start working :)

i completely forgot to say one importand thing - some time ago
replication was working fine with this domain - i think problem start
when old DC was improperly demote (i can't be sure cause i wasn't
administering this serwer that time) . maybe this help You to find
another solution if that fail - i will report what has happend
tommorow.

best regards
Ad

It was working previously probably before you installed SP4. SP4 has changes
that stops single label name registrations (due to excessive traffic from MS
DNS servers that have single label name zones to the Internet Root servers).

Looking forward to your report.

--
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
 
It was working previously probably before you installed SP4. SP4 has changes
that stops single label name registrations (due to excessive traffic from MS
DNS servers that have single label name zones to the Internet Root
servers).

well today i got too much work to check it out but tommorow i got night
shift so i will report u tommorow night.

regards
Ad
 
ok i did what You advise me
replication still doesn't work - same error but in dns in folders _MSDCS
_SITES _TCP and _UDP appear new entries pointing to my second domain
cotroller - but there are still records from this old one and there are none
pointing to current primary DC.

TIA
Ad
 
In
ad said:
ok i did what You advise me
replication still doesn't work - same error but in dns in folders
_MSDCS _SITES _TCP and _UDP appear new entries pointing to my second
domain cotroller - but there are still records from this old one and
there are none pointing to current primary DC.

TIA
Ad

You set that reg entry from article 300684 and it still doesn't work?

If the old server is still showing up in the SRVs, then possibly that
machine is still being referenced in AD ansd it was not removed properly.
Netlogon will always refresh the records of what it finds in AD. You may
havet to do a Metadata cleanup of AD to remove that name.

Look at this article:

HOW TO Remove Data in Active Directory After an Unsuccessful Domain
Controller Demotion Q216498:
http://support.microsoft.com/?id=216498

216364 - Domain Controller Server Object Not Be Removed After Demotion [ADUC
or NTDSUTIL]:
http://support.microsoft.com/?id=216364



--
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
 
In
ad said:
finally repliaction is working again!!

thanx for help

Best Regards
Ad

Good to hear!
;-)

Merry Christmas and a Happy New Year!


--
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