cannot join WinXP to Windows 2000 domain
in [Active Directory]
|
From: Meinolf Weber on 24 Jun 2008 19:28 Hello Russell, If i check the files you have connected two different networks ,CSS and hilldale in one ip network and use the hilldale DHCP for the other domain? Is this correc? Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights. ** Please do NOT email, only reply to Newsgroups ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm > dcdiags. > > "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message > news:ff16fb66a10928ca9b8770d82565(a)msnews.microsoft.com... > >> Hello Russell, >> >> Please post the output from netdiag /v and dcdiag /v. Additional post >> an unedited ipconfig /all from both servers and the client machine. >> >> Best regards >> >> Meinolf Weber >> Disclaimer: This posting is provided "AS IS" with no warranties, and >> confers >> no rights. >> ** Please do NOT email, only reply to Newsgroups >> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm >>> Below is the error message when attempting to join domain. It finds >>> the DC. nslookup can resolve the DC both forward and backward, so it >>> seems that the A record for DC must be right. >>> >>> Now, here is the odd situation. This W2000 DC (Domain1) is using >>> another server W2003 DC (Domain2) for it's DNS and the LAN's DHCP >>> services. (I think this was done so the LAN would have a single >>> DHCP server.) >>> >>> I would even be willing to move the W2000 DNS services to reside on >>> the Domain1 DC if that would solve problem. I'm not sure how to get >>> all the DNS records set up for Active Directory if not done as part >>> of the original dcpromo. >>> >>> Any further advice appreciated. Russell >>> >>> ----- >>> DNS was successfully queried for the service location (SRV) resource >>> record >>> used to locate a domain controller for domain ccs: >>> The query was for the SRV record for _ldap._tcp.dc._msdcs.ccs >>> The following domain controllers were identified by the query: >>> ccsserver.ccs >>> 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. >>> For information about correcting this problem, click Help. >>> Search the Web: >>> domain name >>> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message >>> news:ff16fb66a0eab8ca9ab647b6ec2e(a)msnews.microsoft.com... >>>> Hello Russell, >>>> >>>> What is the error message during the join process? >>>> Also you mix a bit 2 different items, client join problem and DC >>>> diagnostic/troubleshooting >>>> tools. So if you think there are domain problems run dcdiag, >>>> netdiag >>>> and >>>> repadmin /showreps and post the complete output here. For the >>>> clients >>>> check >>>> that they have the correct ip settings, subnet mask and only domain >>>> internal >>>> DNS server. Make sure that no firewall is enabled. >>>> Best regards >>>> Meinolf Weber >>>> Disclaimer: This posting is provided "AS IS" with no warranties, >>>> and >>>> confers >>>> no rights. >>>> ** Please do NOT email, only reply to Newsgroups >>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm >>>>> I have previously been successful joining WinXP PC to this Win2000 >>>>> domain. Have 2 new PCs with WinXP SP3 that will not join the >>>>> domain. dcdiag.txt output is show below. nslookup resolves the >>>>> server name fine. I do not have reverse DNS zone configured. >>>>> (never needed that in past for joining PC to this domain). I'm >>>>> stumped. Any suggestions appreciated. Russell >>>>> >>>>> ------dcdiag.txt ___ >>>>> The domain name ccs 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 ccs: >>>>> The query was for the SRV record for _ldap._tcp.dc._msdcs.ccs The >>>>> following domain controllers were identified by the query: >>>>> ccsserver.ccs >>>>> >>>>> 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. >>>>> For information about correcting this problem, click Help. >>>>> -----
From: Russell on 25 Jun 2008 09:35 Yes, a single LAN that has 2 unrelated Domains, CCS (w2000)and HILLDALE.LOCAL (w2003). Each domain has its own individual DC. The DC serving HILLDALE.LOCAL is also providing DHCP and DNS services for the entire LAN including the CCS domain member PCs. I sent you the diagnostic logs from both DCs and couple of client PCs. I even attempted to simplify the situation by removing the w2003 from the equation by pointing a client PC's DNS to the the w2000 DC. That did not work either, but I suspect because I don't have the DNS services on the W2000 configured exactly right. I'm willing to try almost anything to get this resolved, so I appreciate any thoughts you can offer. thanks, Russell "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message news:ff16fb66a1f438caa479f0ccfbb3(a)msnews.microsoft.com... Hello Russell, If i check the files you have connected two different networks ,CSS and hilldale in one ip network and use the hilldale DHCP for the other domain? Is this correc? Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights. ** Please do NOT email, only reply to Newsgroups ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm > dcdiags. > > "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message > news:ff16fb66a10928ca9b8770d82565(a)msnews.microsoft.com... > >> Hello Russell, >> >> Please post the output from netdiag /v and dcdiag /v. Additional post >> an unedited ipconfig /all from both servers and the client machine. >> >> Best regards >> >> Meinolf Weber >> Disclaimer: This posting is provided "AS IS" with no warranties, and >> confers >> no rights. >> ** Please do NOT email, only reply to Newsgroups >> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm >>> Below is the error message when attempting to join domain. It finds >>> the DC. nslookup can resolve the DC both forward and backward, so it >>> seems that the A record for DC must be right. >>> >>> Now, here is the odd situation. This W2000 DC (Domain1) is using >>> another server W2003 DC (Domain2) for it's DNS and the LAN's DHCP >>> services. (I think this was done so the LAN would have a single >>> DHCP server.) >>> >>> I would even be willing to move the W2000 DNS services to reside on >>> the Domain1 DC if that would solve problem. I'm not sure how to get >>> all the DNS records set up for Active Directory if not done as part >>> of the original dcpromo. >>> >>> Any further advice appreciated. Russell >>> >>> ----- >>> DNS was successfully queried for the service location (SRV) resource >>> record >>> used to locate a domain controller for domain ccs: >>> The query was for the SRV record for _ldap._tcp.dc._msdcs.ccs >>> The following domain controllers were identified by the query: >>> ccsserver.ccs >>> 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. >>> For information about correcting this problem, click Help. >>> Search the Web: >>> domain name >>> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message >>> news:ff16fb66a0eab8ca9ab647b6ec2e(a)msnews.microsoft.com... >>>> Hello Russell, >>>> >>>> What is the error message during the join process? >>>> Also you mix a bit 2 different items, client join problem and DC >>>> diagnostic/troubleshooting >>>> tools. So if you think there are domain problems run dcdiag, >>>> netdiag >>>> and >>>> repadmin /showreps and post the complete output here. For the >>>> clients >>>> check >>>> that they have the correct ip settings, subnet mask and only domain >>>> internal >>>> DNS server. Make sure that no firewall is enabled. >>>> Best regards >>>> Meinolf Weber >>>> Disclaimer: This posting is provided "AS IS" with no warranties, >>>> and >>>> confers >>>> no rights. >>>> ** Please do NOT email, only reply to Newsgroups >>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm >>>>> I have previously been successful joining WinXP PC to this Win2000 >>>>> domain. Have 2 new PCs with WinXP SP3 that will not join the >>>>> domain. dcdiag.txt output is show below. nslookup resolves the >>>>> server name fine. I do not have reverse DNS zone configured. >>>>> (never needed that in past for joining PC to this domain). I'm >>>>> stumped. Any suggestions appreciated. Russell >>>>> >>>>> ------dcdiag.txt ___ >>>>> The domain name ccs 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 ccs: >>>>> The query was for the SRV record for _ldap._tcp.dc._msdcs.ccs The >>>>> following domain controllers were identified by the query: >>>>> ccsserver.ccs >>>>> >>>>> 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. >>>>> For information about correcting this problem, click Help. >>>>> -----
From: Meinolf Weber on 25 Jun 2008 12:25 Hello Russell, So the DNS server hosts 2 different zones for both domains? Please post the DHCP scope settings. Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights. ** Please do NOT email, only reply to Newsgroups ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm > Yes, a single LAN that has 2 unrelated Domains, CCS (w2000)and > HILLDALE.LOCAL (w2003). Each domain has its own individual DC. The > DC serving HILLDALE.LOCAL is also providing DHCP and DNS services for > the entire LAN including the CCS domain member PCs. I sent you the > diagnostic logs from both DCs and couple of client PCs. > > I even attempted to simplify the situation by removing the w2003 from > the equation by pointing a client PC's DNS to the the w2000 DC. That > did not work either, but I suspect because I don't have the DNS > services on the W2000 configured exactly right. > > I'm willing to try almost anything to get this resolved, so I > appreciate any thoughts you can offer. thanks, Russell > > "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message > news:ff16fb66a1f438caa479f0ccfbb3(a)msnews.microsoft.com... Hello > Russell, > > If i check the files you have connected two different networks ,CSS > and hilldale in one ip network and use the hilldale DHCP for the other > domain? Is this correc? > > Best regards > > Meinolf Weber > Disclaimer: This posting is provided "AS IS" with no warranties, and > confers > no rights. > ** Please do NOT email, only reply to Newsgroups > ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm >> dcdiags. >> >> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message >> news:ff16fb66a10928ca9b8770d82565(a)msnews.microsoft.com... >> >>> Hello Russell, >>> >>> Please post the output from netdiag /v and dcdiag /v. Additional >>> post an unedited ipconfig /all from both servers and the client >>> machine. >>> >>> Best regards >>> >>> Meinolf Weber >>> Disclaimer: This posting is provided "AS IS" with no warranties, and >>> confers >>> no rights. >>> ** Please do NOT email, only reply to Newsgroups >>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm >>>> Below is the error message when attempting to join domain. It >>>> finds the DC. nslookup can resolve the DC both forward and >>>> backward, so it seems that the A record for DC must be right. >>>> >>>> Now, here is the odd situation. This W2000 DC (Domain1) is using >>>> another server W2003 DC (Domain2) for it's DNS and the LAN's DHCP >>>> services. (I think this was done so the LAN would have a single >>>> DHCP server.) >>>> >>>> I would even be willing to move the W2000 DNS services to reside on >>>> the Domain1 DC if that would solve problem. I'm not sure how to >>>> get all the DNS records set up for Active Directory if not done as >>>> part of the original dcpromo. >>>> >>>> Any further advice appreciated. Russell >>>> >>>> ----- >>>> DNS was successfully queried for the service location (SRV) >>>> resource >>>> record >>>> used to locate a domain controller for domain ccs: >>>> The query was for the SRV record for _ldap._tcp.dc._msdcs.ccs >>>> The following domain controllers were identified by the query: >>>> ccsserver.ccs >>>> 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. >>>> For information about correcting this problem, click Help. >>>> Search the Web: >>>> domain name >>>> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message >>>> news:ff16fb66a0eab8ca9ab647b6ec2e(a)msnews.microsoft.com... >>>>> Hello Russell, >>>>> >>>>> What is the error message during the join process? >>>>> Also you mix a bit 2 different items, client join problem and DC >>>>> diagnostic/troubleshooting >>>>> tools. So if you think there are domain problems run dcdiag, >>>>> netdiag >>>>> and >>>>> repadmin /showreps and post the complete output here. For the >>>>> clients >>>>> check >>>>> that they have the correct ip settings, subnet mask and only >>>>> domain >>>>> internal >>>>> DNS server. Make sure that no firewall is enabled. >>>>> Best regards >>>>> Meinolf Weber >>>>> Disclaimer: This posting is provided "AS IS" with no warranties, >>>>> and >>>>> confers >>>>> no rights. >>>>> ** Please do NOT email, only reply to Newsgroups >>>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm >>>>>> I have previously been successful joining WinXP PC to this >>>>>> Win2000 domain. Have 2 new PCs with WinXP SP3 that will not join >>>>>> the domain. dcdiag.txt output is show below. nslookup resolves >>>>>> the server name fine. I do not have reverse DNS zone configured. >>>>>> (never needed that in past for joining PC to this domain). I'm >>>>>> stumped. Any suggestions appreciated. Russell >>>>>> >>>>>> ------dcdiag.txt ___ >>>>>> The domain name ccs 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 ccs: >>>>>> The query was for the SRV record for _ldap._tcp.dc._msdcs.ccs The >>>>>> following domain controllers were identified by the query: >>>>>> ccsserver.ccs >>>>>> 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. >>>>>> For information about correcting this problem, click Help. >>>>>> -----
From: Russell on 25 Jun 2008 20:51 Yes, a seperate DNS zone for each windows domain. dhcp scope properties: start ip 192.168.2.33 end ip 192.168.2.149 Lease duration: 180 days DNS tab-Checked: Enable DNS dynamic update according to the settings below Selected: Always dynamicaly update DNS A and PTR records Checked: Dynamically update DNS A and PTR records for DHCP clients that do not request updates. Advanced tab: DHCP only. Any thoughts appreciated. Russell "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message news:ff16fb66a20268caa507f17ee734(a)msnews.microsoft.com... > Hello Russell, > > So the DNS server hosts 2 different zones for both domains? Please post > the > DHCP scope settings. > > Best regards > > Meinolf Weber > Disclaimer: This posting is provided "AS IS" with no warranties, and > confers > no rights. > ** Please do NOT email, only reply to Newsgroups > ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm > >> Yes, a single LAN that has 2 unrelated Domains, CCS (w2000)and >> HILLDALE.LOCAL (w2003). Each domain has its own individual DC. The >> DC serving HILLDALE.LOCAL is also providing DHCP and DNS services for >> the entire LAN including the CCS domain member PCs. I sent you the >> diagnostic logs from both DCs and couple of client PCs. >> >> I even attempted to simplify the situation by removing the w2003 from >> the equation by pointing a client PC's DNS to the the w2000 DC. That >> did not work either, but I suspect because I don't have the DNS >> services on the W2000 configured exactly right. >> >> I'm willing to try almost anything to get this resolved, so I >> appreciate any thoughts you can offer. thanks, Russell >> >> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message >> news:ff16fb66a1f438caa479f0ccfbb3(a)msnews.microsoft.com... Hello >> Russell, >> >> If i check the files you have connected two different networks ,CSS >> and hilldale in one ip network and use the hilldale DHCP for the other >> domain? Is this correc? >> >> Best regards >> >> Meinolf Weber >> Disclaimer: This posting is provided "AS IS" with no warranties, and >> confers >> no rights. >> ** Please do NOT email, only reply to Newsgroups >> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm >>> dcdiags. >>> >>> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message >>> news:ff16fb66a10928ca9b8770d82565(a)msnews.microsoft.com... >>> >>>> Hello Russell, >>>> >>>> Please post the output from netdiag /v and dcdiag /v. Additional >>>> post an unedited ipconfig /all from both servers and the client >>>> machine. >>>> >>>> Best regards >>>> >>>> Meinolf Weber >>>> Disclaimer: This posting is provided "AS IS" with no warranties, and >>>> confers >>>> no rights. >>>> ** Please do NOT email, only reply to Newsgroups >>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm >>>>> Below is the error message when attempting to join domain. It >>>>> finds the DC. nslookup can resolve the DC both forward and >>>>> backward, so it seems that the A record for DC must be right. >>>>> >>>>> Now, here is the odd situation. This W2000 DC (Domain1) is using >>>>> another server W2003 DC (Domain2) for it's DNS and the LAN's DHCP >>>>> services. (I think this was done so the LAN would have a single >>>>> DHCP server.) >>>>> >>>>> I would even be willing to move the W2000 DNS services to reside on >>>>> the Domain1 DC if that would solve problem. I'm not sure how to >>>>> get all the DNS records set up for Active Directory if not done as >>>>> part of the original dcpromo. >>>>> >>>>> Any further advice appreciated. Russell >>>>> >>>>> ----- >>>>> DNS was successfully queried for the service location (SRV) >>>>> resource >>>>> record >>>>> used to locate a domain controller for domain ccs: >>>>> The query was for the SRV record for _ldap._tcp.dc._msdcs.ccs >>>>> The following domain controllers were identified by the query: >>>>> ccsserver.ccs >>>>> 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. >>>>> For information about correcting this problem, click Help. >>>>> Search the Web: >>>>> domain name >>>>> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message >>>>> news:ff16fb66a0eab8ca9ab647b6ec2e(a)msnews.microsoft.com... >>>>>> Hello Russell, >>>>>> >>>>>> What is the error message during the join process? >>>>>> Also you mix a bit 2 different items, client join problem and DC >>>>>> diagnostic/troubleshooting >>>>>> tools. So if you think there are domain problems run dcdiag, >>>>>> netdiag >>>>>> and >>>>>> repadmin /showreps and post the complete output here. For the >>>>>> clients >>>>>> check >>>>>> that they have the correct ip settings, subnet mask and only >>>>>> domain >>>>>> internal >>>>>> DNS server. Make sure that no firewall is enabled. >>>>>> Best regards >>>>>> Meinolf Weber >>>>>> Disclaimer: This posting is provided "AS IS" with no warranties, >>>>>> and >>>>>> confers >>>>>> no rights. >>>>>> ** Please do NOT email, only reply to Newsgroups >>>>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm >>>>>>> I have previously been successful joining WinXP PC to this >>>>>>> Win2000 domain. Have 2 new PCs with WinXP SP3 that will not join >>>>>>> the domain. dcdiag.txt output is show below. nslookup resolves >>>>>>> the server name fine. I do not have reverse DNS zone configured. >>>>>>> (never needed that in past for joining PC to this domain). I'm >>>>>>> stumped. Any suggestions appreciated. Russell >>>>>>> >>>>>>> ------dcdiag.txt ___ >>>>>>> The domain name ccs 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 ccs: >>>>>>> The query was for the SRV record for _ldap._tcp.dc._msdcs.ccs The >>>>>>> following domain controllers were identified by the query: >>>>>>> ccsserver.ccs >>>>>>> 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. >>>>>>> For information about correcting this problem, click Help. >>>>>>> ----- > >
From: Meinolf Weber on 26 Jun 2008 11:59 Hello Russell, Please post the scope options you are using. Not only the scope itself. Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights. ** Please do NOT email, only reply to Newsgroups ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm > Yes, a seperate DNS zone for each windows domain. > > dhcp scope properties: > start ip 192.168.2.33 > end ip 192.168.2.149 > Lease duration: 180 days > DNS tab-Checked: Enable DNS dynamic update according to the settings > below > Selected: Always dynamicaly update DNS A and PTR records > Checked: Dynamically update DNS A and PTR records for DHCP clients > that do > not request updates. > Advanced tab: DHCP only. > Any thoughts appreciated. Russell > > "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message > news:ff16fb66a20268caa507f17ee734(a)msnews.microsoft.com... > >> Hello Russell, >> >> So the DNS server hosts 2 different zones for both domains? Please >> post >> the >> DHCP scope settings. >> Best regards >> >> Meinolf Weber >> Disclaimer: This posting is provided "AS IS" with no warranties, and >> confers >> no rights. >> ** Please do NOT email, only reply to Newsgroups >> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm >>> Yes, a single LAN that has 2 unrelated Domains, CCS (w2000)and >>> HILLDALE.LOCAL (w2003). Each domain has its own individual DC. >>> The DC serving HILLDALE.LOCAL is also providing DHCP and DNS >>> services for the entire LAN including the CCS domain member PCs. I >>> sent you the diagnostic logs from both DCs and couple of client PCs. >>> >>> I even attempted to simplify the situation by removing the w2003 >>> from the equation by pointing a client PC's DNS to the the w2000 DC. >>> That did not work either, but I suspect because I don't have the DNS >>> services on the W2000 configured exactly right. >>> >>> I'm willing to try almost anything to get this resolved, so I >>> appreciate any thoughts you can offer. thanks, Russell >>> >>> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message >>> news:ff16fb66a1f438caa479f0ccfbb3(a)msnews.microsoft.com... Hello >>> Russell, >>> >>> If i check the files you have connected two different networks ,CSS >>> and hilldale in one ip network and use the hilldale DHCP for the >>> other domain? Is this correc? >>> >>> Best regards >>> >>> Meinolf Weber >>> Disclaimer: This posting is provided "AS IS" with no warranties, and >>> confers >>> no rights. >>> ** Please do NOT email, only reply to Newsgroups >>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm >>>> dcdiags. >>>> >>>> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message >>>> news:ff16fb66a10928ca9b8770d82565(a)msnews.microsoft.com... >>>> >>>>> Hello Russell, >>>>> >>>>> Please post the output from netdiag /v and dcdiag /v. Additional >>>>> post an unedited ipconfig /all from both servers and the client >>>>> machine. >>>>> >>>>> Best regards >>>>> >>>>> Meinolf Weber >>>>> Disclaimer: This posting is provided "AS IS" with no warranties, >>>>> and >>>>> confers >>>>> no rights. >>>>> ** Please do NOT email, only reply to Newsgroups >>>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm >>>>>> Below is the error message when attempting to join domain. It >>>>>> finds the DC. nslookup can resolve the DC both forward and >>>>>> backward, so it seems that the A record for DC must be right. >>>>>> >>>>>> Now, here is the odd situation. This W2000 DC (Domain1) is using >>>>>> another server W2003 DC (Domain2) for it's DNS and the LAN's DHCP >>>>>> services. (I think this was done so the LAN would have a single >>>>>> DHCP server.) >>>>>> >>>>>> I would even be willing to move the W2000 DNS services to reside >>>>>> on the Domain1 DC if that would solve problem. I'm not sure how >>>>>> to get all the DNS records set up for Active Directory if not >>>>>> done as part of the original dcpromo. >>>>>> >>>>>> Any further advice appreciated. Russell >>>>>> >>>>>> ----- >>>>>> DNS was successfully queried for the service location (SRV) >>>>>> resource >>>>>> record >>>>>> used to locate a domain controller for domain ccs: >>>>>> The query was for the SRV record for _ldap._tcp.dc._msdcs.ccs >>>>>> The following domain controllers were identified by the query: >>>>>> ccsserver.ccs >>>>>> 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. >>>>>> For information about correcting this problem, click Help. >>>>>> Search the Web: >>>>>> domain name >>>>>> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message >>>>>> news:ff16fb66a0eab8ca9ab647b6ec2e(a)msnews.microsoft.com... >>>>>>> Hello Russell, >>>>>>> >>>>>>> What is the error message during the join process? >>>>>>> Also you mix a bit 2 different items, client join problem and DC >>>>>>> diagnostic/troubleshooting >>>>>>> tools. So if you think there are domain problems run dcdiag, >>>>>>> netdiag >>>>>>> and >>>>>>> repadmin /showreps and post the complete output here. For the >>>>>>> clients >>>>>>> check >>>>>>> that they have the correct ip settings, subnet mask and only >>>>>>> domain >>>>>>> internal >>>>>>> DNS server. Make sure that no firewall is enabled. >>>>>>> Best regards >>>>>>> Meinolf Weber >>>>>>> Disclaimer: This posting is provided "AS IS" with no warranties, >>>>>>> and >>>>>>> confers >>>>>>> no rights. >>>>>>> ** Please do NOT email, only reply to Newsgroups >>>>>>> ** HELP us help YOU!!! >>>>>>> http://www.blakjak.demon.co.uk/mul_crss.htm >>>>>>>> I have previously been successful joining WinXP PC to this >>>>>>>> Win2000 domain. Have 2 new PCs with WinXP SP3 that will not >>>>>>>> join the domain. dcdiag.txt output is show below. nslookup >>>>>>>> resolves the server name fine. I do not have reverse DNS zone >>>>>>>> configured. (never needed that in past for joining PC to this >>>>>>>> domain). I'm stumped. Any suggestions appreciated. Russell >>>>>>>> >>>>>>>> ------dcdiag.txt ___ >>>>>>>> The domain name ccs 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 ccs: >>>>>>>> The query was for the SRV record for _ldap._tcp.dc._msdcs.ccs >>>>>>>> The >>>>>>>> following domain controllers were identified by the query: >>>>>>>> ccsserver.ccs >>>>>>>> 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. >>>>>>>> For information about correcting this problem, click Help. >>>>>>>> -----
First
|
Prev
|
Next
|
Last
Pages: 1 2 3 4 5 Prev: Account Operators Group Next: NetUserGetLocalGroups in multi-domain AD environment |