Re: XP Pro - Logging on to Domain issues

Another thing discovered is when a different user tries to log on to that
computer (that has access to the domain and can log on to any of the other
computers already on the domain Win2K or not) it says the following message
now "The system cannot log you on now because the domain DOMAIN is not
available."

This makes it seem that XP Pro isn't seeing the domain??

"Bobby" <bobby@xxxxxxxxxxx> wrote in message
news:#k308lLqFHA.3672@xxxxxxxxxxxxxxxxxxxxxxx
> Hi Doug,
>
> The only thing I could find that closely resembles that is under Logon not
> Group Policy and it is "Always wait for the network at computer startup
and
> logon." Is this where you want me to go? Or if you could be kind of
enough
> to direct me to where I should go exactly?
>
> Thanks,
> Bobby
>
> "Doug Sherman [MVP]" <dsherman@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
> news:#4eb4cLqFHA.2772@xxxxxxxxxxxxxxxxxxxxxxx
> > Try disabling fast user logon - you can do this with Group Policy or run
> > gpedit.msc on the local machine:
> >
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;305293
> >
> > Doug Sherman
> > MCSE, MCSA, MCP+I, MVP
> >
> > "Bobby" <bobby@xxxxxxxxxxx> wrote in message
> > news:ukpTLQLqFHA.564@xxxxxxxxxxxxxxxxxxxxxxx
> > > Hi there,
> > >
> > > I previously posted as a mapped drive issue but it's a bit more than
> that
> > > we've discovered. We are running a Windows 2000 Server domain and any
> > "new"
> > > XP Pro machines that are joined on the domain and rebooted cannot
access
> > the
> > > network. After the reboot it seems as if you are joining the domain
by
> > > logging on but you're actually not and it's using the cached
credentials
> > > from the previous log on. We even manually put in all required
numbers
> > > (Primary DNS, Alternative DNS, Static IP, etc...) and it still doesn't
> > work.
> > > What ends up happening is let's say you go to My Network Places, then
to
> > > Entire Network, and choose Microsoft Network...all computers
(including
> > > domain controller) are visible but as soon as you go to click on one
of
> > them
> > > you can't access them (and under normal circumstances with other
clients
> > > such as previous Win2K Pro AND XP Pro you can). Then a
usernam/password
> > > dialog box pops up asking you to log on with DIFFERENT credentials
then
> > what
> > > we logged on the computer with...after which I can view the network
and
> > > shared folders and files and so on.
> > >
> > > Is there something in particular that you need to watch for when
adding
> XP
> > > Pro machines to your domain? Like I mentioned before we already have
an
> > XP
> > > Pro and an XP Home client on the domain that function just fine (the
XP
> > Home
> > > I imagine was tweaked a bit or required a bit more work to function
> > > correctly on the domain). If anyone can help me out with this that
> would
> > be
> > > great. If more info is required just let me know and I'll give it to
> you.
> > > I'm pretty good with replies.
> > >
> > > Thanks in advance guys!
> > >
> > > Bobby
> > >
> > >
> >
> >
>
>


.

Relevant Pages

  • Re: Cant use WM6 to access network shares
    ... unfortunately nothing in any of the event logs. ... the logon prompt. ... So for whatever reason it's just not passing my credentials ... Can get to about any other share on the network. ...
    (microsoft.public.pocketpc.wireless)
  • Re: IIS Auth Error - Kerberos/NTLM not accepting credentials
    ... > Services that users are having problems authenticating against. ... > someone tries to connect they are prompted for credentials. ... > Logon Failure: ... > network but the name of the machine. ...
    (microsoft.public.inetserver.iis.security)
  • Re: Domain not available on PEAP clients at first logon
    ... credentials)>>> No, I'd like a transparent access to the network. ... It is a switched, enterprise network and I'd like to implement access control ... network first, THEN get them on your secured 802.1x>>> I solved enabling PEAP with 'computer' logon in addition to 'user'>>> logon; in such a way, if a PC belongs to domain, it enters in the>>> network already before prompt and a user can>>> login even if this is his first logon or his>>> password expired. ... During next 802.1x re-authentications, I will see a user login in IAS log and>>> this is OK for me. ...
    (microsoft.public.internet.radius)
  • Re: Domain not available on PEAP clients at first logon
    ... >>> What I would suggest to you here is to go to the PEAP configuration and>> allow the user to specify the credentials > No, I'd like a transparent access to the network. ... It is a switched, enterprise network and I'd like to implement access control ... >>> The other option you have is to provision the machines on the regular>> network first, THEN get them on your secured 802.1x> I solved enabling PEAP with 'computer' logon in addition to 'user' logon;> in such a way, if a PC belongs to domain, it enters in the network already before prompt and a user can login even if this> is his first logon or his password expired. ... > During next 802.1x re-authentications, I will see> a user login in IAS log and this is OK for me. ...
    (microsoft.public.internet.radius)
  • xp long boot on AD
    ... I have also posted this request for help in Proformance & ... The two xp pro machines are taking 90 to 120 second to ... second to logon to the network. ...
    (microsoft.public.windowsxp.network_web)