T
thorn_gabriel
I REALLY need some help on this one:
I will try to condense this as much as I can.
2 DC's-
One running Windows 2000 Server w/SP4- Has been the DC for 3 years as
well as running DHCP, DNS & WINS.
The other just recently brought up as a new DC running W2003 w/SP1
This last Friday we shut down DHCP on the old DC and installed DHCP on
the new server. We are trying to get everything off of the older DC
and eventually demote.
So we set up a brand new scope on the new server, becuase we are adding
to our current scope (we were running out of addresses) Our old range
was
10.0.0.90- 10.0.0.254
255.255.255.0
10.0.0.1
Was pointed to the old DC's IP for DNS and WINS
We made the new scope
10.0.0.200 - 10.0.3.254
255.255.252.0
10.0.0.1
Now points ot the new DC's DNS and WINS
So Monday morning everyone picked up new leases. I got a call that a
user could not print to a shared printer attached directly to another
users pc. Went through all of the usual steps to get this fixed, but
nothing worked. I could ping from a command prompt by name or IP just
fine. But if I click Start-Run and type in a workstation name, a
message comes back saying it could not be found. After that I saw both
workstations had IP's in the new range (10.0.1.x)
I went back to my desk, and saw I had an older adrress in the 10.0.0.x
range. I can access both machines just fine?!?!
First problem I noticed was that DNS was not updating any of the
records with the any clients running in the new range of 10.0.1.x. I
went in and manually deleted a couple of the old records pointing to a
now exlcuded IP and then the records were recreated. So I manually
deleted all old DNS records and then DNS looked ok with the new
records.
So where should I be looking to fix this issue? DNS was my first
thought, but maybe I am not looking in the right place?
I know this is alot to digest, but we are completely out of ideas.
Please help us, we are sinking fast!!!!!
I will try to condense this as much as I can.
2 DC's-
One running Windows 2000 Server w/SP4- Has been the DC for 3 years as
well as running DHCP, DNS & WINS.
The other just recently brought up as a new DC running W2003 w/SP1
This last Friday we shut down DHCP on the old DC and installed DHCP on
the new server. We are trying to get everything off of the older DC
and eventually demote.
So we set up a brand new scope on the new server, becuase we are adding
to our current scope (we were running out of addresses) Our old range
was
10.0.0.90- 10.0.0.254
255.255.255.0
10.0.0.1
Was pointed to the old DC's IP for DNS and WINS
We made the new scope
10.0.0.200 - 10.0.3.254
255.255.252.0
10.0.0.1
Now points ot the new DC's DNS and WINS
So Monday morning everyone picked up new leases. I got a call that a
user could not print to a shared printer attached directly to another
users pc. Went through all of the usual steps to get this fixed, but
nothing worked. I could ping from a command prompt by name or IP just
fine. But if I click Start-Run and type in a workstation name, a
message comes back saying it could not be found. After that I saw both
workstations had IP's in the new range (10.0.1.x)
I went back to my desk, and saw I had an older adrress in the 10.0.0.x
range. I can access both machines just fine?!?!
First problem I noticed was that DNS was not updating any of the
records with the any clients running in the new range of 10.0.1.x. I
went in and manually deleted a couple of the old records pointing to a
now exlcuded IP and then the records were recreated. So I manually
deleted all old DNS records and then DNS looked ok with the new
records.
So where should I be looking to fix this issue? DNS was my first
thought, but maybe I am not looking in the right place?
I know this is alot to digest, but we are completely out of ideas.
Please help us, we are sinking fast!!!!!