Thanks this has answered the question. I had assumed this was much more
complicated.
Steve
-----Original Message-----
From: Danilo Almeida [mailto:xxxxx@MIT.EDU]
Sent: 03 November 2000 15:20
To: NT Developers Interest List
Subject: [ntdev] RE: [NTDEV] Security on SharesJust to expand on what Bill is saying:
Based on my undertaning, the “guest” account needs to be
enabled with a
blank password. This is because the network client will try
“guest” with a
blank password after trying the current user with the
password the current
user used to log into the local machine.
- Danilo
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com]On Behalf Of Bill Wandel
> Sent: Friday, November 03, 2000 8:03 AM
> To: NT Developers Interest List
> Subject: [ntdev] RE: [NTDEV] Security on Shares
>
>
> Make sure that the guest user account is enabled.
>
> Bill Wandel
>
> -----Original Message-----
> From: Steve Hayward [SMTP:xxxxx@avantis.co.uk]
> Sent: Friday, November 03, 2000 6:02 AM
> To: NT Developers Interest List
> Subject: [ntdev] RE: [NTDEV] Security on Shares
>
> What I am looking for is ‘Anonymous’ access. That is to say
the NT4.0
> machine being accessed does not validate the user accessing
shares in
> anyway. ie the accessing user does not exist in any of the machines
> user/group lists.
>
> Steve
You are currently subscribed to ntdev as: xxxxx@avantis.co.uk
To unsubscribe send a blank email to $subst(‘Email.Unsub’)