AD Install

[Cary Shultz [A.D. MVP]]

Essam,

It needs to be plugged into a hub or a switch. Just stick a Cat5 cable in
the NIC ( on the Server ) and the other end into a hub or switch. The hub
or switch does not have to be connected to anything, just turned on....

Now you can continue.

You can also use the MS Loopback Adapter if you do not have a hub or a
switch.

Cary

 

[Cary Shultz [A.D. MVP]]

Essam,

Then I might suggest that you either give that WIN2000 Server that you are
trying to dcpromo another name or that you look into why there is another
computer on the network with that particular name.

Did you ever have a Domain Controller that had the same name as the one that
you are trying to give to this one? That would probably indicate that
someone did not properly remove that Domain Controller from AD or that it
crashed and no one did a metadata cleanup. Should this be the case take a
look at the following MSKB Article to remove the former DC properly from AD
so that you can continue with the dcpromo of this one:

http://support.microsoft.com/?id=216498

If none of these is what happened then maybe you can explain things with a
bit more detail so that we can get to the root of the problem.

HTH,

Cary

 

[Lanwench [MVP - Exchange]]

How many NICs on this server?

I run the Dcpromo , Whene I get to the "FULL DNS name of new
domain:" I wrote server.bk - NEXT

I get the error "the default Netbios domain name "server0" was
selected due to name conflicts on the network."

don't forget that the server connect to empty HUB

I don't have any domain, the server connect to empty HUB.

Essam,

Then I might suggest that you either give that WIN2000 Server that
you are trying to dcpromo another name or that you look into why
there is another computer on the network with that particular name.

Did you ever have a Domain Controller that had the same name as the
one that you are trying to give to this one? That would probably
indicate that someone did not properly remove that Domain
Controller from AD or that it crashed and no one did a metadata
cleanup. Should this be the case take a look at the following MSKB
Article to remove the former DC properly from AD so that you can
continue with the dcpromo of this one:

http://support.microsoft.com/?id=216498

If none of these is what happened then maybe you can explain things
with a bit more detail so that we can get to the root of the
problem.

HTH,

Cary

yeh , I put it in the HUB,

The problem that I can't complete the active directory
I restart the server, and now I get message that another server
in this domain,, and the name of my server is founded in this
network!!!!


þþ"Cary Shultz [A.D. MVP]" <[email protected]> ëúá áäåãòä
Essam,

It needs to be plugged into a hub or a switch. Just stick a Cat5 cable
in
the NIC ( on the Server ) and the other end into a hub or switch. The
hub
or switch does not have to be connected to anything, just turned
on....

Now you can continue.

You can also use the MS Loopback Adapter if you do not have a hub
or a switch.

Cary

Hi,

I install new server 2000,
in the wizard start the active directory install and didn't

connect

to
the
"HUB" and it stop responding to install,

I restart the server and now I can't to install the server,

get message the the name of this server was found in the network

 

[Essam]

Hi,

I install new server 2000,
in the wizard start the active directory install and didn't connect to the
"HUB" and it stop responding to install,

I restart the server and now I can't to install the server,

get message the the name of this server was found in the network

 

[Essam]

yeh , I put it in the HUB,

The problem that I can't complete the active directory
I restart the server, and now I get message that another server in this
domain,, and the name of my server is founded in this network!!!!

 

[Tiago]

Hello

Probably you have a bad installation of the server OS.
Clean up and reinstall everything again. Use an other
installation disc. Dont go ahead, if you already have
errors on the "Domain".

Greetings Tiago

-----Original Message-----
I run the Dcpromo , Whene I get to the "FULL DNS name of new domain:" I
wrote server.bk - NEXT

I get the error "the default Netbios domain

name "server0" was selected due

to name conflicts on the network."

don't forget that the server connect to empty HUB

I don't have any domain, the server connect to empty HUB.


þþ"Cary Shultz [A.D. MVP]" <[email protected]> ëúá áäåãòä

Essam,

Then I might suggest that you either give that

WIN2000 Server that you
are why there is
another

same name as the one
that

Controller from AD or that
it this be the case take
a

former DC properly from
AD

explain things with
a another server in
this

domain,, and the name of my server is founded in this network!!!!


þþ"Cary Shultz [A.D. MVP]" <[email protected]> ëúá áäåãòä
Essam,

It needs to be plugged into a hub or a switch.

Just stick a Cat5
cable

in
the NIC ( on the Server ) and the other end into

a hub or switch.
The

anything, just turned
on....

do not have a hub or
a install and didn't
connect

to

.

 

[Essam]

I don't have any domain, the server connect to empty HUB.

 

[Essam]

I run the Dcpromo , Whene I get to the "FULL DNS name of new domain:" I
wrote server.bk - NEXT

I get the error "the default Netbios domain name "server0" was selected due
to name conflicts on the network."

don't forget that the server connect to empty HUB

I don't have any domain, the server connect to empty HUB.

Essam,

Then I might suggest that you either give that WIN2000 Server that you are
trying to dcpromo another name or that you look into why there is another
computer on the network with that particular name.

Did you ever have a Domain Controller that had the same name as the one that
you are trying to give to this one? That would probably indicate that
someone did not properly remove that Domain Controller from AD or that it
crashed and no one did a metadata cleanup. Should this be the case take a
look at the following MSKB Article to remove the former DC properly from AD
so that you can continue with the dcpromo of this one:

http://support.microsoft.com/?id=216498

If none of these is what happened then maybe you can explain things with a
bit more detail so that we can get to the root of the problem.

HTH,

Cary

yeh , I put it in the HUB,

The problem that I can't complete the active directory
I restart the server, and now I get message that another server in this
domain,, and the name of my server is founded in this network!!!!


þþ"Cary Shultz [A.D. MVP]" <[email protected]> ëúá áäåãòä
Essam,

It needs to be plugged into a hub or a switch. Just stick a Cat5

cable

in
the NIC ( on the Server ) and the other end into a hub or switch.

The
hub

or switch does not have to be connected to anything, just turned on....

Now you can continue.

You can also use the MS Loopback Adapter if you do not have a hub or a
switch.

Cary

Hi,

I install new server 2000,
in the wizard start the active directory install and didn't

connect

to

 

[Naveen]

Essam,
Where is top level domain,example full dns name enter as
computername.server.com,then see that when it goes to
netbios domain it will take as computername.
Hope it solves the problem

-----Original Message-----
I run the Dcpromo , Whene I get to the "FULL DNS name of new domain:" I
wrote server.bk - NEXT

I get the error "the default Netbios domain

name "server0" was selected due

to name conflicts on the network."

don't forget that the server connect to empty HUB

I don't have any domain, the server connect to empty HUB.


þþ"Cary Shultz [A.D. MVP]" <[email protected]> ëúá áäåãòä

Essam,

Then I might suggest that you either give that

WIN2000 Server that you
are why there is
another

same name as the one
that

Controller from AD or that
it this be the case take
a

former DC properly from
AD

explain things with
a another server in
this

domain,, and the name of my server is founded in this network!!!!


þþ"Cary Shultz [A.D. MVP]" <[email protected]> ëúá áäåãòä
Essam,

It needs to be plugged into a hub or a switch.

Just stick a Cat5
cable

in
the NIC ( on the Server ) and the other end into

a hub or switch.
The

anything, just turned
on....

do not have a hub or
a install and didn't
connect

to

.