Guest Drew Govnyak Posted April 10, 2008 Posted April 10, 2008 I inherited a windows 2000 (native mode) network with FQDN set to companyname.local.com. According to the KB292541, I can rename it to companyname.local, but it's time consuming and not recommended. Can someone point out the problems I may run in to if FQDN is kept unchanged.
Guest Danny Sanders Posted April 10, 2008 Posted April 10, 2008 Re: change FQDN on Windows 2000 Server Actually you can't rename a native mode Win 2k domain. From section 1 of the KB article you cited: You have to keep the Windows 2000 domain in Mixed mode. After you change it to Native mode, you cannot return the domain to Mixed mode, thereby rendering renaming impossible. I'm not sure you will run into problems as your domain is now. You run into problems with a single label domain name like mydomain instead of mydomain.com. I would leave as is and re-evaluate the name when/if you move to Win 2k3. hth DDS "Drew Govnyak" <no-email-here@none.com> wrote in message news:Or9duF0mIHA.4292@TK2MSFTNGP04.phx.gbl... >I inherited a windows 2000 (native mode) network with FQDN set to >companyname.local.com. According to the KB292541, I can rename it to >companyname.local, but it's time consuming and not recommended. Can someone >point out the problems I may run in to if FQDN is kept unchanged. > > > >
Guest Drew Govnyak Posted April 10, 2008 Posted April 10, 2008 Re: change FQDN on Windows 2000 Server Funny that you brought this up, because I also have a customer who's domain name is 'compnayname.' Also running in the native 2000 mode. What problems should I see in that environment? "Danny Sanders" <DSanders@NOSPAMciber.com> wrote in message news:unzrKL0mIHA.3512@TK2MSFTNGP03.phx.gbl... > Actually you can't rename a native mode Win 2k domain. > > From section 1 of the KB article you cited: > You have to keep the Windows 2000 domain in Mixed mode. After you > change it to Native mode, you cannot return the domain to Mixed mode, > thereby rendering renaming impossible. > > I'm not sure you will run into problems as your domain is now. You > run into problems with a single label domain name like mydomain instead of > mydomain.com. > > I would leave as is and re-evaluate the name when/if you move to Win > 2k3. > > hth > DDS > > > > "Drew Govnyak" <no-email-here@none.com> wrote in message > news:Or9duF0mIHA.4292@TK2MSFTNGP04.phx.gbl... >>I inherited a windows 2000 (native mode) network with FQDN set to >>companyname.local.com. According to the KB292541, I can rename it to >>companyname.local, but it's time consuming and not recommended. Can >>someone point out the problems I may run in to if FQDN is kept unchanged. >> >> >> >> > >
Guest Danny Sanders Posted April 10, 2008 Posted April 10, 2008 Re: change FQDN on Windows 2000 Server See: http://support.microsoft.com/kb/300684/en-us hth DDS "Drew Govnyak" <no-email-here@none.com> wrote in message news:u2aN1O0mIHA.4740@TK2MSFTNGP02.phx.gbl... > Funny that you brought this up, because I also have a customer who's > domain name is 'compnayname.' Also running in the native 2000 mode. What > problems should I see in that environment? > > > > > > "Danny Sanders" <DSanders@NOSPAMciber.com> wrote in message > news:unzrKL0mIHA.3512@TK2MSFTNGP03.phx.gbl... >> Actually you can't rename a native mode Win 2k domain. >> >> From section 1 of the KB article you cited: >> You have to keep the Windows 2000 domain in Mixed mode. After you >> change it to Native mode, you cannot return the domain to Mixed mode, >> thereby rendering renaming impossible. >> >> I'm not sure you will run into problems as your domain is now. You >> run into problems with a single label domain name like mydomain instead >> of mydomain.com. >> >> I would leave as is and re-evaluate the name when/if you move to Win >> 2k3. >> >> hth >> DDS >> >> >> >> "Drew Govnyak" <no-email-here@none.com> wrote in message >> news:Or9duF0mIHA.4292@TK2MSFTNGP04.phx.gbl... >>>I inherited a windows 2000 (native mode) network with FQDN set to >>>companyname.local.com. According to the KB292541, I can rename it to >>>companyname.local, but it's time consuming and not recommended. Can >>>someone point out the problems I may run in to if FQDN is kept unchanged. >>> >>> >>> >>> >> >> > >
Recommended Posts