Koozali.org: home of the SME Server
Obsolete Releases => SME Server 7.x => Topic started by: jsmith773 on March 17, 2008, 05:14:21 AM
-
Hey Guys
I am setting up a network in my home to test and practice networking skills. This is my setup Cable Modem -------> Router (DHCP Disabled)------>Sme Server
\
\
\------->XP MACHICE
\
------> VISTA MACHINE
\
-------->Os x machine
I have them all in a work group. I did setup a domain. domain.xxx. I have enabled domain controller in server manager and turned on dhcp. When using the ipconfig /all command I see the domain.xxx but when i try to add xp machine to domain i get an error (windows cannot find a domain controller). What am I doing wron the DNS server is the ip of the server and I can see and connect to ibays just fine. When i use cain and able (network auditing tool) it list the server as domain controller. I use this on the xp machine. What is the problem can you guys figure this out? What am I doing wrong? I've also added the registry file from http://servername/server-resources/r...winxplogon.reg
-
This is the error I get
Note: This information is intended for a network administrator. If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\WINDOWS\debug\dcdiag.txt.
The following error occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain domain.xxx:
The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)
The query was for the SRV record for _ldap._tcp.dc._msdcs.domain.xxx
Common causes of this error include the following:
- The DNS SRV record is not registered in DNS.
- One or more of the following zones do not include delegation to its child zone:
domain.xxx
local
. (the root zone)
For information about correcting this problem, click Help.
-
http://wiki.contribs.org/SME_Server:Documentation:Administration_Manual:Chapter7#Connecting_to_a_Domain
should help a bit.
-
for the XP computer use the admin account and password it will work fine also if that does not work log in as administrator in xp and do the same again i have done it the first way all good
with vista forget it you can try my way but i doubt it will work even trying to get vista to join a windows server 2003 is a pain in the ass you have to
also with the XP pc go in to c:\windows\system32\drivers\etc and edit the host file and and add the ipaddress of the server in there other wise it takes forever for XP also edit the Lmhosts.sam file and put the domain info in the but make sure you go file save as then save it as Lmhosts with out the sam info on the end windows will put the .txt at the end rename it and take the .txt off the end and reboot then do the domain stuff all should be good after that
-
also with the XP pc go in to c:\windows\system32\drivers\etc and edit the host file and and add the ipaddress of the server in there other wise it takes forever for XP also edit the Lmhosts.sam file and put the domain info in the but make sure you go file save as then save it as Lmhosts with out the sam info on the end windows will put the .txt at the end rename it and take the .txt off the end and reboot then do the domain stuff all should be good after that
This should not be necessary at all, just log in to your machine with a local administrator account, fill in the value you entered in the server-manager for the workgroup name in the field for the domain in windows and supply the admin (domain admin, the same as you use for the server-manager) credentials. There is absolutely no need to modify host files as this might result in problems in the future when IP ranges might be changed.
-
Thankyou guys I have resolved the issue by using the workgroup as the domain and creating a local account with the same credential as the server admin account
-
cactus you maybe right about the host files in windows but with a win2k3 server if you don't chabge the host files domain logons take for ever maybe just a force of habit as i work on both Linux and windows servers AD needs this stuff in