KCC error

  • Thread starter Thread starter eddiec
  • Start date Start date
E

eddiec

DC running RRAS for VPN. Windows accounting and authentication. IP config assigned via DHCP relay agent. Remote clients are unable to connect, connection times out on verifying username and pwd. There is no particular error that appears when clients try to connect. However the following general errors appear in the Event Log:



Error in Event Viewer / Directory Service for the KCC:

The attempt to establish a replication link with parameters

Partition: CN=Schema,CN=Configuration,DC=xyz,DC=com,

Source DSA DN: CN=NTDS Settings,CN=UTIL2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=xyz,DC=com

Source DSA Address: b836cecc-fbb1-4bca-baaf-3fc631d56f34._msdcs.xyz.com

Inter-site Transport (if any):


failed with the following status:

The DSA operation is unable to proceed because of a DNS lookup failure. The record data is the status code. This operation will be retried.





Error in Event Viewer / System Log for Remote Access:

Unable to contact a DHCP server. The Automatic Private IP Address 169.254.184.187 will be assigned to dial-in clients. Clients may be unable to access resources on the network.

How do I troubleshoot these errors?

TIA

eddiec :-)
 
eddiec says...
DC running RRAS for VPN. Windows accounting and authentication. IP config assigned via DHCP relay agent. Remote clients are unable to connect, connection times out on verifying username and pwd. There is no particular error that appears when clients try to connect. However the following general errors appear in the Event Log:

Error in Event Viewer / Directory Service for the KCC:

The attempt to establish a replication link with parameters
Partition: CN=Schema,CN=Configuration,DC=xyz,DC=com,
Source DSA DN: CN=NTDS Settings,CN=UTIL2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=xyz,DC=com
Source DSA Address: b836cecc-fbb1-4bca-baaf-3fc631d56f34._msdcs.xyz.com
Inter-site Transport (if any):
failed with the following status:
The DSA operation is unable to proceed because of a DNS lookup failure. The record data is the status code. This operation will be retried.

Error in Event Viewer / System Log for Remote Access:
Unable to contact a DHCP server. The Automatic Private IP Address 169.254.184.187 will be assigned to dial-in clients. Clients may be unable to access resources on the network.
How do I troubleshoot these errors?
Click to expand...
Hi Eddie,

fist make sure your DHCP-Server is working and assigns IP-Adresses and
the Network configuration to your clients.

Also make sure that the RRAS Server is configured to use the right
DNS-Server, I'd run netdiag and dcdiag out of the support tools on the
RAS-Server to get more specific informations what's wrong.

If you have any issues where you'll have questions, post the errors
from Netdiag and DcDiag and make sure you include your topology
informations about DCs and DNS.
 
hi Simon,

Netdiag came up with two errors. DNS registration for the VPN server was
incorrect on the DNS servers, also the error:
Failed to query SPN registration on DC

I ran Win2K SP4 on the VPN Server (KB 297384 advises run SP3 to fix this
error) and now all is sweet.

Vielen dank,

eddiec :-)

Ulf B. Simon-Weidner said:
eddiec says...
Click to expand...
config assigned via DHCP relay agent. Remote clients are unable to connect,
connection times out on verifying username and pwd. There is no particular
error that appears when clients try to connect. However the following
general errors appear in the Event Log:
Settings,CN=UTIL2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configur
ation,DC=xyz,DC=com
Click to expand...
169.254.184.187 will be assigned to dial-in clients. Clients may be unable
to access resources on the network.
 
eddiec says...
hi Simon,

Netdiag came up with two errors. DNS registration for the VPN server was
incorrect on the DNS servers, also the error:
Failed to query SPN registration on DC

I ran Win2K SP4 on the VPN Server (KB 297384 advises run SP3 to fix this
error) and now all is sweet.

Vielen dank,

eddiec :-)
Click to expand...
Hello eddiec,

you're welcome - I'm glad it helped ;-)
 
Back
Top