Re: Any Way Around the New Default Behavior of XP SP2 + NTLM "Failback"
- From: Chuck <none@xxxxxxxxxxx>
- Date: Fri, 03 Mar 2006 08:06:15 -0800
On 2 Mar 2006 21:59:37 -0800, "artemidorus" <jason@xxxxxxxxxxx> wrote:
Chuck wrote:
On 27 Feb 2006 19:15:32 -0800, "artemidorus" <jason@xxxxxxxxxxx> wrote:
artemidorus wrote:
seriously? there is no workaround for this?
Back again to see if I can't coax some kind of definitive answer out of
you folks...
It would appear that nobody has an answer for you, based upon your question.
Maybe you need to try and state your question based upon reasonable
expectations, and we can try and work with you.
So, what do you need to do with your network? Be realistic (flexible) now.
--
Cheers,
Chuck, MS-MVP [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.
Curses, I don't know how I didn't see this response, so, my apologies
for turning it around so slowly...
The issue is that I run XP as virtual machine under my linux-powered
laptop... most of the time this works great, except when I take my
machine off of my home network (where my domain controllers, etc. live)
or when I use the VPN connection (under XP). The latter presents
problems because the connection between the XP box and the network is
routed (under linux bridged connections on wireless network cards don't
work under VMware...), making those hosts unreachable with the IPSEC
tunnel up and running... The problems this scenario presents is that I
can't connect to samba shares on my laptop from the virtual machine
under these specific conditions... I have to think that this has
something to do with the fact that the xp system is unable to verify
credentials in the absence of a domain controller. Prior to XP SP2, the
system would "downshift" to NTLM and be good to go... After SP2, this
behavior is not preserved... Your additional thoughts are
appreciated... Thank you. :o)
Why not try and define this perceived "downshift to NTLM"? If a domain
controller is unavailable, a domain member computer should be able to
authenticate using cached credentials (if available). Barring that, you have to
login with a local account. I don't know that SP2 changed any of that
behaviour.
Is it possible that the security changes in SP2 interferes with some secondary
behaviour that you're describing as the "downshift to NTLM"?
--
Cheers,
Chuck, MS-MVP [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.
.
- References:
- Re: Any Way Around the New Default Behavior of XP SP2 + NTLM "Failback"
- From: artemidorus
- Re: Any Way Around the New Default Behavior of XP SP2 + NTLM "Failback"
- Prev by Date: Re: File sharing won't work
- Next by Date: Re: RPC failed while 2 PCs connected
- Previous by thread: Re: Any Way Around the New Default Behavior of XP SP2 + NTLM "Failback"
- Next by thread: Re: Any Way Around the New Default Behavior of XP SP2 + NTLM "Failback"
- Index(es):
Relevant Pages
|
