Win2k AD/DNS Problems

  • Thread starter Thread starter Jim Easley
  • Start date Start date
J

Jim Easley

Ok bear with me this might be confusing (it's been confusing me for
weeks now).

Recently I've been working on a small Win2k domain with 1 DC
(Poweredge 2600) and 1 Exchange server (poweredge 500). The Exchange
previously was both exchange and the DC. Client buys a new server to
replace the existing on. The "admin" in charge of this ran Ghost on
the 500, imaged the box, then loaded that image on the new server.

I don't know what the person did next, but the network name of the
machine was changed so I am assume he ran dcpromo and rebuilt the
domain.

What I think the major problem is: He used a registered domain name
as the AD domain name.

Does this cause major DNS slowness at the client level?

What kind of problems does this cause in active directory?


I have statically configured DNS and WINS on all client PC's to try
and help with network logins and such but it's barely noticeable.

They are also having Outlook 97 issues where a login box will randomly
appear, yet everything answer I've found either on here or on
Microsoft I have applied to the client and I can't get that problem to
go away.

I recently rebuilt their exchange server completely from scratch and
migrated all their mail over, so atleast they have a solidly
functioning email server now (aside from the Outlook clients).

I am dreading having to rebuild the DC completely but is that the best
way to go to fix this mess? Won't that screw up Exchange and almost
require that to be rebuilt as well?

Sorry for the confusing post and all the questions, I've been racking
my brain for 2 weeks over this and just when I think I get things
stable, the cell phone rings at dinner.

Thanks in advance for any help.
 
In
Jim Easley said:
Ok bear with me this might be confusing (it's been confusing me for
weeks now).

Recently I've been working on a small Win2k domain with 1 DC
(Poweredge 2600) and 1 Exchange server (poweredge 500). The Exchange
previously was both exchange and the DC. Client buys a new server to
replace the existing on. The "admin" in charge of this ran Ghost on
the 500, imaged the box, then loaded that image on the new server.

I don't know what the person did next, but the network name of the
machine was changed so I am assume he ran dcpromo and rebuilt the
domain.

What I think the major problem is: He used a registered domain name
as the AD domain name.

Does this cause major DNS slowness at the client level?
Click to expand...

It should not, as long as you only point the clients to the internal DNS
server.
What kind of problems does this cause in active directory?
Click to expand...

None, so long as you are using your internal DNS server's IP in TCP/IP
properties of all domain members.
I have statically configured DNS and WINS on all client PC's to try
and help with network logins and such but it's barely noticeable.
Click to expand...

If the clients are loging in slow it is probably because they are using an
external DNS server.
They are also having Outlook 97 issues where a login box will randomly
appear, yet everything answer I've found either on here or on
Microsoft I have applied to the client and I can't get that problem to
go away.

I recently rebuilt their exchange server completely from scratch and
migrated all their mail over, so atleast they have a solidly
functioning email server now (aside from the Outlook clients).

I am dreading having to rebuild the DC completely but is that the best
way to go to fix this mess? Won't that screw up Exchange and almost
require that to be rebuilt as well?

Sorry for the confusing post and all the questions, I've been racking
my brain for 2 weeks over this and just when I think I get things
stable, the cell phone rings at dinner.

Thanks in advance for any help.
Click to expand...

If you will post your ipconfig /all and the domain name from ADU&C I can
give you a very good idea of what to do.

We can clean this up, but since this has the same DNS name as a public
domian you may have trouble accessing sites and services in that public
domain. Hopefully it is your public domain, so it will be easier to get
information on any records you need to create to gain access those sites.
 
Back
Top