S
Shandy
I need a configuration workaround or advice on how to correct the network
setup.
Current config:
xp & win2k clients (~20 in total)
win2000 server running Active Directory as PDC.
Active directory has been created for acme.com. And all clients are
connected to acme.com domain. The problem is that the dns servers for
acme.com are controlled by our isp. PDC is also running dns with forwarding.
DHCP is configured on the network router to give out the PDC's IP as the DNS
server address. Clients also have the router set up as the default gateway
IP address.
I get DNS registration errors when clients log on. And more importantly the
acme.com (ACME) domain isn't listed in the locations dialog when trying to
add network users to local policy groups.
How should I fix it?
My thoughts are uninstall the the active directory and create a new one
called dev.acme.com. I presume I can then set up dns with a forward lookup
zone to resolve external domains. But then I'd have to remove all clients
from the acme.com domain and then join the dev.acme.com domain losing lots
of user information. (Unless I use the XP user transfer utilty). Am I right
in thinking this? Also what are the long term implication when we plan to
have our mail server internally rather than at the ISP. Will there be a
problem configuring exchange so that (e-mail address removed) gets delivered to
(e-mail address removed)? Simliarly when we set up an ftp server which we would want
to be ftp.acme.com. Also can the domain shortname still be ACME?
Alternatively change from a dynamic IP to a static IP then move dns control
to our PDC. Would need to make sure www and mail traffic is still directed
to our ISP hosting. Is ther an alternative to this?. Athough I'm not sure
if this would solve my dns registration and domain browsing problems.
There is a spare server available that could be used if the server has to be
reconfigured. Would it be useful to set up a BDC and replicate the
existiing active directory promote it to a PDC then reconfigure the original
server and migrate clients and users from one to the other finally removing
the temporary server. Any thoughts on this?
Any advice much appreciated.
Neil
setup.
Current config:
xp & win2k clients (~20 in total)
win2000 server running Active Directory as PDC.
Active directory has been created for acme.com. And all clients are
connected to acme.com domain. The problem is that the dns servers for
acme.com are controlled by our isp. PDC is also running dns with forwarding.
DHCP is configured on the network router to give out the PDC's IP as the DNS
server address. Clients also have the router set up as the default gateway
IP address.
I get DNS registration errors when clients log on. And more importantly the
acme.com (ACME) domain isn't listed in the locations dialog when trying to
add network users to local policy groups.
How should I fix it?
My thoughts are uninstall the the active directory and create a new one
called dev.acme.com. I presume I can then set up dns with a forward lookup
zone to resolve external domains. But then I'd have to remove all clients
from the acme.com domain and then join the dev.acme.com domain losing lots
of user information. (Unless I use the XP user transfer utilty). Am I right
in thinking this? Also what are the long term implication when we plan to
have our mail server internally rather than at the ISP. Will there be a
problem configuring exchange so that (e-mail address removed) gets delivered to
(e-mail address removed)? Simliarly when we set up an ftp server which we would want
to be ftp.acme.com. Also can the domain shortname still be ACME?
Alternatively change from a dynamic IP to a static IP then move dns control
to our PDC. Would need to make sure www and mail traffic is still directed
to our ISP hosting. Is ther an alternative to this?. Athough I'm not sure
if this would solve my dns registration and domain browsing problems.
There is a spare server available that could be used if the server has to be
reconfigured. Would it be useful to set up a BDC and replicate the
existiing active directory promote it to a PDC then reconfigure the original
server and migrate clients and users from one to the other finally removing
the temporary server. Any thoughts on this?
Any advice much appreciated.
Neil