Re: Primary Network Logon in 9x
From: Steve Winograd [MVP] (winograd_at_pobox.com)
Date: 04/04/04
- Next message: Steve Winograd [MVP]: "Re: Don't have access to workgroup"
- Previous message: Quaoar: "Re: PCI Ethernet and PCI Wireless Card Not Cooperating"
- In reply to: Todd Hopfinger: "Primary Network Logon in 9x"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 03 Apr 2004 22:28:43 -0700
In article <17c2401c419b6$716abf60$a301280a@phx.gbl>, "Todd Hopfinger"
<anonymous@discussions.microsoft.com> wrote:
I answered the very same question in the Windows 98 networking group
when you asked it on March 30, Todd. In case you missed it, I'm
repeating it here. If you're not satisfied with the answer, please
say more, and I'll do my best to explain.
>What is the difference between 'Windows Logon'
>and 'Client for Microsoft Networks' with respect
>to 'Primary Network Logon'?
Good question!
>I understand that 'Client for Microsoft Networks' must be
>set as the 'Primary Network Logon' in order authenicate
>against a NT domain server.
Right.
> However, what is function
>of 'Client for Microsoft Networks' in a workgroup setting
In a workgroup all of the available logon types (Windows, Client for
Microsoft Networks, Microsoft Family) give access to all networking
functions.
Client for Microsoft Networks must be installed to enable a computer
to browse the network and access other computers, but it doesn't have
to be the primary network logon.
To enable password saving for DUN connections, either Client for
Microsoft Networks or Microsoft Family Logon must be installed. But
they don't need to be the primary network logon.
>- What workgroup machine is it authenicating to?
There's no authentication when a workgroup computer connects to the
network. You can enter any password, or no password, at the Microsoft
Networking logon prompt.
>- Does it avoid authenication and just cache the user
>name and password for later share access?
At logon, the system simply caches the user name and password. It
subsequently sends them to computers (Windows NT/2000/XP) that request
them to validate access to shared resources. If the other computer
doesn't recognize the user name and password as valid, Win9x comes
back with the dreaded "IPC$" prompt. There's no correct response to
the "IPC$" prompt.
>- Does it automatically unlock the local user account
>with the same user name?
There's nothing to unlock, because user accounts on Windows 9x don't
provide any type of security or access control.
Locally, the logged-in user name simply determines which user's
settings (desktop, favorites, etc) to use.
>Can anyone describe the network logon process in detail?
I'm not sure that anyone, even at Microsoft, can. :-)
Thankfully, Windows XP did away with the different logon types and the
complexity and confusion that they cause.
-- Best Wishes, Steve Winograd, MS-MVP (Windows Networking) Please post any reply as a follow-up message in the news group for everyone to see. I'm sorry, but I don't answer questions addressed directly to me in E-mail or news groups. Microsoft Most Valuable Professional Program http://mvp.support.microsoft.com
- Next message: Steve Winograd [MVP]: "Re: Don't have access to workgroup"
- Previous message: Quaoar: "Re: PCI Ethernet and PCI Wireless Card Not Cooperating"
- In reply to: Todd Hopfinger: "Primary Network Logon in 9x"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
