Guest Tom Posted July 9, 2008 Posted July 9, 2008 Hello, We recently installed a new Windows 2003 server; set it up as an additional domain controller; transferred the FSMO roles from our existing Windows 2000 DC server; demoted our old server and removed it from the network. We have approxiametly 200 clients that login to our network. 25% Vista Business and 75% XP Pro. Since the change over we are getting "The system cannot login because the domain (example) is not available.". We don't get the message on all of the clients, only on about 25 machines. I've disjoined and rejoined them to the domain with no problems. The Vista machines work with no problems, we've only seen the problem on XP. If I login locally and UNC map to the server, authenticate, logout, then try logging in to the domain, it works fine. We've had the problem on new clients and clients that have been on the domain for years. Any suggestions that you have would be greatly appreciated. Thanks, Tom
Guest Kyle Blake Posted July 9, 2008 Posted July 9, 2008 RE: Domain login errors Sounds like DNS ...maybe not being "AD" integrated? Very interesting the domain list not being populated. "Tom" wrote: > Hello, > We recently installed a new Windows 2003 server; set it up as an additional > domain controller; transferred the FSMO roles from our existing Windows 2000 > DC server; demoted our old server and removed it from the network. We have > approxiametly 200 clients that login to our network. 25% Vista Business and > 75% XP Pro. Since the change over we are getting "The system cannot login > because the domain (example) is not available.". We don't get the message on > all of the clients, only on about 25 machines. I've disjoined and rejoined > them to the domain with no problems. The Vista machines work with no > problems, we've only seen the problem on XP. If I login locally and UNC map > to the server, authenticate, logout, then try logging in to the domain, it > works fine. We've had the problem on new clients and clients that have been > on the domain for years. Any suggestions that you have would be greatly > appreciated. > Thanks, > Tom
Guest Meinolf Weber Posted July 9, 2008 Posted July 9, 2008 Re: Domain login errors Hello Tom, Is the new server also DNS and are all clients configured to use it as preferred DNS? Do you use AD integrated zones before adding the new server? Another question, do you also make the new server Global catalog before demoting the other one? 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 > Hello, > We recently installed a new Windows 2003 server; set it up as an > additional > domain controller; transferred the FSMO roles from our existing > Windows 2000 > DC server; demoted our old server and removed it from the network. We > have > approxiametly 200 clients that login to our network. 25% Vista > Business and > 75% XP Pro. Since the change over we are getting "The system cannot > login > because the domain (example) is not available.". We don't get the > message on > all of the clients, only on about 25 machines. I've disjoined and > rejoined > them to the domain with no problems. The Vista machines work with no > problems, we've only seen the problem on XP. If I login locally and > UNC map > to the server, authenticate, logout, then try logging in to the > domain, it > works fine. We've had the problem on new clients and clients that > have been > on the domain for years. Any suggestions that you have would be > greatly > appreciated. > Thanks, > Tom
Guest Tom Posted July 9, 2008 Posted July 9, 2008 Re: Domain login errors Actually, all of our DNS and IP addressing is controller through our State. We are a school. The clients are automatically set to point to the State DNS servers. I do have the DC pointing to itself for DNS. I'm not sure about the AD integrated zones or the Global catalog. I only transferred the FSMO roles and then demoted the old DC. Did I miss something? Thanks for the quick response. Tom "Meinolf Weber" wrote: > Hello Tom, > > Is the new server also DNS and are all clients configured to use it as preferred > DNS? Do you use AD integrated zones before adding the new server? Another > question, do you also make the new server Global catalog before demoting > the other one? > > 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 > > > Hello, > > We recently installed a new Windows 2003 server; set it up as an > > additional > > domain controller; transferred the FSMO roles from our existing > > Windows 2000 > > DC server; demoted our old server and removed it from the network. We > > have > > approxiametly 200 clients that login to our network. 25% Vista > > Business and > > 75% XP Pro. Since the change over we are getting "The system cannot > > login > > because the domain (example) is not available.". We don't get the > > message on > > all of the clients, only on about 25 machines. I've disjoined and > > rejoined > > them to the domain with no problems. The Vista machines work with no > > problems, we've only seen the problem on XP. If I login locally and > > UNC map > > to the server, authenticate, logout, then try logging in to the > > domain, it > > works fine. We've had the problem on new clients and clients that > > have been > > on the domain for years. Any suggestions that you have would be > > greatly > > appreciated. > > Thanks, > > Tom > > >
Guest Meinolf Weber Posted July 9, 2008 Posted July 9, 2008 Re: Domain login errors Hello Tom, So the new DC is also DNS server? Then open DNS management console, mark the server and in the right pane you see the kind of zone. So also all clients use that server as the DNS server on there NIC? To see if it is Global catalog: http://support.microsoft.com/?id=313994 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 > Actually, all of our DNS and IP addressing is controller through our > State. > We are a school. The clients are automatically set to point to the > State DNS > servers. I do have the DC pointing to itself for DNS. I'm not sure > about > the AD integrated zones or the Global catalog. I only transferred the > FSMO > roles and then demoted the old DC. Did I miss something? Thanks for > the > quick response. > Tom > "Meinolf Weber" wrote: > >> Hello Tom, >> >> Is the new server also DNS and are all clients configured to use it >> as preferred DNS? Do you use AD integrated zones before adding the >> new server? Another question, do you also make the new server Global >> catalog before demoting the other one? >> >> 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 >>> Hello, >>> We recently installed a new Windows 2003 server; set it up as an >>> additional >>> domain controller; transferred the FSMO roles from our existing >>> Windows 2000 >>> DC server; demoted our old server and removed it from the network. >>> We >>> have >>> approxiametly 200 clients that login to our network. 25% Vista >>> Business and >>> 75% XP Pro. Since the change over we are getting "The system cannot >>> login >>> because the domain (example) is not available.". We don't get the >>> message on >>> all of the clients, only on about 25 machines. I've disjoined and >>> rejoined >>> them to the domain with no problems. The Vista machines work with >>> no >>> problems, we've only seen the problem on XP. If I login locally and >>> UNC map >>> to the server, authenticate, logout, then try logging in to the >>> domain, it >>> works fine. We've had the problem on new clients and clients that >>> have been >>> on the domain for years. Any suggestions that you have would be >>> greatly >>> appreciated. >>> Thanks, >>> Tom
Guest Tom Posted July 9, 2008 Posted July 9, 2008 Re: Domain login errors Yes, the DNS service is running. However, the DNS is automatically assigned by our State so I'm not sure if that's part of the problem or not. The zone listed in the DNS manager is our domain name: example.com. I was told by the State that the clients must point to their DNS servers. The server is the Global Catalog server. Will it help to remove the check mark, restart, and have it replicate again? Thanks for the quick response. Tom "Meinolf Weber" wrote: > Hello Tom, > > So the new DC is also DNS server? Then open DNS management console, mark > the server and in the right pane you see the kind of zone. So also all clients > use that server as the DNS server on there NIC? > > To see if it is Global catalog: > http://support.microsoft.com/?id=313994 > > 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 > > > Actually, all of our DNS and IP addressing is controller through our > > State. > > We are a school. The clients are automatically set to point to the > > State DNS > > servers. I do have the DC pointing to itself for DNS. I'm not sure > > about > > the AD integrated zones or the Global catalog. I only transferred the > > FSMO > > roles and then demoted the old DC. Did I miss something? Thanks for > > the > > quick response. > > Tom > > "Meinolf Weber" wrote: > > > >> Hello Tom, > >> > >> Is the new server also DNS and are all clients configured to use it > >> as preferred DNS? Do you use AD integrated zones before adding the > >> new server? Another question, do you also make the new server Global > >> catalog before demoting the other one? > >> > >> 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 > >>> Hello, > >>> We recently installed a new Windows 2003 server; set it up as an > >>> additional > >>> domain controller; transferred the FSMO roles from our existing > >>> Windows 2000 > >>> DC server; demoted our old server and removed it from the network. > >>> We > >>> have > >>> approxiametly 200 clients that login to our network. 25% Vista > >>> Business and > >>> 75% XP Pro. Since the change over we are getting "The system cannot > >>> login > >>> because the domain (example) is not available.". We don't get the > >>> message on > >>> all of the clients, only on about 25 machines. I've disjoined and > >>> rejoined > >>> them to the domain with no problems. The Vista machines work with > >>> no > >>> problems, we've only seen the problem on XP. If I login locally and > >>> UNC map > >>> to the server, authenticate, logout, then try logging in to the > >>> domain, it > >>> works fine. We've had the problem on new clients and clients that > >>> have been > >>> on the domain for years. Any suggestions that you have would be > >>> greatly > >>> appreciated. > >>> Thanks, > >>> Tom > > >
Guest Meinolf Weber Posted July 9, 2008 Posted July 9, 2008 Re: Domain login errors Hello Tom, Global catalog has nothing to do with DNS configuration, let it like it is. Please post an unedited ipconfig /all from the new server and one problem client. 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, the DNS service is running. However, the DNS is automatically > assigned > by our State so I'm not sure if that's part of the problem or not. > The zone > listed in the DNS manager is our domain name: example.com. I was > told by > the State that the clients must point to their DNS servers. The > server is > the Global Catalog server. Will it help to remove the check mark, > restart, > and have it replicate again? > Thanks for the quick response. > Tom > "Meinolf Weber" wrote: > >> Hello Tom, >> >> So the new DC is also DNS server? Then open DNS management console, >> mark the server and in the right pane you see the kind of zone. So >> also all clients use that server as the DNS server on there NIC? >> >> To see if it is Global catalog: >> http://support.microsoft.com/?id=313994 >> 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 >>> Actually, all of our DNS and IP addressing is controller through our >>> State. >>> We are a school. The clients are automatically set to point to the >>> State DNS >>> servers. I do have the DC pointing to itself for DNS. I'm not sure >>> about >>> the AD integrated zones or the Global catalog. I only transferred >>> the >>> FSMO >>> roles and then demoted the old DC. Did I miss something? Thanks >>> for >>> the >>> quick response. >>> Tom >>> "Meinolf Weber" wrote: >>>> Hello Tom, >>>> >>>> Is the new server also DNS and are all clients configured to use it >>>> as preferred DNS? Do you use AD integrated zones before adding the >>>> new server? Another question, do you also make the new server >>>> Global catalog before demoting the other one? >>>> >>>> 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 >>>>> Hello, >>>>> We recently installed a new Windows 2003 server; set it up as an >>>>> additional >>>>> domain controller; transferred the FSMO roles from our existing >>>>> Windows 2000 >>>>> DC server; demoted our old server and removed it from the network. >>>>> We >>>>> have >>>>> approxiametly 200 clients that login to our network. 25% Vista >>>>> Business and >>>>> 75% XP Pro. Since the change over we are getting "The system >>>>> cannot >>>>> login >>>>> because the domain (example) is not available.". We don't get the >>>>> message on >>>>> all of the clients, only on about 25 machines. I've disjoined and >>>>> rejoined >>>>> them to the domain with no problems. The Vista machines work with >>>>> no >>>>> problems, we've only seen the problem on XP. If I login locally >>>>> and >>>>> UNC map >>>>> to the server, authenticate, logout, then try logging in to the >>>>> domain, it >>>>> works fine. We've had the problem on new clients and clients that >>>>> have been >>>>> on the domain for years. Any suggestions that you have would be >>>>> greatly >>>>> appreciated. >>>>> Thanks, >>>>> Tom
Guest Tom Posted July 9, 2008 Posted July 9, 2008 Re: Domain login errors The server ipconfig: 10.130.2.49 255.255.254.0 10.130.2.1 10.130.2.49 A client ipconfig: 10.130.2.99 255.255.254.0 10.130.2.1 165.234.71.10 10.57.1.10 All of the client machines have the same DNS information, whether they are having problems or not. The State told me that we must use those DNS servers. I don't understand why it's a random problem. Most of the clients work just fine. Thanks. "Meinolf Weber" wrote: > Hello Tom, > > Global catalog has nothing to do with DNS configuration, let it like it is. > Please post an unedited ipconfig /all from the new server and one problem > client. > > 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, the DNS service is running. However, the DNS is automatically > > assigned > > by our State so I'm not sure if that's part of the problem or not. > > The zone > > listed in the DNS manager is our domain name: example.com. I was > > told by > > the State that the clients must point to their DNS servers. The > > server is > > the Global Catalog server. Will it help to remove the check mark, > > restart, > > and have it replicate again? > > Thanks for the quick response. > > Tom > > "Meinolf Weber" wrote: > > > >> Hello Tom, > >> > >> So the new DC is also DNS server? Then open DNS management console, > >> mark the server and in the right pane you see the kind of zone. So > >> also all clients use that server as the DNS server on there NIC? > >> > >> To see if it is Global catalog: > >> http://support.microsoft.com/?id=313994 > >> 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 > >>> Actually, all of our DNS and IP addressing is controller through our > >>> State. > >>> We are a school. The clients are automatically set to point to the > >>> State DNS > >>> servers. I do have the DC pointing to itself for DNS. I'm not sure > >>> about > >>> the AD integrated zones or the Global catalog. I only transferred > >>> the > >>> FSMO > >>> roles and then demoted the old DC. Did I miss something? Thanks > >>> for > >>> the > >>> quick response. > >>> Tom > >>> "Meinolf Weber" wrote: > >>>> Hello Tom, > >>>> > >>>> Is the new server also DNS and are all clients configured to use it > >>>> as preferred DNS? Do you use AD integrated zones before adding the > >>>> new server? Another question, do you also make the new server > >>>> Global catalog before demoting the other one? > >>>> > >>>> 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 > >>>>> Hello, > >>>>> We recently installed a new Windows 2003 server; set it up as an > >>>>> additional > >>>>> domain controller; transferred the FSMO roles from our existing > >>>>> Windows 2000 > >>>>> DC server; demoted our old server and removed it from the network. > >>>>> We > >>>>> have > >>>>> approxiametly 200 clients that login to our network. 25% Vista > >>>>> Business and > >>>>> 75% XP Pro. Since the change over we are getting "The system > >>>>> cannot > >>>>> login > >>>>> because the domain (example) is not available.". We don't get the > >>>>> message on > >>>>> all of the clients, only on about 25 machines. I've disjoined and > >>>>> rejoined > >>>>> them to the domain with no problems. The Vista machines work with > >>>>> no > >>>>> problems, we've only seen the problem on XP. If I login locally > >>>>> and > >>>>> UNC map > >>>>> to the server, authenticate, logout, then try logging in to the > >>>>> domain, it > >>>>> works fine. We've had the problem on new clients and clients that > >>>>> have been > >>>>> on the domain for years. Any suggestions that you have would be > >>>>> greatly > >>>>> appreciated. > >>>>> Thanks, > >>>>> Tom > > >
Guest Meinolf Weber Posted July 9, 2008 Posted July 9, 2008 Re: Domain login errors Hello Tom, Server looks ok, but the client can not use the domain internal server from your domain, so they are not aible to find the domain correctly. 165.x.x.x seems to be a public DNS server which should only be used as a forwarder under the DNS management console under the server properties. The first one on the client should be your 10.130.2.49 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 > The server ipconfig: > 10.130.2.49 > 255.255.254.0 > 10.130.2.1 > 10.130.2.49 > A client ipconfig: > 10.130.2.99 > 255.255.254.0 > 10.130.2.1 > 165.234.71.10 > 10.57.1.10 > All of the client machines have the same DNS information, whether they > are > having problems or not. The State told me that we must use those DNS > servers. I don't understand why it's a random problem. Most of the > clients > work just fine. > Thanks. > "Meinolf Weber" wrote: > >> Hello Tom, >> >> Global catalog has nothing to do with DNS configuration, let it like >> it is. Please post an unedited ipconfig /all from the new server and >> one problem client. >> >> 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, the DNS service is running. However, the DNS is automatically >>> assigned >>> by our State so I'm not sure if that's part of the problem or not. >>> The zone >>> listed in the DNS manager is our domain name: example.com. I was >>> told by >>> the State that the clients must point to their DNS servers. The >>> server is >>> the Global Catalog server. Will it help to remove the check mark, >>> restart, >>> and have it replicate again? >>> Thanks for the quick response. >>> Tom >>> "Meinolf Weber" wrote: >>>> Hello Tom, >>>> >>>> So the new DC is also DNS server? Then open DNS management console, >>>> mark the server and in the right pane you see the kind of zone. So >>>> also all clients use that server as the DNS server on there NIC? >>>> >>>> To see if it is Global catalog: >>>> http://support.microsoft.com/?id=313994 >>>> 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 >>>>> Actually, all of our DNS and IP addressing is controller through >>>>> our >>>>> State. >>>>> We are a school. The clients are automatically set to point to >>>>> the >>>>> State DNS >>>>> servers. I do have the DC pointing to itself for DNS. I'm not >>>>> sure >>>>> about >>>>> the AD integrated zones or the Global catalog. I only transferred >>>>> the >>>>> FSMO >>>>> roles and then demoted the old DC. Did I miss something? Thanks >>>>> for >>>>> the >>>>> quick response. >>>>> Tom >>>>> "Meinolf Weber" wrote: >>>>>> Hello Tom, >>>>>> >>>>>> Is the new server also DNS and are all clients configured to use >>>>>> it as preferred DNS? Do you use AD integrated zones before adding >>>>>> the new server? Another question, do you also make the new server >>>>>> Global catalog before demoting the other one? >>>>>> >>>>>> 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 >>>>>>> Hello, >>>>>>> We recently installed a new Windows 2003 server; set it up as an >>>>>>> additional >>>>>>> domain controller; transferred the FSMO roles from our existing >>>>>>> Windows 2000 >>>>>>> DC server; demoted our old server and removed it from the >>>>>>> network. >>>>>>> We >>>>>>> have >>>>>>> approxiametly 200 clients that login to our network. 25% Vista >>>>>>> Business and >>>>>>> 75% XP Pro. Since the change over we are getting "The system >>>>>>> cannot >>>>>>> login >>>>>>> because the domain (example) is not available.". We don't get >>>>>>> the >>>>>>> message on >>>>>>> all of the clients, only on about 25 machines. I've disjoined >>>>>>> and >>>>>>> rejoined >>>>>>> them to the domain with no problems. The Vista machines work >>>>>>> with >>>>>>> no >>>>>>> problems, we've only seen the problem on XP. If I login locally >>>>>>> and >>>>>>> UNC map >>>>>>> to the server, authenticate, logout, then try logging in to the >>>>>>> domain, it >>>>>>> works fine. We've had the problem on new clients and clients >>>>>>> that >>>>>>> have been >>>>>>> on the domain for years. Any suggestions that you have would be >>>>>>> greatly >>>>>>> appreciated. >>>>>>> Thanks, >>>>>>> Tom
Guest Tom Posted July 10, 2008 Posted July 10, 2008 Re: Domain login errors Thanks again for the help. I'm going to manually set the dns to point to my server and see if the problem goes away. If it does then I contact the State and see if they will add my server as the primary dns. Thanks, Tom "Meinolf Weber" wrote: > Hello Tom, > > Server looks ok, but the client can not use the domain internal server from > your domain, so they are not aible to find the domain correctly. 165.x.x.x > seems to be a public DNS server which should only be used as a forwarder > under the DNS management console under the server properties. The first one > on the client should be your 10.130.2.49 > > 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 > > > The server ipconfig: > > 10.130.2.49 > > 255.255.254.0 > > 10.130.2.1 > > 10.130.2.49 > > A client ipconfig: > > 10.130.2.99 > > 255.255.254.0 > > 10.130.2.1 > > 165.234.71.10 > > 10.57.1.10 > > All of the client machines have the same DNS information, whether they > > are > > having problems or not. The State told me that we must use those DNS > > servers. I don't understand why it's a random problem. Most of the > > clients > > work just fine. > > Thanks. > > "Meinolf Weber" wrote: > > > >> Hello Tom, > >> > >> Global catalog has nothing to do with DNS configuration, let it like > >> it is. Please post an unedited ipconfig /all from the new server and > >> one problem client. > >> > >> 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, the DNS service is running. However, the DNS is automatically > >>> assigned > >>> by our State so I'm not sure if that's part of the problem or not. > >>> The zone > >>> listed in the DNS manager is our domain name: example.com. I was > >>> told by > >>> the State that the clients must point to their DNS servers. The > >>> server is > >>> the Global Catalog server. Will it help to remove the check mark, > >>> restart, > >>> and have it replicate again? > >>> Thanks for the quick response. > >>> Tom > >>> "Meinolf Weber" wrote: > >>>> Hello Tom, > >>>> > >>>> So the new DC is also DNS server? Then open DNS management console, > >>>> mark the server and in the right pane you see the kind of zone. So > >>>> also all clients use that server as the DNS server on there NIC? > >>>> > >>>> To see if it is Global catalog: > >>>> http://support.microsoft.com/?id=313994 > >>>> 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 > >>>>> Actually, all of our DNS and IP addressing is controller through > >>>>> our > >>>>> State. > >>>>> We are a school. The clients are automatically set to point to > >>>>> the > >>>>> State DNS > >>>>> servers. I do have the DC pointing to itself for DNS. I'm not > >>>>> sure > >>>>> about > >>>>> the AD integrated zones or the Global catalog. I only transferred > >>>>> the > >>>>> FSMO > >>>>> roles and then demoted the old DC. Did I miss something? Thanks > >>>>> for > >>>>> the > >>>>> quick response. > >>>>> Tom > >>>>> "Meinolf Weber" wrote: > >>>>>> Hello Tom, > >>>>>> > >>>>>> Is the new server also DNS and are all clients configured to use > >>>>>> it as preferred DNS? Do you use AD integrated zones before adding > >>>>>> the new server? Another question, do you also make the new server > >>>>>> Global catalog before demoting the other one? > >>>>>> > >>>>>> 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 > >>>>>>> Hello, > >>>>>>> We recently installed a new Windows 2003 server; set it up as an > >>>>>>> additional > >>>>>>> domain controller; transferred the FSMO roles from our existing > >>>>>>> Windows 2000 > >>>>>>> DC server; demoted our old server and removed it from the > >>>>>>> network. > >>>>>>> We > >>>>>>> have > >>>>>>> approxiametly 200 clients that login to our network. 25% Vista > >>>>>>> Business and > >>>>>>> 75% XP Pro. Since the change over we are getting "The system > >>>>>>> cannot > >>>>>>> login > >>>>>>> because the domain (example) is not available.". We don't get > >>>>>>> the > >>>>>>> message on > >>>>>>> all of the clients, only on about 25 machines. I've disjoined > >>>>>>> and > >>>>>>> rejoined > >>>>>>> them to the domain with no problems. The Vista machines work > >>>>>>> with > >>>>>>> no > >>>>>>> problems, we've only seen the problem on XP. If I login locally > >>>>>>> and > >>>>>>> UNC map > >>>>>>> to the server, authenticate, logout, then try logging in to the > >>>>>>> domain, it > >>>>>>> works fine. We've had the problem on new clients and clients > >>>>>>> that > >>>>>>> have been > >>>>>>> on the domain for years. Any suggestions that you have would be > >>>>>>> greatly > >>>>>>> appreciated. > >>>>>>> Thanks, > >>>>>>> Tom > > >
Recommended Posts