Re: XP Pro - Logging on to Domain issues

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: SBS 2003 Win XP/2000 Pro Clients TCP/IP Problems
    ... network and no DHCP services provided by any machines still on the network. ... Check all machines for DNS entries. ... It really sounds like a IP Address conflict the way the server stops ... > PCs, 3 of which are running Windows XP Pro, the rest 2000 Pro. ...
    (microsoft.public.windows.server.sbs)
  • Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL, Blue screen of Death
    ... I have two machines. ... I know that this has something to do with the network. ... the BSOD only occurs on XP Pro. ... Use .symfix to have the debugger choose a symbol path. ...
    (microsoft.public.windowsxp.network_web)
  • Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL, Blue screen of Death
    ... I have two machines. ... I know that this has something to do with the network. ... the BSOD only occurs on XP Pro. ... Use .symfix to have the debugger choose a symbol path. ...
    (microsoft.public.windowsxp.hardware)
  • Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL, Blue screen of Death
    ... I have two machines. ... I know that this has something to do with the network. ... the BSOD only occurs on XP Pro. ... Use .symfix to have the debugger choose a symbol path. ...
    (microsoft.public.win2000.networking)
  • Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL, Blue screen of Death
    ... I have two machines. ... I know that this has something to do with the network. ... the BSOD only occurs on XP Pro. ... Use .symfix to have the debugger choose a symbol path. ...
    (microsoft.public.windowsxp.help_and_support)