Re: xp workstations unable to log-in to win 2003 domain at boot-up

Yes, try to move the computers to another workgroup first (e.g. just name it
A). Reboot the PC and then try to join it to domain...

--
Mike
Microsoft MVP - Windows Security

"joeydb331" <joeydb331@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:419B94F5-6D13-4228-A661-C27DA0F5DBDD@xxxxxxxxxxxxxxxx
> yes i can access that share no problem . . . would you recommend i change
> the
> name of the workgroup to be differnt than the domain. right now they are
> both 'drive-ind' . . they were before too when everything worked so i
> didnt
> think of it as an issue but maybe that could have something to do with it
> .
> .what do you think/ ill check the event logs and send you whateveer
> information i can gleen from them
> thanks agian yoiure my hero =)
>
> "Miha Pihler [MVP]" wrote:
>
>> Can you access this share from your client...
>>
>> \\dcserver\sysvol\
>>
>> where dcserver is name of your new server.
>>
>> Can you again check event logs on your domain controller and your client
>> for
>> any errors. Check System and Application logs.
>>
>> I am slowly running out of ideas what could be wrong.
>>
>> My advice is still to remove the client PC from old domain that doesn't
>> exist any more and join them to workgroup. Reboot the PC and try to add
>> them
>> to new domain...
>>
>> --
>> Mike
>> Microsoft MVP - Windows Security
>>
>> "joeydb331" <joeydb331@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:C1DCF678-D655-4995-8A2B-306FBB9FB7EC@xxxxxxxxxxxxxxxx
>> > All of the workstations are xp professional, most of which have
>> > service
>> > pack
>> > 2. I did reboot the server after changing the various settings.
>> > Lastly
>> > every workstation is having the same problem. They are all part of the
>> > workgroup and none of them are able to log-in to the domain at
>> > boot-up.
>> > After each workstation boots up though, they can all access the dc
>> > machine
>> > (the user is presented with a login screen when trying to access files
>> > on
>> > the
>> > server and if they have the right permissions, they can use those
>> > files
>> > no
>> > problem.
>> > I am perplexed!
>> >
>> >
>> > ihler [MVP]" wrote:
>> >
>> >> Hi,
>> >>
>> >> Did you reboot the DC server or restart NetLogon service?
>> >>
>> >> To be able to go to the internet you will have to set up DNS on DC
>> >> server.
>> >> Open DNS MMC and right click on server name in MMC. Now go to
>> >> forwarders
>> >> tab
>> >> end enter your ISP DNS server or what you had set before
>> >> (192.168.1.1).
>> >>
>> >> Can you try to add some other PC to the domain -- if there is a
>> >> problem
>> >> with
>> >> this particular one?
>> >>
>> >> What version of client do you use? E.g. Windows XP Professional with
>> >> Service
>> >> Pack 2?
>> >>
>> >> --
>> >> Mike
>> >> Microsoft MVP - Windows Security
>> >>
>> >> "joeydb331" <joeydb331@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> >> news:A16C8265-7C15-4B3F-873E-EC141AA367D9@xxxxxxxxxxxxxxxx
>> >> > okay i set the servers ip address and preferred dns server manually:
>> >> > ip 192.168.1.101
>> >> > dns 192.168.1.101
>> >> >
>> >> > I deleted all of the 'computers' from the active directory. I also
>> >> > disabled
>> >> > my network card, changed the name of my pc (for the new client
>> >> > set-up),
>> >> > and
>> >> > rebooted after the changes had been made to the server.
>> >> >
>> >> > When i to set the preferred dns server (address above) on my
>> >> > workstation
>> >> > pc
>> >> > it would no longer allow me to access the internet and I received
>> >> > the
>> >> > same
>> >> > error message as I originally wrote about about when i tried to join
>> >> > the
>> >> > domian.
>> >> >
>> >> > I am discouraged.
>> >> > Thank you so much for your help so far though . . . maybe some of
>> >> > that
>> >> > information will help you diagnose whats wrong with this nightmare.
>> >> >
>> >> > Looking forward to hearing from you,
>> >> >
>> >> > Joey
>> >> >
>> >> > "Miha Pihler [MVP]" wrote:
>> >> >
>> >> >> Hi,
>> >> >>
>> >> >> My recommendation is to put DC server to static IP address. Also
>> >> >> change
>> >> >> preferred DNS settings on the server to point back to the server
>> >> >> itself.
>> >> >> E.g. if you give your server IP address 192.168.1.50 enter this IP
>> >> >> address
>> >> >> under preferred DNS server. After you did these two changes,
>> >> >> restart
>> >> >> netlogon service.
>> >> >>
>> >> >> Now, change also TCP configuration of the client (e.g. Windows XP).
>> >> >> They
>> >> >> must also point to 192.168.1.50 for preferred DNS server.
>> >> >>
>> >> >> After you do this, try to add client to domain again (try with
>> >> >> different
>> >> >> clients)...
>> >> >>
>> >> >> --
>> >> >> Mike
>> >> >> Microsoft MVP - Windows Security
>> >> >>
>> >> >> "joeydb331" <joeydb331@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> >> >> news:D7F2A9C9-02B9-4C24-9E4C-B212C6004DE4@xxxxxxxxxxxxxxxx
>> >> >> > That reply i just sent you was obviously a mistake. Here's the
>> >> >> > information
>> >> >> > that i left out:
>> >> >> >
>> >> >> > The errror message originally was:
>> >> >> >
>> >> >> > " your computer could not be joined to the domain because the
>> >> >> > following
>> >> >> > error
>> >> >> > has occured: the specified server cannot perform the requested
>> >> >> > operation."
>> >> >> >
>> >> >> > recently it changed to something about not being able to use
>> >> >> > multiple
>> >> >> > instances of user log-ins (or something like that) i'd tell you
>> >> >> > the
>> >> >> > exact
>> >> >> > message but unfortuantely i just tried it again and im back to
>> >> >> > the
>> >> >> > original
>> >> >> > error message again! dag nab it.
>> >> >> >
>> >> >> > I am using a linksys router that has a built-in dhcp server, etc.
>> >> >> > (i'm
>> >> >> > sure
>> >> >> > that you're familiar with them). Due to that, I just left the
>> >> >> > majority
>> >> >> > of
>> >> >> > settings up to the router (like automatic ip address, etc.) I am
>> >> >> > under
>> >> >> > the
>> >> >> > impression that a static ip address would be better, but this
>> >> >> > business
>> >> >> > internet service is thru SBC and they are not paying for any
>> >> >> > static
>> >> >> > ip's.
>> >> >> >
>> >> >> > When checking the event viewer it states that DNS has started and
>> >> >> > doesn't
>> >> >> > show any errors.
>> >> >> >
>> >> >> > ip address 192.168.1.(100 - 150
>> >> >> > automatically
>> >> >> > assigned
>> >> >> > subnet mask 255.255.255.0
>> >> >> > default gateway 192.168.1.1 (This is the routers
>> >> >> > ip
>> >> >> > address)
>> >> >> > dhcp server 192.168.1.1
>> >> >> >
>> >> >> > dns server 192.168.0.1 (This is the SBC
>> >> >> > DSL
>> >> >> > modem's
>> >> >> > address)
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > "Miha Pihler [MVP]" wrote:
>> >> >> >
>> >> >> >> Hi,
>> >> >> >>
>> >> >> >> How is DNS set up on Domain Controller (DC)?
>> >> >> >>
>> >> >> >> What did you set for preferred DNS server under TCP/IP settings
>> >> >> >> on
>> >> >> >> DC?
>> >> >> >>
>> >> >> >> What did you set for preferred DNS server under TCP/IP settings
>> >> >> >> on
>> >> >> >> client
>> >> >> >> PC?
>> >> >> >>
>> >> >> >> What is the exact error that you get when you try to join it to
>> >> >> >> domain?
>> >> >> >>
>> >> >> >> Don't pre-create any computer accounts (if you already did -
>> >> >> >> remove
>> >> >> >> them)
>> >> >> >> and then try processed described before. Once the processed
>> >> >> >> described
>> >> >> >> in
>> >> >> >> my
>> >> >> >> previous post is successful it will create Computer account on
>> >> >> >> domain
>> >> >> >> controller automatically.
>> >> >> >>
>> >> >> >> You should also check Event Logs on DC (System and Application
>> >> >> >> logs -
>> >> >> >> and
>> >> >> >> also others) for any errors.
>> >> >> >>
>> >> >> >> --
>> >> >> >> Mike
>> >> >> >> Microsoft MVP - Windows Security
>> >> >> >>
>> >> >> >> "joeydb331" <joeydb331@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
>> >> >> >> message
>> >> >> >> news:B2C47AF2-B42B-4072-B3BC-3060B1AECCA1@xxxxxxxxxxxxxxxx
>> >> >> >> > When i try what you've suggested (again THANKS so much for
>> >> >> >> > being
>> >> >> >> > cool
>> >> >> >> > enough
>> >> >> >> > to write all of that stuff out for me) I have no problem
>> >> >> >> > becoming
>> >> >> >> > a
>> >> >> >> > member
>> >> >> >> > of
>> >> >> >> > the workgroup (and it happens just like you describe), but
>> >> >> >> > when i
>> >> >> >> > then
>> >> >> >> > try
>> >> >> >> > to
>> >> >> >> > join the domain i recieve that same damn error message that
>> >> >> >> > i've
>> >> >> >> > been
>> >> >> >> > getting
>> >> >> >> > all along.
>> >> >> >> > I'm beginning to think that something is wrong with the way
>> >> >> >> > that
>> >> >> >> > I
>> >> >> >> > set-up
>> >> >> >> > the win 2003 server PC. Maybe some policy setting I'm
>> >> >> >> > missing,
>> >> >> >> > trust
>> >> >> >> > relationship issue, or service that i should have running but
>> >> >> >> > don't,
>> >> >> >> > etc.
>> >> >> >> > Hey when you set-up a 'computer' in the 'active directory
>> >> >> >> > users
>> >> >> >> > and
>> >> >> >> > computers' area and it asks you if the computer will be a
>> >> >> >> > 'managed
>> >> >> >> > computer',
>> >> >> >> > do you ever answer 'yes' to that and if so, how do you
>> >> >> >> > determine
>> >> >> >> > your
>> >> >> >> > 'GUID'?
>> >> >> >> > could my issue be some how related to that?
>> >> >> >> > Thanks again for any and all help that you are willing to
>> >> >> >> > provide
>> >> >> >> > =)
>> >> >> >> >
>> >> >> >> > "Miha Pihler [MVP]" wrote:
>> >> >> >> >
>> >> >> >> >> Hi,
>> >> >> >> >>
>> >> >> >> >> Right click on My Computer on PC that you want to add to
>> >> >> >> >> domain.
>> >> >> >> >> Now
>> >> >> >> >> click
>> >> >> >> >> on Properties. Click on Change and under Domain enter name of
>> >> >> >> >> your
>> >> >> >> >> new
>> >> >> >> >> domain.
>> >> >> >> >>
>> >> >> >> >> If computer is already a member of domain then enter a name
>> >> >> >> >> (e.g.
>> >> >> >> >> Temp)
>> >> >> >> >> under Workgroup. Once the computer is joined to Workgroup (it
>> >> >> >> >> will
>> >> >> >> >> say
>> >> >> >> >> "Welcome to Temp Workgroup) go back and under domain enter
>> >> >> >> >> name
>> >> >> >> >> of
>> >> >> >> >> your
>> >> >> >> >> new
>> >> >> >> >> domain. (You don't have to reboot yet). Once a computer is
>> >> >> >> >> back
>> >> >> >> >> in
>> >> >> >> >> domain
>> >> >> >> >> do
>> >> >> >> >> a reboot and your computer should now be able to log in to
>> >> >> >> >> the
>> >> >> >> >> domain.
>> >> >> >> >>
>> >> >> >> >> --
>> >> >> >> >> Mike
>> >> >> >> >> Microsoft MVP - Windows Security
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> "joeydb331" <joeydb331@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
>> >> >> >> >> message
>> >> >> >> >> news:EC299BDF-3067-454C-9245-7DE703E267A7@xxxxxxxxxxxxxxxx
>> >> >> >> >> >I read your response (thank you very much by the way) and
>> >> >> >> >> >gave
>> >> >> >> >> >it
>> >> >> >> >> >a
>> >> >> >> >> >try.
>> >> >> >> >> > First, I opened the 'active directory users and computers'
>> >> >> >> >> > mmc
>> >> >> >> >> > on
>> >> >> >> >> > the
>> >> >> >> >> > 2003
>> >> >> >> >> > server, then I added a new PC named "tryagain" in the
>> >> >> >> >> > 'computers'
>> >> >> >> >> > section,
>> >> >> >> >> > checking the various settings, assignign rights and
>> >> >> >> >> > permissions,
>> >> >> >> >> > etc.
>> >> >> >> >> > Then
>> >> >> >> >> > I
>> >> >> >> >> > renamed one of the XP workstations to "tryagain", rebooted,
>> >> >> >> >> > and
>> >> >> >> >> > attempted
>> >> >> >> >> > to
>> >> >> >> >> > go through the network wizard process that I had explained
>> >> >> >> >> > in
>> >> >> >> >> > my
>> >> >> >> >> > very
>> >> >> >> >> > first
>> >> >> >> >> > post. Unfortunatley I got the exact same error message
>> >> >> >> >> > AGAIN.


.

Relevant Pages

  • Cant login the morning after.
    ... I tried to log on after a reboot and got 2 ... logon after multiple reboots without getting a error ... server re-syncronize. ... >Each workstation has netbios turned off, ...
    (microsoft.public.windowsxp.security_admin)
  • Re: SBE Workgroup Mode or Forced Conversion? Downgrading to Standard 2
    ... SP2 workstation set up with file sharing and Internet Connection Sharing. ... With workgroups I have two computers in a workgroup ... I don't want the server to have a privileged ...
    (microsoft.public.windows.server.sbs)
  • Remote Access Assistance Needed.
    ... Server 1 and the one workstation HAVE to be a specific ... different specific workgroup name. ... 3> Both locations have broadband internet connections. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Front End Back End Problems
    ... which is basicly all of our current databases. ... ends are all located on local workstation drives and the ... out the server and there is no reported problems with it. ... >> default workgroup that comes with Access. ...
    (microsoft.public.access.security)
  • Re: What to do with the clients??
    ... Prior to doing this, make sure you know the password for the Workstation Administrator Account. ... Click in the radio button for Workgroup and leave the default name WORKGROUP ... Cris Hanna [SBS - MVP] ... Windows Small Business Server 2008 Unleashed ...
    (microsoft.public.windows.server.sbs)
Loading