Setting up a domain problem
Kjell
I'm re-working a local network ni order to create a W2003 domain with AD
The current situation is pretty comlicated to say the least.
There are at least 2 other domain controllers active (Linux and openBSD) one
which occupies the domain name xxxxxx.se which is also active on the Internet.
I was thinking of setting up xxxxxx.local as the new W2003 domain but the
wizard complains over a conflicting default netbios domain name on the
network.
and suggest the use of xxxxxx0 for netbios name.... not sure exactly what
this means....
could this conflict be between xxxxxx.se vs xxxxxx.local ??
- Or is this name conflict based on something else.?
i.e. -They have for a long time used the xxxxxx as workgroup name on many
servers and clients.
I'm not 100% sure how "Netbios name" vs "domain name" vs "host name" vs
"workgroup" name is related to each other.
The company really would like to keep the "xxxxxx" name and that's why I
would like to use "xxxxxx.local" name for the new w2003 domain.
Can I create this "xxxxxx.local" w2003 domain with netcable not connected
and then attach it without creating a hugh communication conflict on the
network.??
In the long perspective all other domain controllers will be killed and all
resources will be moved into this new W2003 domain.
95% of all clients is WinXP sp2, only a few belongs to a domain (not the
xxxxxx.se) the majority is just in the same workgroup (xxxxxx)
I guess you understand that xxxxxx is really something else, but in above
text the "xxxxxx" always represents the same name.
Kjell
Paul Bergson [MVP-DS]
another machine with the exact same name. So if you have a machine with the
name xxxxxxx or the NetBIOS domain name is xxxxxxx, you can't name either
with the exact same name.
Host Name - Usually refers to the physical name of the device defined within
the fqdn of the object
NetBIOS name - Separate from DNS host name and is usually associated with
Windows local networking
Domain Name - When referring to Windows, part of Active Directories
collection of objects
Workgroup - Local Windows grouping name, for disparate machines
You may want to use Wikipedia to try and lookup each of these. I wouldn't
press forward until you better understood the technology. Once you have
some understanding I would then find a book (Or training course) to better
prepare yourself for this adventure.
--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2003, 2000 (Early Achiever), NT
Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.
"Kjell" <Kj...@discussions.microsoft.com> wrote in message
news:99B138C4-184A-4E95...@microsoft.com...
Jorge Silva
I agreee with Paul, sounds like you have 2 machines with the same NetBIOS
name.
--
===================================
I hope that the information above helps you.
Have a Nice day.
Jorge Silva
MCSE, MVP Directory Services
===================================
"Kjell" <Kj...@discussions.microsoft.com> wrote in message
news:99B138C4-184A-4E95...@microsoft.com...
Kjell
Taking a training course and reading a couple of books is probably the best
way but not acceptable in the time frame. :-)
I've once before (at my home network) done something similar moving from
name.se to name.local accepting the suggested name0 but I dont like the
impact.
In some cases when you must give your account and password you're forced to
state kj...@name.local in full and not just kjell@name which is possible if
you don't do this move of naming.
The domain name is then presented as name0 in many situations and that is
not nice.
My brother also made the same name change going from name.se to name.local
and he managed to stay away from the side effect, but he can't remember the
details now. :-(
So, the bottom line is actually: how do you create a new domain using
name.local when you have a domain active using the name.se?
all host names are different.
the only way I see a conflict is a workgroup on approx 25 machines having
the same name, and probably the current samba domain controller having the
name.se
But; I thought that name.se and name.local was two completely different
things !!!
Kjell
Kjell
Is host name and netBios name the same thing?
Where on a Windows machine can I see the netBios name?
Is it possible that the Samba server today holding the xxxxxx.se domain is
also holding the netBios name xxxxxx ?
Non of the host names is occuping this name. Only a workgroup; is that enough?
Kjell
Jorge Silva
should get response by some other machine that has the same networkname.
--
===================================
I hope that the information above helps you.
Have a Nice day.
Jorge Silva
MCSE, MVP Directory Services
===================================
"Kjell" <Kj...@discussions.microsoft.com> wrote in message
news:91D49382-511E-40E4...@microsoft.com...
Kjell
It's the same subnet and no response with ping.
I've checked with wikipedia regarding netBios name vs host name; it looks
like this is not the same thing, but I cannot find a place to see the netBios
name on my Win2003 nor the WinXP so where is it defined?
Does anyone know if it's possible to have two domains with just differences
in top domain name part at all in the same subnet?
On the other hand the wizards says:
"This is the name that users of earlier versions of windows will use to
identify the new domain, Click Next to accept........."
Where goes the limit between earlier and not earlier windows versions?
Is this just a conflict hitting the pre Win2000 environment? we do not have
any pre win2000 machines !!
Is there a way to shutdown support for pre win2000 systems?
-and by that allowing me to use namings accepted by newer systems only.?
Kjell
Jorge Silva
properties, you'll see the Computer Name).
--
===================================
I hope that the information above helps you.
Have a Nice day.
Jorge Silva
MCSE, MVP Directory Services
===================================
"Kjell" <Kj...@discussions.microsoft.com> wrote in message
news:6B893B41-9E2D-4DC7...@microsoft.com...
Jorge Silva
the ip of the other computer that has the same name, check in the eventlog.
--
===================================
I hope that the information above helps you.
Have a Nice day.
Jorge Silva
MCSE, MVP Directory Services
===================================
"Kjell" <Kj...@discussions.microsoft.com> wrote in message
news:6B893B41-9E2D-4DC7...@microsoft.com...
Kjell
I have solved the issue; It's not a conflict first of all.
This is how it works.
Normally the computer name, aka host name is translated into netBios name
and your domain name will also be translated into a netBios group name by
dropping the top name part (.com for example)
the result must be a unique name.
So, the warning I got was simlpy a warning that netBios could not use the
normal translation by dropping the top name part, the wizard suggests adding
a zero (0) to it in order to make it unique.
A machine on our network has apparantly registered this netBios name
already, even though most of the machines are Samba and Linux machines not
using netBios at all.
If you want to test the effect, do this.
Take a local network with dc, for example mydomain.com
Now create a new domain controller in the same subnet (sharing the IP range)
and suggest it to take the domain name mydomain.local
You will now get mydomain.local with netBios group name mydomain0
Suddenly you will realize why you can refer to a machine or resource not
using fully qualified domain name, it's netBios doing the job for you. :-)
PS
netBios name does not have to be the same as host name at all, it will
probably be more complicated to set it up but it will work just the same.
Kjell
Jorge Silva
--
===================================
I hope that the information above helps you.
Have a Nice day.
Jorge Silva
MCSE, MVP Directory Services
===================================
"Kjell" <Kj...@discussions.microsoft.com> wrote in message
news:82D1250D-342B-4D49...@microsoft.com...