Re: Adding Windows NT 3.5 Client to Domain

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Ace Fekay [MVP] (PleaseSubstituteMyActualFirstName&LastNameHere_at_hotmail.com)
Date: 02/07/04


Date: Sat, 7 Feb 2004 10:11:21 -0500

In news:3FFD76B8.AA3DE1FF@nomail.phxint.please.ru,
Kirill S. Palagin <kpalagin@nomail.phxint.please.ru> posted their thoughts,
then I offered mine
> Actually you can turn off SMB signing requirment.
> http://support.microsoft.com/default.aspx?scid=kb;en-us;555038
>
> Brian O'Neil wrote:
>
>> Windows Server 2003 requires all clients participate in
>> SMB signing. To achieve this in 9x, and NT 4.0 you
>> install the DSclient.exe package.
>> Unfortunately, this is not avaialable for NT 3.5 or 3.51
>> I don't believe you can turn off SMB signing in 2003.
>>
>> -Brian
>>> -----Original Message-----
>>> I'm attempting to add a Windows NT 3.5 machine into to
>> my
>>> domain but when I attempt to join I receive a message
>>> stating that the domain controller could not be found.
>> The
>>> machine is running software that is specific to Windows
>> NT
>>> 3.5 and cannot be upgraded to NT 4 or Win2000. I also
>>> tried adding the computer account but the computer name
>>> has an underscore in the name and AD does not allow that
>>> character.
>>> .

In addition, you can goto the Default Domain Controller Policy:
Expand Local Policies,
In detail pane, double click:
"Microsoft network server: Digitally sign communication (always)"
Ensure that Define this policy is checked
Select Disabled
Click Ok

This will allow backward level clients to authenticate into the domain. This
is a method we use to allow DOS based clients to access data on a 2k3 DC
during our auto classroom setups for the Win2003 classes, and applies to W9x
and NT4 since their authentication methods are similar.

-- 
Regards,
Ace
Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.
Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
-- 
=================================


Relevant Pages

  • Re: User and Group Permissions
    ... I am the administrator of Windows Server ... > for testing purposes for our clients. ... > software while not being able to access Control Panel, ... With two apps you the easiest way is to build a group (do it with a separate ...
    (microsoft.public.windows.server.active_directory)
  • Re: Remote Windows 2003 server setup
    ... you do not want to join the windows server 2003 to ... Windows server AD newsgroup: ... the office for the 4 clients. ... you may want to contact Microsoft CSS directly. ...
    (microsoft.public.windows.server.sbs)
  • Re: Error 80072EFD....yet again
    ... Microsoft Security Advisory: Microsoft Windows Server Update ... clients that used to be able to auto-update without problems. ... and configured all sites in Trusted Sites on clients and in ISA Management ...
    (microsoft.public.windowsupdate)
  • Re: Remotely attached site
    ... > Thanks for using this newsgroup. ... > I suggest you follow the steps below to check if the SMB signing on SBS ... > sever is match with the setting on the remote site clients. ... > clients and SBS server to see if the issue can be resolved. ...
    (microsoft.public.windows.server.sbs)
  • Re: Active Directory and Win98 and NT 4.0 clients
    ... See this article for details about compatibility issues: ... Modify Security Settings and User Rights Assignments: ... The increased security in Win2003 will affect clients due to vSMB signing ... >> The problem is likely SMB signing, ...
    (microsoft.public.win2000.active_directory)