P
Paul Pearce
Hello
We just recently changed our domain name from abc.com to
def.com for our internal network.
We now have a number of PCs that are registering in DHCP
as MachineName.abc.com instead of with the new DNS suffix.
When I IPCONFIG one of the PCs, it shows the Primary DNS
suffix as abc.com and the DNS Suffix Search list as
abc.com first, then def.com next.
I've looked in all the expected places for supplying this
suffix value, but everything is set as should be.
The affected PCs are all running W2K, connecting thru a
Server 2003 Domain Controller, are identical PCs (we have
a real mix in this shop!) and may have been installed
using RIS. I'm not sure on this last part as I'm new here.
I did a quick search of the registry on one PC and found
one setting for abc.com in
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ADs\Providers\LDAP
\CN=Aggregate, CN=Schema, CN=Configuration, DC=abc,DC=com
The biggest problem to date I've had with these PCs is
they take forever to log on.
Any thoughts on this?
Confused in Canada
We just recently changed our domain name from abc.com to
def.com for our internal network.
We now have a number of PCs that are registering in DHCP
as MachineName.abc.com instead of with the new DNS suffix.
When I IPCONFIG one of the PCs, it shows the Primary DNS
suffix as abc.com and the DNS Suffix Search list as
abc.com first, then def.com next.
I've looked in all the expected places for supplying this
suffix value, but everything is set as should be.
The affected PCs are all running W2K, connecting thru a
Server 2003 Domain Controller, are identical PCs (we have
a real mix in this shop!) and may have been installed
using RIS. I'm not sure on this last part as I'm new here.
I did a quick search of the registry on one PC and found
one setting for abc.com in
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ADs\Providers\LDAP
\CN=Aggregate, CN=Schema, CN=Configuration, DC=abc,DC=com
The biggest problem to date I've had with these PCs is
they take forever to log on.
Any thoughts on this?
Confused in Canada