|
Horror Story: I did 5 months
of research and Before you do
the upgrade, check the DNS tab of TCPIP properties, and see if you have a
domain name in there. If you do, use that name for your W2K Domain, or change
what is in there to the domain name you want to use for your W2K Domain. I had inherited
that network from a previous admin. When they set it up, they entered our
External DNS name in there. I didn’t check it, and used a different
domain name during dcpromo. What I ended up with was the following for computer
and network name COMPUTER NAME Computer.domain_a.co.uk DOMAIN NAME netbios_domain.domain_a.co.uk What I would
have, and wanted to have ended up with, if I had changed the DNS entry in TCPIP
props, was COMPUTER NAME Computer.netbios_domain.domain_a.co.uk DOMAIN NAME netbios_domain.domain_a.co.uk You’ll
notice that the machines FQDN in the top example is different from the FQDN for
the W2K domain. When that happens, just try adding anything to the domain. “Cannot
find a domain controller” is what you will get. Hope that helps J
T: +5 999 736 0309 ext
4537 -----Original Message----- Have a server or two to migrate to
Windows 2000, anybody with horror stories they want to share. Any useful
resources that should be reviewed prior to taking the digital plunge. Thanks in advance --------------------------------------------- Richard Jones http://www.sunbelt-software.com/ntsysadmin_list_charter.htm |
- Windows NT4 sp6a servers running SQL version 7 sp 2 Richard Jones
- Re: Windows NT4 sp6a servers running SQL version 7... Clayton
- Re: Windows NT4 sp6a servers running SQL version 7... The Realist's Mail
