Re: Adding an NT 4.0 BDC to 2003 Active Directory Network

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

From: Dan DeStefano (augur5ATyahooDOTcom)
Date: 06/08/04 

Date: Tue, 8 Jun 2004 01:48:00 -0400

you can try disabling smb signing just to get the nt4 bdc up, and the domain
info copied, then re-enable it. there shouldnt be any problems unless you
have client machines set to require smb signing. can you do this off-hours
just in case?

Dan

"Philip Gerard" <anonymous@discussions.microsoft.com> wrote in message
news:18CF0D51-4BBB-49B7-8114-C41BF1A68FD0@microsoft.com...
> Hi,
>
> I am trying to set up a test network to prepare for an Exchange 5.5 to
Exchange 2003 migration. To get my regular domain accounts onto my test
network I was going to add an NT 4.0 BDC to my 2003 AD domain, remove it,
add it to my test environment, and promote it to the PDC. Then I was going
to recreate my AD environment by upgrading this NT 4.0 machine. The problem
I am running into is that when I go to create my BDC it cannot log onto my
AD network so I cannot get it set up (the only copy of NT I have is 4.0
sp1).. Would the solution to this problem be to temporarily disable SMB
signing on my 2003 AD domain? Are there any potential problems on my live
network in doing this? Is the following procedure the correct one to make
this change:
>
> In the Default Domain Controllers Policy,
> Under Computer Configuration/Windows Settings/Security Settings/Local
> Policies/Security Options,
> right-click "Microsoft network server: Digitally sign communications
> (always)",
> click Properties, and then click Disabled.
>
> Thanks for any help in advance?
>
> P.S. Is there a better way to accomplish what I am trying to do in setting
up a test environment? I thought about doing dcpromo on a 2003 server and
then taking that box off the network and then deleting that box under AD
Domain Controllers. Somewhere I heard or read that this might require some
AD cleanup whereas the other method would not. Any truth to this?
>

Relevant Pages

  • Event Viewer Networking Connectivity
    ... What we need is a very solid working network. ... Here's what lead up to this scenario of BDC replacement. ... On the corporate side I can see our servers. ... Registration of the DNS record ...
    (microsoft.public.windows.server.networking)
  • Re: SMB packet and secure channel signing
    ... You know, in all the times that you and I have the debate on SMB Signing, ... > Optionally you can do "if client agrees" and thus the signing will be ... > Just don't screw up in the process of disabling these suckers. ... SMB Signing puts a tag on each and every network packet ...
    (microsoft.public.windows.server.sbs)
  • Re: SMB signing problem with winXP
    ... In an SBS 2003 network with Windows XP workstations I did have ... It drove the client crazy because it hung ... >> SMB Signing in the Default Domain Policy and the Default Domain ... >> There is no problem with Disabling SMB Signing entirely. ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: Migration from SBS 4.5 to Windows 2003 Server
    ... Once its a BDC and DNS etc and synch is all done... ... You can't promote it to a PDC while connected to the SBS network ... server, do I need to disable it prior to installing the new DNS server on ...
    (microsoft.public.backoffice.smallbiz)
  • Re: Server Lockup Copying File to Network
    ... I don't know for sure that smb signing is related to your ... to connect to a Windows 2003 Server in a workgroup. ... > What if the client operating system is the server itself copying to ... >> reboot I would install the latest drivers from Intel for your network ...
    (microsoft.public.windows.server.networking)