dns error netlogon error

  • Thread starter Thread starter soundarrajan
  • Start date Start date
S

soundarrajan

hi all
i'm newly joined one institude(college), there is onely one win2k
server around 70 clients. giving following error so kindly give me a
solution
netlogon error

registration of the DNS record '_gc._tcp.student.ac.ae.600 in SRV 0
100 3268 Primary.student.ac.ae. 'failed with the following error:
DNS Server unable to interpret format

W32 time

This machine is a PDC of the domain at the root of the forest.
Configure
to sync from external time source using the net command, 'net
time/setsntp:
<server name>'


thanks & regards

soundarrajan
 
In
soundarrajan said:
hi all
i'm newly joined one institude(college), there is onely one win2k
server around 70 clients. giving following error so kindly give me a
solution
netlogon error

registration of the DNS record '_gc._tcp.student.ac.ae.600 in SRV 0
100 3268 Primary.student.ac.ae. 'failed with the following error:
DNS Server unable to interpret format

W32 time

This machine is a PDC of the domain at the root of the forest.
Configure
to sync from external time source using the net command, 'net
time/setsntp:
<server name>'


thanks & regards

soundarrajan
Click to expand...

The DNS error may possibly be due to pointing to a DNS server in your IP
properties that is not hosting the AD zone. Actually, with an AD network,
all domain members (DCs, clients and servers), need only use your internal
DNS server(s) only. Reason why, is AD stores it's resources and service
locations in DNS in the form of SRV records (those folders with the
underscore in them). They are used for a multitude of things, such as
finding the domain when a client logons, domain replication from one DC to
another, authentication, and more. To illustrate, if a client queried the
external DNS server with a query such as, "Where is my domain", will that
server have the answer? NO.

As for the error, it's trying to do it's normal default behavior to register
those resource and service locations into DNS. If it's poiinting somewhere
else, that's one of the errors that is generated.

Recommendation: Point all machines only to the internal server that is
hosting your AD zone, and configure a forwarder to your ISP's DNS or to your
university campus DNS. This way all machines query your DNS and if it
doesn't have the answer, it asks outside. If the forwarding option is grayed
out, delete the root zone, (it looks like a period), refresh the console,
and try again. If not sure how to configure this, this article will guide
you thru it:
http://support.microsoft.com/?id=300202

As for the W32Time error, that's due to not setting the time server on the
domain controller holding the PDC emulator role. Try this:
net stop time
net time /setsntp:192.5.41.41
w32tm -once
net start time


--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.
 
The registration is failing possibly due to the primary dns setting on the
machine being incorrect. Make sure the dns of the domain controller is on
your network and does not belong to an isp and is reachable. Verify that
the properties of the network adapter dns settings use a valid dns suffix
for your organization then stop and restart the netlogon service so it will
re-register. Make sure that your machine can resolve the time sync server
name to an ip address => nslookup time-server-name at a command prompt.

Lee
 
In
Lee said:
The registration is failing possibly due to the primary dns setting
on the machine being incorrect. Make sure the dns of the domain
controller is on your network and does not belong to an isp and is
reachable. Verify that the properties of the network adapter dns
settings use a valid dns suffix for your organization then stop and
restart the netlogon service so it will re-register. Make sure that
your machine can resolve the time sync server name to an ip address
=> nslookup time-server-name at a command prompt.
Click to expand...

You will also need to open UDP 123 on the firewall to the machine that holds
the PDC Emulator Role for NTP traffic. The time settings that I mentioned in
my post needs to be ONLY done on each domain's PDC Emulator. That is the
time synch server for all members of a domain. Each domain has their own.

Ace
 
Back
Top