Re: XP Pro - Logging on to Domain issues
- From: "Doug Sherman [MVP]" <dsherman@xxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 24 Aug 2005 10:56:38 -0400
I think you're in the right place. What I meant was that you could use
Active Directory Group Policy to pump this setting out to all machines in
the domain or an OU within the domain as distinguished from changing the
setting on an individual machine.
To change the setting on an individual machine (probably the best way to
test whether this will solve your problem):
Click Start/Run gpedit.msc ENTER.
Expand Computer Configuration, Expand Administrative Templates, Expand
System, and click on Logon - enable the policy.
Note - it may take 2 logons for the policy to be effective.
Doug Sherman
MCSE, MCSA, MCP+I, MVP
"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
> > >
> > >
> >
> >
>
>
.
- References:
- XP Pro - Logging on to Domain issues
- From: Bobby
- Re: XP Pro - Logging on to Domain issues
- From: Doug Sherman [MVP]
- Re: XP Pro - Logging on to Domain issues
- From: Bobby
- XP Pro - Logging on to Domain issues
- Prev by Date: Re: Upgrading XP home edition to XP Pro
- Next by Date: Re: XP Pro - Logging on to Domain issues
- Previous by thread: Re: XP Pro - Logging on to Domain issues
- Next by thread: Re: XP Pro - Logging on to Domain issues
- Index(es):
Relevant Pages
|
