Thanks for your reply Chuck.
I have done your suggestions and it still doesn't allow the XP Home computer to authenticate as the user. It only sends "Guest" as user name. I'm beginning to think this is just the way XP Home operates and it's another limitation of XP Home. Someone else said I could get around this by using this command:
NET USE x: \\xppro\share [password|*] /USER:username
The shared folder is for Quickbooks and the user needs it to be simple. I wonder if a drive could be mapped or if this command might have to be used in a log in script. Any ideas?
Thanks,
Steve Smith
Chuck wrote
>Thanks for your reply Chuck.
>
[quoted text clipped - 5 lines]
>Thanks,
>Steve Smith
Steve,
Then that's it. The reason why you're getting the popup (specifying Guest as
the account) is that the Guest account is not enabled on the Pro system (or
password not matching). If enabled, and your password matches the assigned
password, it should connect without the popup.
Connecting When Advanced File Sharing is Being Used
In order to connect to a Windows XP Professional shared folder when advanced
file sharing is being used, you must be:
" Using a set of credentials that Windows XP can validate (it is either a
local computer account or a domain account) and has been granted the Read,
Change, or Full Control access type either explicitly (the account name) or
though group membership, as specified in the permissions of the shared folder.
" Using a set of credentials that Windows XP cannot validate, and either
the domain Guest account or the local Guest account has been enabled and has
been granted the Read, Change, or Full Control access type either explicitly
(the Guest account name) or though group membership, as specified in the
permissions of the shared folder.
IOW, if "the local Guest account has been enabled", it acts as a fallback to
provide access to computers authenticating with the Guest account, when a
non-Guest account is preferred for authentication.
With XP Pro and Advanced File Sharing, you can authenticate using the Guest
account, or a non-Guest account, at your choice, for incoming file sharing. And
you can use Advanced File Sharing, and authenticate by non-Guest accounts with
computers running AFS also, or authenticate by the Guest account with computers
using SFS, for outgoing file sharing.
With XP Home, that uses only the Guest account for incoming sharing, you're
stuck with using the Guest account for outgoing sharing also. That actually
makes sense. In a retarded way.
I'll look forward to hearing what happens when you override the Guest account
authentication (from XP Home) with the "Net Use ..." command. Please do let us
know.
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
Steve Smith - 01 Jul 2004 00:50 GMT
> .. The reason why you're getting the popup (specifying Guest as
> the account) is that the Guest account is not enabled on the Pro system (or
> password not matching). If enabled, and your password matches the assigned
> password, it should connect without the popup.
Yes, I disabled the Guest account on the Pro system for security reasons. I'd like to keep it disabled if that's possible while still allows access from XP Home.
>...you're stuck with using the Guest account for outgoing sharing....
That's the answer I've been looking for. So, unless I can use the Net Use ... command, XP sends only Guest as the user name, right? So, if the Net Use ... command doesn't work iwht XP Home, I'll have to enable the Guest account on the Pro computer. This won't be too bad because I did read that you can setup a password for the Guest account. You type "net user guest password, reboot and any attempt to log on as Guest will require a password. However, I'd rather diable the Guest account and use the Net Use ... command as long as the connection is persistent. I don't want the user to have to use this command each time they want to access the share.
> ....I'll look forward to hearing what happens when you override the Guest account
> authentication (from XP Home) with the "Net Use ..." command. Please do let us
> know.
I will post back what I find out. It will be tomorrow before I'll be able to test this.
Steve Smith