BDC/PDC Problems after Subnet change

We are in the middle of a migration from Exchange 5.5/NT4 to Exchange
2003/Win2K3. We have already installed a new NT4 BDC, promoted that to PDC,
and then upgraded it to Win2K3. Had a few hiccups, but all was running OK
after a week or so. Then had a requirement to change our internal LAN subnet
because of a conflict with the subnet of one of our clients, to which we
needed to establish VPN connectivity (we went from a 10.7.32.0/24 range to
172.25.32.0/24). I changed our LAN subnet, changed DNS, DHCP, and then fixed
addresses for all of our servers and routers. Started with the Win2K3 DC
first, and finished with the NT4 BDC last. All seemed OK, but today had some
problems with users not able to connect to resources (printers, shares) on
the NT4 BDC. When I look at Server Manager on the NT4 machine, it says that
it cannot connect to the Primary DC. The Win2K3 DC is now listed as a BDC
(was listed as PDC before). If I try to "promote" Win2K3 DC to PDC from NT4
Server Manager, it tells me that the
server name is an invalid path.

I believe that our connectivity problems are related to the BDC not being
able to connect properly to the Active Directory DC. Any ideas on how to
correct this? I have run dcdiag on the Win2K3 server. Cannot run dcdiag
against the NT4 BDC, I get the following:

[servername] LDAP search failed with error 58,
The specified server cannot perform the requested operation..
***Error: The machine, tecate could not be contacted, because of a bad net
response. Check to make sure that this machine is a Domain Controller.

Any ideas, anybody?

Yes attempt to open user manager for domains then
open a dos prompt and run nbtstat -c. Note the value
of the domain name 1b unique names for domains, it
should point towards your new W2k3 DC, if it doesn't.
Look at the TTL or time to live value. If it's -1 then
there is a static entry in your lmhosts file which must
be changed or removed. If you decide to change the
tcp/ip address then from a dos prompt run nbtstat -R
to purge and reload the cache. If the TTL is 600 or
less then the entry is most likely being pulled from a
WINS database. Open the WINS database and
sort by name then delete the offending 1b entry.


"Motek Kore Guy" <(E-Mail Removed)> wrote in message
news:46930051-8CD1-4371-B6E7-(E-Mail Removed)...
> We are in the middle of a migration from Exchange 5.5/NT4 to Exchange
> 2003/Win2K3. We have already installed a new NT4 BDC, promoted that to
> PDC,
> and then upgraded it to Win2K3. Had a few hiccups, but all was running OK
> after a week or so. Then had a requirement to change our internal LAN
> subnet
> because of a conflict with the subnet of one of our clients, to which we
> needed to establish VPN connectivity (we went from a 10.7.32.0/24 range to
> 172.25.32.0/24). I changed our LAN subnet, changed DNS, DHCP, and then
> fixed
> addresses for all of our servers and routers. Started with the Win2K3 DC
> first, and finished with the NT4 BDC last. All seemed OK, but today had
> some
> problems with users not able to connect to resources (printers, shares) on
> the NT4 BDC. When I look at Server Manager on the NT4 machine, it says
> that
> it cannot connect to the Primary DC. The Win2K3 DC is now listed as a BDC
> (was listed as PDC before). If I try to "promote" Win2K3 DC to PDC from
> NT4
> Server Manager, it tells me that the
> server name is an invalid path.
>
> I believe that our connectivity problems are related to the BDC not being
> able to connect properly to the Active Directory DC. Any ideas on how to
> correct this? I have run dcdiag on the Win2K3 server. Cannot run dcdiag
> against the NT4 BDC, I get the following:
>
> [servername] LDAP search failed with error 58,
> The specified server cannot perform the requested operation..
> ***Error: The machine, tecate could not be contacted, because of a bad
> net
> response. Check to make sure that this machine is a Domain Controller.
>
> Any ideas, anybody?
>