WinXP laptop, simple-style login conn to Win2000 share, error

From: brad h (bhegrat@hotmail.com)
Date: 09/09/02 

From: "brad h" <bhegrat@hotmail.com>
Date: Mon, 9 Sep 2002 12:20:01 -0700

Alright. First of all, the "PushButton" style logon is
typically used for local machine access/workgroup access
only. You cannot use that way of authentication in a
Domain.

So, to simplify matters, add all machines to the domain.
You do this so you don't have a million different netbios
names (workgroup names, domain names, domain accounts,
local machine accounts) to keep track of...

Next, if you can't browse the network from the XP machines
at all, be sure of the following:
1. TCP/IP is installed with NetBIOS enabled.
2. The TCP/IP NetBIOS Helper Service is started.
3. The Workstation service is started.
4. The Computer Browsers service is started.

Ok. Now we are at the point of configuring the server.
Make sure of the following:
1. Server service is started
2. IF all of the XP laptops are added to the domain,
ensure that the Permissions for your shares are set to the
domain accounts in question.

NOW. Windows XP attempts to login into remote assets with
the local account information. You are attempting to use
local account names that "match" to a DC account in order
to access a share. To set this up for the end user's
convenience, add all machines to the domain (thus losing
the "pushbutton login") and configure the Laptops to auto
login with the acmeuser DOMAIN account. Then configure
your secure share to be public (if it isn't already - you
can't browse to a hidden share) and set the SHARE
permissions to EVERYONE but the FILE Permissions to just
the acmeboss account.

Hope this helps...

Brad

>-----Original Message-----
>I'm trying to understand this behavior on WinXP
connecting to a Windows 2000
>fileshare on a test network I created.
>
>Preconditions:
>1) I made a single Win2000 domain user, 'acmeuser' which
gives access to
>public fileshares hosted on the Win2000 domain
controller 'Server1'.
>
>2) My WinXP laptop is using the 'pushbutton' style of
login as user 'Myname'
>with a password, as everyone seems to want to do these
days. Users are
>lulled into complacency by no-typing logins, but I've
still got to
>understand how this works.
>
>3) The laptop connects to this share as user 'acmeuser'
and 'password', I
>set it to remember that password, which I presume tries
to apply it to every
>connection to Server1. All the public shares are
accessible from that single
>login, which is what I wanted.
>
>4) I now created a share on server 1 'Secure Folder'
which only grants
>permission (full) to a separate user 'acmeboss'.
>
>Symptoms:
>A) I can't browse to that share on the WinXP laptop and
input a new username
>password. I only get an error dialog stating 'you don't
have permission to
>access...' I would like to know how to force a login
prompt here, without
>making public shares require a (re)login for
the 'acmeuser' trivial login it
>is expected to use.
>
>B) I can't map that secure share to a network letter
because (and this is
>the weird part) the dialog filled out as follows:
>Drive: S:
>Folder: \\Server1\Secure Folder (typed in, not browse-
filled)
>Reconnect at Logon: yes
>(different) Username: ACMECORP\acmeboss,
password: 'secured'
>(click finish)
>The network folder specified is currently mapped using a
different user name
>and password. To connect using a different user name and
password, first
>disconnect any existing mappings to this network share.
>
>I have made sure that there is no connection to this
share. In fact I've
>disconnected all shares prior to the above step. I can
only assume that the
>WinXP laptop is trying to use that acmeuser login against
the secured
>folder.
>
>Any advice would be greatly appreciated.
>
>
>
>
>.
>