RE: 2003 DNS problems on VMware

when joining the workstation to the domain did you use the fqdn? "MCSA.CO.UK"

"gstar" wrote:

Hi,
For a test lab I am using 2003 enterprise edition, I work with
standard daily so thought it would be OK but have hit a wall with what
I think is DNS?

The 2003 box and XP box are running as virtual machines [vmware]as
follows:
vmxp1 10.10.10.3
vmdc1 10.10.0.10

Now everything is up and running on both boxes with the server setup
as DHCP, DNS, WINS & DC roles but the XP client cannot join the domain
no matter what I try. From vmxp1 I can ping the server by IP or DNS
name, nslookup is OK and can access the HDD so I dont think its
specifically network related.

below I have detailed ipconfig & NSLOOKUP, Netdiag...?

Lastly, the DC event vwr app log, I keep getting Userenv alerts
1006 - Windows cannot bind to MCSA.co.uk domain [local error]. group
Policy aborted.
1053 - Windows cannot obtain the domain controller name for your
computer network

Windows IP Configuration VMXP1

Host Name . . . . . . . . . . . . : vmxp1
Primary Dns Suffix . . . . . . . : mcsa.co.uk
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : mcsa.co.uk
co.uk

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Accelerated AMD
PCNet Adapter

Physical Address. . . . . . . . . : 00-0C-29-68-82-50
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 10.10.10.3
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.10.10.2
DHCP Server . . . . . . . . . . . : 10.10.10.10
DNS Servers . . . . . . . . . . . : 10.10.10.10
Primary WINS Server . . . . . . . : 10.10.10.10
Lease Obtained. . . . . . . . . . : 20 March 2007 13:17:15
Lease Expires . . . . . . . . . . : 28 March 2007 13:17:15


C:\Documents and Settings\Administrator\VMXP1>nslookup
Default Server: vmdc1.mcsa.co.uk
Address: 10.10.10.10

nslookup
Server: vmdc1.mcsa.co.uk
Address: 10.10.10.10

Non-authoritative answer:
Name: nslookup.co.uk
Address: 82.152.134.170
_______________________________________________________________________
Windows IP Configuration VMDC1

Host Name . . . . . . . . . . . . : VMDC1
Primary Dns Suffix . . . . . . . : MCSA.CO.UK
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : MCSA.CO.UK
CO.UK

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Accelerated AMD PCNet
Adapter
Physical Address. . . . . . . . . : 00-0C-29-36-69-39
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.10.10.10
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.10.10.2
DNS Servers . . . . . . . . . . . : 10.10.10.10
Primary WINS Server . . . . . . . : 10.10.10.10


C:\Documents and Settings\Administrator.VM_DC1>nslookup
Default Server: vmdc1.mcsa.co.uk
Address: 10.10.10.10

nslookup
Server: vmdc1.mcsa.co.uk
Address: 10.10.10.10

Non-authoritative answer:
Name: nslookup.CO.UK
Address: 82.152.134.170


_______________________________________________________________________

WHEN ATTEMPTING TO JOIN DOMAIN FROM VMXP1 I RECEIVE THIS ERROR:

The domain name MCSA might be a NetBIOS domain name. If this is the
case, verify that the domain name is properly registered with WINS.
If you are certain that the name is not a NetBIOS domain name, then
the following information can help you troubleshoot your DNS
configuration.
DNS was successfully queried for the service location (SRV) resource
record used to locate a domain controller for domain MCSA:

The query was for the SRV record for _ldap._tcp.dc._msdcs.MCSA
The following domain controllers were identified by the query:
vmdc1.mcsa.co.uk
Common causes of this error include:
- Host (A) records that map the name of the domain controller to its
IP addresses are missing or contain incorrect addresses.
- Domain controllers registered in DNS are not connected to the
network or are not running.

DCDIAG ON VMDC1


Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\VMDC1
Starting test: Connectivity
......................... VMDC1 passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\VMDC1
Starting test: Replications
......................... VMDC1 passed test Replications
Starting test: NCSecDesc
......................... VMDC1 passed test NCSecDesc
Starting test: NetLogons
Unable to connect to the NETLOGON share! (\\VMDC1\netlogon)
[VMDC1] An net use or LsaPolicy operation failed with error
1203, Win32 Error 1203.
......................... VMDC1 failed test NetLogons
Starting test: Advertising
Fatal Error:DsGetDcName (VMDC1) call failed, error 1355
The Locator could not find the server.
......................... VMDC1 failed test Advertising
Starting test: KnowsOfRoleHolders
......................... VMDC1 passed test
KnowsOfRoleHolders
Starting test: RidManager
......................... VMDC1 passed test RidManager
Starting test: MachineAccount
......................... VMDC1 passed test MachineAccount
Starting test: Services
......................... VMDC1 passed test Services
Starting test: ObjectsReplicated
......................... VMDC1 passed test ObjectsReplicated
Starting test: frssysvol
......................... VMDC1 passed test frssysvol
Starting test: frsevent
There are warning or error events within the last 24 hours
after the

SYSVOL has been shared. Failing SYSVOL replication problems
may cause

Group Policy problems.
......................... VMDC1 failed test frsevent
Starting test: kccevent
......................... VMDC1 passed test kccevent
Starting test: systemlog
......................... VMDC1 passed test systemlog
Starting test: VerifyReferences
......................... VMDC1 passed test VerifyReferences

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

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

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 : MCSA
Starting test: CrossRefValidation
......................... MCSA passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... MCSA passed test CheckSDRefDom

Running enterprise tests on : MCSA.CO.UK
Starting test: Intersite
......................... MCSA.CO.UK passed test Intersite
Starting test: FsmoCheck
Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error
1355
A Global Catalog Server could not be located - All GC's are
down.
Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
A Time Server could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed,
error 1355
A Good Time Server could not be located.
Warning: DcGetDcName(KDC_REQUIRED) call failed, error 1355
A KDC could not be located - All the KDCs are down.
......................... MCSA.CO.UK failed test FsmoCheck



Many thanx,

G


.

Relevant Pages

  • Re: BDC DCDIAG Problem
    ... I just set up DNS as a backup DNS server according to the MS procedure I ... Running partition tests on: ForestDnsZones ... Starting test: CrossRefValidation ...
    (microsoft.public.windows.server.sbs)
  • Re: BDC DCDIAG Problem
    ... the DNS was removed and reinstalled on the BDC, ... ensure that you can contact the server that authenticated you.. ... Running partition tests on: ForestDnsZones ... Starting test: CrossRefValidation ...
    (microsoft.public.windows.server.sbs)
  • Re: Windows 2003 NtFrs Event 13508 sysvoldomain
    ... Testing server: Flemington\domainDC1 ... Running partition tests on: ForestDnsZones ... Starting test: CrossRefValidation ... PASS - All the DNS entries for DC are registered on DNS server ...
    (microsoft.public.windows.server.active_directory)
  • Re: 2008 replication
    ... I was not aware of these server tools - so thanks ... AD running successfully before adding the DNS roles. ... Running partition tests on: ForestDnsZones ... Starting test: CrossRefValidation ...
    (microsoft.public.windows.server.active_directory)
  • Re: Windows 2003 NtFrs Event 13508 sysvoldomain
    ... Testing server: Flemington\domainDC1 ... Running partition tests on: ForestDnsZones ... Starting test: CrossRefValidation ... PASS - All the DNS entries for DC are registered on DNS server ...
    (microsoft.public.windows.server.active_directory)
Loading