- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
can not join xp to domain.
Dear Friends,
I have aMacBook with Vmware Fusion containing windows Xp and Windows 2003 Ent. Server. Mac Book is connected wirelessly with acor easy box
Dlink Router(192.168.2.1) .The Router is in DHCP enabled Mode.
Internet is working properly in all .The network adapter in Virtual Machine is Bridge Mode.
The ip address of Mac is :-
192.168.2.110
Subnet 255.255.255.0 ,
Default Gateway 192.168.2.1
Similarly Windows 2003 DHCP server got Ip address from routers When i make ipconifg/all in 2003 it will shows following details
192.168.2.114
Subnet 255.255.255.0 ,
Default Gateway 192.168.2.1 ,
DHCP Server:-192.168.2.1
, Dns Server 192.168.2.1
Simillary in Xp
192.168.2.115
Subnet 255.255.255.0 ,
Default Gateway 192.168.2.1 ,
DHCP Server:-192.168.2.1
, Dns Server 192.168.2.1
I can easily ping between XP and 2003 and also nslookup is working in both :-
Standardserver:-arcor.easybox
Address:- 192.168.2.1
Active Directory are well configured .I have also configure DNS server in 2003 but only Forward Lookupzone and Reverse-Lookupzone.Inside Forward lookup zone i can see
Haus.Luginsland.Tuebingen.com which is my Doman Name.And i have also added xp host here.
But when i want to join the xp machine( by clicking Xp desktop ,My computer ,properties and Changes to domain)
to the Member of Domain i will always get error message.I try to type domain name Haus.Luginsland.Tuebingen.com
But it shows always error message which is as follow.
An error occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain Haus.Luginsland.Tuebingen.com.
The error was: "No records found for given DNS query."
(error code 0x0000251D DNS_INFO_NO_RECORDS)
The query was for the SRV record for ldap.tcp.dc._msdcs.Haus.Luginsland.Tuebingen.com
I also try to use Netdiag and Dcdiag but i dont know how to use in Dos mode the command line does not accept.
Warm welcome for your answer.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi MatrixLuginsland,
I am not fimiliar with the MacBook or VMware Fusion but maybe I can offer some observations.
Similarly Windows 2003 DHCP server got Ip address from routers When i make ipconifg/all in 2003 it will shows following details
192.168.2.114
Subnet 255.255.255.0 ,
Default Gateway 192.168.2.1 ,
DHCP Server:-192.168.2.1
, Dns Server 192.168.2.1
I am assuming that the Windows 2003 DHCP is your Active Directory Domain Controller vm to which you wish the WinXP vm to join as a member of the domain. The AD domain controller should point to itself since it is acting as the DNS, DHCP and Domain Controller for a domain. The configuration you have now, will allow for Internet access through your router. Your router has DHCP service on in order to give the IP address to the AD domain controller 192.168.2.114 and then route to the Internet through the router gateway 192.168.2.1.
Simillary in Xp
192.168.2.115
Subnet 255.255.255.0 ,
Default Gateway 192.168.2.1 ,
DHCP Server:-192.168.2.1
, Dns Server 192.168.2.1
Your WinXP also as recieved it's ip address ( 192.168.2.115 ) from the router ( 192.168.2.1 ) so when you try the join the WinXP client vm to the Windows 2003 domain vm, the WinXP vm is pointing to the gateway of the router instead of gateway to the domain controller.
You will must likely have to add a second virtual nic to both your vms and configure them for a different subnet. Use one virtual nic for Internet access to the vms and use one virtual nic for the domain subnet.
You can use a 10.X.X.X subnet for your Windows domain. So for example configure the second nic on the domain controller like so:
IP - 10.1.1.1
Subnet - 255.255.255.0
Gateway - 10.1.1.1
DNS - 10.1.1.1
Your workstation should have an ip in the domain controller subnet such as:
IP - 10.1.1.10
Subnet - 255.255.255.0
Gateway - 10.1.1.1
DNS - 10.1.1.1
I would configure a static ip for the workstation and not use dhcp on the domain controller unless you want to work with the dhcp aspect of windows 2003 server.
Hope this helps
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re-install your domain controller operating system and reconfigure the domain name to something like this (e.g.. testlan.com) , Configure active directory, dns etc. again.
Disable the nic used for Internet connection ( 192.168.2.114) during the re-installation of the AD domain controller. The second nic will be used for the re-installation with the 10.1.1.1 ip. Name your virtual domain controller vm (something like win2k3svr)
After the re-installation, an ipconfig should show the host name: win2k3svr and the ip address information. Then try to join your workstation to the new domain just created.