[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 319
  • Last Modified:

DNS Update Problem? Or Windows XP problem?

Hi there,

I've set up a clean install of a Windows 2003 SMB Edition Server a while ago.

Now everything works fine, with my PC's i can PING everyone, and back. Except for 1 laptop!
This laptop used to be in the old domain before i reïnstalled it so what i did was remove the laptop from the old domain,
changed his computer name, joined the laptop to the new domain (same domain name though).

Now on the laptop i can ping everyone, even myself. But the others cannot Ping the laptop, not on IP nor on its name.

I've rebooted the laptop and the server multiple times (once let the laptop turned on just rebooted the server, once let the server run rebooted the laptop, once shutdown laptop reboot server, restart laptop etc.)

But it still doesn't fix it.

On my server i have the following 3 errors in the DNS although i don't know how to fix them.


code: 4004
Last date: 20-03-2006

The DNS server was unable to complete directory service enumeration of zone BVDOMEIN.BVLAN.  This DNS server is configured to use information obtained from Active Directory for this zone and is unable to load the zone without it.  Check that the Active Directory is functioning properly and repeat enumeration of the zone. The extended error debug information (which may be empty) is "". The event data contains the error.

code: 4015
Last date: 20-03-2006

The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly. The extended error debug information (which may be empty) is "". The event data contains the error.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

code: 6702
Last date: 03-04-2006

DNS server has updated its own host (A) records.  In order to ensure that its DS-integrated peer DNS servers are able to replicate with this server, an attempt was made to update them with the new records through dynamic update.  An error was encountered during this update, the record data is the error code.
 
If this DNS server does not have any DS-integrated peers, then this error
should be ignored.
 
If this DNS server's Active Directory replication partners do not have the correct IP address(es) for this server, they will be unable to replicate with it.
 
To ensure proper replication:
1) Find this server's Active Directory replication partners that run the DNS server.
2) Open DnsManager and connect in turn to each of the replication partners.
3) On each server, check the host (A record) registration for THIS server.
4) Delete any A records that do NOT correspond to IP addresses of this server.
5) If there are no A records for this server, add at least one A record corresponding to an address on this server, that the replication partner can contact.  (In other words, if there multiple IP addresses for this DNS server, add at least one that is on the same network as the Active Directory DNS server you are updating.)
6) Note, that is not necessary to update EVERY replication partner.  It is only necessary that the records are fixed up on enough replication partners so that every server that replicates with this server will receive (through replication) the new data.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Warnings

code: 2630
Last Date: 14-03-2006

The DNS server could not configure the network connections of this computer with the local computer's IP address as the preferred DNS server, because this computer is connected to networks with different or invalid DNS namespaces. Manual configuration of the local DNS server to perform name resolution on one or more of the namespaces is required before the preferred DNS servers of this computer should be modified.
 
If the network connections of this computer are not configured with the local computer's IP address as the preferred DNS server, this computer may not be able to dynamically register DC locator records in DNS. Absence of these records may prevent other Active Directory domain controllers and domain members from locating this domain controller.
 
User Action:
 
Ensure that DC locator DNS records enumerated in the file %SystemRoot%\system32\config\netlogon.dns are registered on the local DNS server. If these records are not registered in DNS:
a) Add a delegation to this DNS server to parent DNS zone matching the name of the Active Directory domain OR
b) Configure the local DNS server with appropriate root hints and forwarders (if necessary) and configure the network connections of this computer with the local computer's IP address as the preferred DNS server. Note that other computers using other DNS servers as their preferred or alternate DNS servers may not be able to locate this domain controller, unless the DNS infrastructure is properly configured.


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Code: 414
Last Date: 14-03-2006

The DNS server machine currently has no DNS domain name.  Its DNS name is a single label hostname with no domain (example:  "host" rather than "host.microsoft.com").
 
You might have forgotten to configure a primary DNS domain for the server computer. For more information, see either "DNS server log reference" or "To configure the primary DNS suffix for a client computer" in the online Help.
 
While the DNS server has only a single label name, all zones created will have default records (SOA and NS) created using only this single label name for the server's hostname.  This can lead to incorrect and failed referrals when clients and other DNS servers use these records to locate this server by name.
 
To correct this problem:
  1) open Control Panel
  2) open System applet
  3) select Computer Name tab
  4) click the "Change" button and join the computer to a domain or workgroup; this name will be used as your DNS domain name
  5) reboot to initialize with new domain name
 
After reboot, the DNS server will attempt to fix up default records, substituting new DNS name of this server, for old single label name.  However, you should review to make sure zone's SOA and NS records now properly use correct domain name of this server.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

I do NOT have a "." zone
I do have a BVDOMEIN.BVLAN zone with all PC's including the laptop listed
and a _msdcs.BVDOMEIN.BVLAN zone with the SOA, NS and CNAME.

I can ping internet adresses and visit them, its just that 1 laptop.

0
PatrickAdrichem
Asked:
PatrickAdrichem
  • 2
1 Solution
 
Jay_Jay70Commented:
Hi PatrickAdrichem,

check that the workstation service is enabled and that the windows firewall service is disabled, try rerunning the network ID wizard to recconect to Domain - triple check your dns settings and make sure they all point correctly        then we go again :)   also try running DCDIAG on your DC just to ensure no problems at that end

Cheers!
0
 
PatrickAdrichemAuthor Commented:
Disabling the firewall fixed the problem, Nice of microsoft to create something to prohibit their own software from working correctly lol!

thnx for the answer! =)
0
 
Jay_Jay70Commented:
another magical microsoft show of intelligence yes :)

cheers
0

Featured Post

Veeam Disaster Recovery in Microsoft Azure

Veeam PN for Microsoft Azure is a FREE solution designed to simplify and automate the setup of a DR site in Microsoft Azure using lightweight software-defined networking. It reduces the complexity of VPN deployments and is designed for businesses of ALL sizes.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now