J
jim.mackillop
Hi, I'm trying to replace our company's existing windows 2000 domain
controller with a windows 2003 machine. Our existing server is outdated
so we've purchased a new machine with better hardware that already has
windows 2003 standard installed on it.
I understand that I can't just add the 2003 machine to the 2000 domain
without running the adprep utility to upgrade the active directory.
When running the dcdiag and netdiag commands (on the win2000 server),
all tests complete successfully but I get warnings about the DNS
entries for this server are not registered correctly in the DNS server
'ip address' which leads me to believe that something is not setup
properly. I have some basic knowledge of what should be in place but
not much after that.
Looking at the win2k server it's setup on a fixed IP address, and the
default gateway is set to our firewall/router. I show 3 DNS server
addresses, the first being the fixed local/private IP address of the
win2k server, and the second and third addresses are the provided
addresses from our ISP. I've checked all workstations and they are all
set to "obtain an IP address automatically" and "obtain DNS server
address automatically".
Something else that i'm not sure about is our domain namespace. We are
using office.companyname.com as the local domain for our office but the
parent domain (companyname.com) points to the address of the machine
that hosts our website (which belongs to our web-hosting company) and
is not listed on our domain controller as a DNS server address (I don't
think that it should be but I could be wrong).
So I'm able to get the dcdiag and netdiag tests to pass with no errors
but I do get some warnings which I would like to get resolved before I
go any further.
First of all, does our existing domain appear to be setup correctly (or
mostly correct)?
Second, since we only have about 6 workstations, would it be easier to
just setup a new network environment using the new win2003 server?
Thanks,
Jim
controller with a windows 2003 machine. Our existing server is outdated
so we've purchased a new machine with better hardware that already has
windows 2003 standard installed on it.
I understand that I can't just add the 2003 machine to the 2000 domain
without running the adprep utility to upgrade the active directory.
When running the dcdiag and netdiag commands (on the win2000 server),
all tests complete successfully but I get warnings about the DNS
entries for this server are not registered correctly in the DNS server
'ip address' which leads me to believe that something is not setup
properly. I have some basic knowledge of what should be in place but
not much after that.
Looking at the win2k server it's setup on a fixed IP address, and the
default gateway is set to our firewall/router. I show 3 DNS server
addresses, the first being the fixed local/private IP address of the
win2k server, and the second and third addresses are the provided
addresses from our ISP. I've checked all workstations and they are all
set to "obtain an IP address automatically" and "obtain DNS server
address automatically".
Something else that i'm not sure about is our domain namespace. We are
using office.companyname.com as the local domain for our office but the
parent domain (companyname.com) points to the address of the machine
that hosts our website (which belongs to our web-hosting company) and
is not listed on our domain controller as a DNS server address (I don't
think that it should be but I could be wrong).
So I'm able to get the dcdiag and netdiag tests to pass with no errors
but I do get some warnings which I would like to get resolved before I
go any further.
First of all, does our existing domain appear to be setup correctly (or
mostly correct)?
Second, since we only have about 6 workstations, would it be easier to
just setup a new network environment using the new win2003 server?
Thanks,
Jim