Re: I'm still googling, but since I'm roll over....

From: Merv Porter [SBS-MVP] (mwport_at_no_spam_hotmail.com)
Date: 03/06/05 

Date: Sat, 5 Mar 2005 20:45:57 -0500

Also found..

"Specified Domain Either Does Not Exist or Could Not Be Contacted" Error
Message When You Try to Join a Windows NT 4.0 Domain
http://support.microsoft.com/default.aspx?scid=kb;en-us;285800 

-- 
Merv  Porter  [SBS MVP]
===================================
"Merv Porter [SBS-MVP]" <mwport@no_spam_hotmail.com> wrote in message
news:u$FclweIFHA.2428@TK2MSFTNGP10.phx.gbl...
> What happens if you put the NT workstation in a new workgroup, reboot,
then
> try to join the SBS domain?
>
> -- 
> Merv  Porter  [SBS MVP]
> ===================================
> "IBC" <spamityspam@spam.spam> wrote in message
> news:OOVF2BeIFHA.4060@TK2MSFTNGP14.phx.gbl...
> > Merv,
> >
> > Thanks for looking! There are conflicts between the two methods listed,
> Ones
> > says make everything static (WINS, DNS) and the other says it shouldn't
> be.
> > (it wasn't on the last server either) I've tried manually adding the
> machine
> > several times, but it continues to say it cannot join the domain. I
tried
> > deleting the account and joining, making a new account at the server and
> > joining....nothing wants to work.
> >
> > I'm finding all sorts of people with this issue, but no firm solutions.
> >
> > Thanks again!
> >
> > -- 
> > "Nostradamus didn't mention anything about new viruses, so....I'm Cool."
> >
> > .
> > "Merv Porter [SBS-MVP]" <mwport@no_spam_hotmail.com> wrote in message
> > news:%23hXZ%232dIFHA.1396@TK2MSFTNGP10.phx.gbl...
> > > Any help here?
> > >
> > >
> >
>
http://groups-beta.google.com/group/microsoft.public.windows.server.sbs/browse_thread/thread/acea63f6fbab5c8b/3b2ab67ced3c5092?q=sbs+2003+%22Unable+to+connect+to+the+domain+controller+for+this+domain%22#3b2ab67ced3c5092
> > >
> > >
> > > And from SBS 2003 Help
> > > --------------------------------------------
> > > Computers running Windows NT Workstation 4.0
> > >
> > > From the server:
> > >
> > > Create a user account
> > >
> > > Open Server Management.
> > > In the console tree, click Users.
> > > In the details pane, click Add a User.
> > > Follow the steps in the Add User Wizard to create a user account.
> > >   Note
> > >
> > > To open Server Management, click Start, and then click Server
> Management.
> > > Create a computer account
> > >
> > > Open Server Management.
> > > In the console tree, click Client Computers.
> > > In the details pane, click Set Up Client Computers.
> > > Follow the instructions in the Set Up Computer Wizard.
> > >   Note
> > >
> > > To open Server Management, click Start, and then click Server
> Management.
> > > Locate the Windows Small Business Server domain name
> > >
> > > Click Start, and then click Server Management.
> > > In the console tree, double-click Advanced Management.
> > > In the details pane, click Active Directory Users and Computers, and
> then
> > > right-click the name of the computer running Windows Small Business
> > Server.
> > > Click Properties. The domain name is located in the Domain name
> > (pre-Windows
> > > 2000) box.
> > > From the client computer:
> > >
> > > Install and configure TCP/IP
> > >
> > > For more information, see To install and configure TCP/IP on client
> > > computers running earlier versions of Windows. Client computers should
> not
> > > be configured with static WINS, DNS, or default gateway settings
unless
> a
> > > pre-existing network requires it.
> > >
> > > Configure networking settings
> > >
> > > Click Start, click Settings, click Control Panel, and then
double-click
> > > Network.
> > > Click the Identification tab. The computer running Windows NT
> Workstation
> > > 4.0 must be a member of the same domain as the computer running
Windows
> > > Small Business Server.
> > > If your client computer displays Workgroup, click Change.
> > >
> > > In the Identification Changes dialog box, under Member of, click
Domain.
> > > Type the name of the Windows Small Business Server domain.
> > > To locate the domain name from the server, click Start, right-click My
> > > Computer, click Properties, and then click the Computer Name tab.
> > >
> > > Restart the client computer.
> > > --------------------------------------------
> > >
> > > -- 
> > > Merv  Porter  [SBS MVP]
> > > ===================================
> > > "IBC" <spamityspam@spam.spam> wrote in message
> > > news:e$33bYdIFHA.2428@TK2MSFTNGP10.phx.gbl...
> > > > ....Can anybody point me to the specifics on hooking up a NT4.0 sp6
> > > client?
> > > > We have one on a proprietary controller for a large format printer
> that
> > > I'm
> > > > not allowed to upgrade. I get this message:
> > > >
> > > > "Unable to connect to the domain controller for this domain. Have
you
> > > > administrator check your computer account on the domain."
> > > >
> > > > I'll keep looking in the meantime. Thanks for taking time out of
your
> > > > weekend!
> > > >
> > > > -- 
> > > > "Nostradamus didn't mention anything about new viruses, so....I'm
> Cool."
> > > >
> > > > .
> > > >
> > > >
> > >
> > >
> >
> >
>
>

Relevant Pages

  • Re: Im still googling, but since Im roll over....
    ... > (it wasn't on the last server either) I've tried manually adding the ... >> To open Server Management, click Start, and then click Server ... click Set Up Client Computers. ... The computer running Windows NT ...
    (microsoft.public.windows.server.sbs)
  • Re: W2K RIS Servers in W2K3 Domain
    ... Setting the LAN Manager Authentication Level on a network that includes RIS: ... > We're considering upgrading the domain to Windows ... > systems on remote boot-enabled client computers by connecting the computer ... > If your network uses RIS with Windows 2000 Server, ...
    (microsoft.public.win2000.setup_deployment)
  • Re: W2K RIS Servers in W2K3 Domain
    ... Setting the LAN Manager Authentication Level on a network that includes RIS: ... > We're considering upgrading the domain to Windows ... > systems on remote boot-enabled client computers by connecting the computer ... > If your network uses RIS with Windows 2000 Server, ...
    (microsoft.public.windows.server.setup)
  • Re: W2K RIS Servers in W2K3 Domain
    ... Setting the LAN Manager Authentication Level on a network that includes RIS: ... > We're considering upgrading the domain to Windows ... > systems on remote boot-enabled client computers by connecting the computer ... > If your network uses RIS with Windows 2000 Server, ...
    (microsoft.public.windows.server.migration)
  • Re: W2K RIS Servers in W2K3 Domain
    ... Setting the LAN Manager Authentication Level on a network that includes RIS: ... > We're considering upgrading the domain to Windows ... > systems on remote boot-enabled client computers by connecting the computer ... > If your network uses RIS with Windows 2000 Server, ...
    (microsoft.public.win2000.active_directory)
Loading