NT4 to server 2003 upgrade problems

ok... finally got the NT4 PDC up and running with 2003 and AD. our few
remaining windows 98 clients could not log on... had to install WINS on the
new 2003 DC. why is this? why isnt DNS enough?

also... lets say the NT4 domain was DOMAIN and the new AD domain is
DOMAIN.COM, will all clients now have to be joined to the new DOMAIN.COM
domain? whats the best practice here? thank you


<(E-Mail Removed)> wrote in message
news:uQ4id.6961$(E-Mail Removed) t...
> ok... finally got the NT4 PDC up and running with 2003 and AD. our few
> remaining windows 98 clients could not log on... had to install WINS on
> the new 2003 DC. why is this? why isnt DNS enough?
>

Windows 98 uses netbios name resolution to locate domain controllers which
is why wins is needed. Windows 2000/XP Pro can use dns because they are
capable of locating the _srv dns records to locate the domain controllers
while Windows 98 can not. Windows 98 relies on the netbios name
registrations that you would see when running the nbtstat -n command on a
domain controller. The link below has more details. --- Steve

http://support.microsoft.com/kb/q247811/

<(E-Mail Removed)> wrote in message
news:uQ4id.6961$(E-Mail Removed) t...
> ok... finally got the NT4 PDC up and running with 2003 and AD. our few
> remaining windows 98 clients could not log on... had to install WINS on
> the new 2003 DC. why is this? why isnt DNS enough?
>

Yes, all NT4.0/W2K/XP Pro/W2003 computers will need to be joined to the
DOMAIN.COM domain to have full functionality in the domain such as Group
Policy [not NT4.0 computers though] . Their computer accounts will by
default be located in the computers container in Active Directory Users and
Computers. When you join an NT4.0 computer to the domain use the netbios
name when specifying the domain name [no .com] . W98 type operating systems
can not be joined to the domain. I suggest you install the support tools on
your domain controllers. You will find netdiag, dcdiag, gpotool, gpresult,
and replmon in particualr very helpful. Netdiag and gpresult will also be
extremely helpful in troubleshooting domain computer issues such as problems
with connectivity to domain controllers. --- Steve


<(E-Mail Removed)> wrote in message
news:675id.7553$(E-Mail Removed) t...
> also... lets say the NT4 domain was DOMAIN and the new AD domain is
> DOMAIN.COM, will all clients now have to be joined to the new DOMAIN.COM
> domain? whats the best practice here? thank you
>
>
> <(E-Mail Removed)> wrote in message
> news:uQ4id.6961$(E-Mail Removed) t...
>> ok... finally got the NT4 PDC up and running with 2003 and AD. our few
>> remaining windows 98 clients could not log on... had to install WINS on
>> the new 2003 DC. why is this? why isnt DNS enough?
>>
>
>

question... all windows xp machines were members of the old NT 4 domain
"DOMAIN". when the server upgrade was done and the nt4 pdc was now a 2003 AD
DC, windows xp machines logged on this morning and under computer
properties, computer name, they are listed as members of the new DOMAIN.COM
domain... without ever specifically joining this new domain.... whats going
on?



"Steven L Umbach" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Yes, all NT4.0/W2K/XP Pro/W2003 computers will need to be joined to the
> DOMAIN.COM domain to have full functionality in the domain such as Group
> Policy [not NT4.0 computers though] . Their computer accounts will by
> default be located in the computers container in Active Directory Users
> and Computers. When you join an NT4.0 computer to the domain use the
> netbios name when specifying the domain name [no .com] . W98 type
> operating systems can not be joined to the domain. I suggest you install
> the support tools on your domain controllers. You will find netdiag,
> dcdiag, gpotool, gpresult, and replmon in particualr very helpful. Netdiag
> and gpresult will also be extremely helpful in troubleshooting domain
> computer issues such as problems with connectivity to domain
> controllers. --- Steve
>
>
> <(E-Mail Removed)> wrote in message
> news:675id.7553$(E-Mail Removed) t...
>> also... lets say the NT4 domain was DOMAIN and the new AD domain is
>> DOMAIN.COM, will all clients now have to be joined to the new DOMAIN.COM
>> domain? whats the best practice here? thank you
>>
>>
>> <(E-Mail Removed)> wrote in message
>> news:uQ4id.6961$(E-Mail Removed) t...
>>> ok... finally got the NT4 PDC up and running with 2003 and AD. our few
>>> remaining windows 98 clients could not log on... had to install WINS on
>>> the new 2003 DC. why is this? why isnt DNS enough?
>>>
>>
>>
>
>

That is all part of the upgrade process when you upgraded your NT4.0 PDC to
a Windows 2003 domain controller. Sounds like things went well! Be sure your
dns is configured correctly in the domain as if not configured correctly it
will be a cause of a number of problems. Biggest problem is configuring
domain computers with ISP dns servers in their preferred dns server list.
See the FAQ below on AD dns if interested. --- Steve

http://support.microsoft.com/default...en-us%3B291382

<(E-Mail Removed)> wrote in message
news:RN7id.8855$(E-Mail Removed) t...
> question... all windows xp machines were members of the old NT 4 domain
> "DOMAIN". when the server upgrade was done and the nt4 pdc was now a 2003
> AD DC, windows xp machines logged on this morning and under computer
> properties, computer name, they are listed as members of the new
> DOMAIN.COM domain... without ever specifically joining this new domain....
> whats going on?
>
>
>
> "Steven L Umbach" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Yes, all NT4.0/W2K/XP Pro/W2003 computers will need to be joined to the
>> DOMAIN.COM domain to have full functionality in the domain such as Group
>> Policy [not NT4.0 computers though] . Their computer accounts will by
>> default be located in the computers container in Active Directory Users
>> and Computers. When you join an NT4.0 computer to the domain use the
>> netbios name when specifying the domain name [no .com] . W98 type
>> operating systems can not be joined to the domain. I suggest you install
>> the support tools on your domain controllers. You will find netdiag,
>> dcdiag, gpotool, gpresult, and replmon in particualr very helpful.
>> Netdiag and gpresult will also be extremely helpful in troubleshooting
>> domain computer issues such as problems with connectivity to domain
>> controllers. --- Steve
>>
>>
>> <(E-Mail Removed)> wrote in message
>> news:675id.7553$(E-Mail Removed) t...
>>> also... lets say the NT4 domain was DOMAIN and the new AD domain is
>>> DOMAIN.COM, will all clients now have to be joined to the new DOMAIN.COM
>>> domain? whats the best practice here? thank you
>>>
>>>
>>> <(E-Mail Removed)> wrote in message
>>> news:uQ4id.6961$(E-Mail Removed) t...
>>>> ok... finally got the NT4 PDC up and running with 2003 and AD. our few
>>>> remaining windows 98 clients could not log on... had to install WINS on
>>>> the new 2003 DC. why is this? why isnt DNS enough?
>>>>
>>>
>>>
>>
>>
>
>