Secure Shared Network Folder

[Guest]

Is it possible to create a secure shared network folder in a network that is
/not/ on a domain? In 98 you could simply put in a password for the folder,
and connecting computers would have to use that password to access said
folder. This feature has been removed in XP for only God knows what reason,
and every attempt I have tried at creating some form of security for a shared
folder on a network has failed.

The closest I have come to success is by this method:

I created a new account on the computer hosting the shared folder.
I next set the permissions of the shared folder to allow access only from
the new user.
I next used "Map network drive" on the other computers, and told it to use a
different username and password. I made /sure/ I had checked the "Reconnect
at Logon" box, and everything seemed to be working fine. I was able to access
the folder through the mapped drive, but not through the network. Good,
great.. it worked, though in a very rediculous, roundabout way.

I then rebooted the computer after installing something, and when I got back
in, the mapped drive was still there. I double clicked it, and, to my great
surprise, it told me I needed to enter a password. I spent thirty minutes
searching every dialog box I could find, as well as googling around, trying
to locate a simple little box that says "Remember password". Alas, I was
unable to locate said box and, therefore, was unable to create a secure
network folder that was persistant and useable without any input from the
user. I had to abandon the attempt because this was completely unacceptable.

So, is it possible to create a shared folder that is secure, while remaining
persistantly useable without any input from the user? This folder is not on a
computer that is part of a domain.

Thank you.

-Sastira

 

[Malke]

Is it possible to create a secure shared network folder in a network
that is /not/ on a domain? In 98 you could simply put in a password
for the folder, and connecting computers would have to use that
password to access said folder. This feature has been removed in XP
for only God knows what reason, and every attempt I have tried at
creating some form of security for a shared folder on a network has
failed.

The closest I have come to success is by this method:

I created a new account on the computer hosting the shared folder.
I next set the permissions of the shared folder to allow access only
from the new user.
I next used "Map network drive" on the other computers, and told it to
use a different username and password. I made /sure/ I had checked the
"Reconnect at Logon" box, and everything seemed to be working fine. I
was able to access the folder through the mapped drive, but not
through the network. Good, great.. it worked, though in a very
rediculous, roundabout way.

I then rebooted the computer after installing something, and when I
got back in, the mapped drive was still there. I double clicked it,
and, to my great surprise, it told me I needed to enter a password. I
spent thirty minutes searching every dialog box I could find, as well
as googling around, trying to locate a simple little box that says
"Remember password". Alas, I was unable to locate said box and,
therefore, was unable to create a secure network folder that was
persistant and useable without any input from the user. I had to
abandon the attempt because this was completely unacceptable.

So, is it possible to create a shared folder that is secure, while
remaining persistantly useable without any input from the user? This
folder is not on a computer that is part of a domain.

It depends on whether you have Pro or Home Edition. With Pro, create a
new user group and add the users who are allowed to access that folder.
Make sure you include yourself! Then set the read/write permissions on
that folder/files for only the new user group. If you have Home
Edition, look for third-party software to do what you want such as
Winzip.

Malke

 

[Steve Winograd [MVP]]

Is it possible to create a secure shared network folder in a network that is
/not/ on a domain? In 98 you could simply put in a password for the folder,
and connecting computers would have to use that password to access said
folder. This feature has been removed in XP for only God knows what reason,
and every attempt I have tried at creating some form of security for a shared
folder on a network has failed.

The closest I have come to success is by this method:

I created a new account on the computer hosting the shared folder.
I next set the permissions of the shared folder to allow access only from
the new user.
I next used "Map network drive" on the other computers, and told it to use a
different username and password. I made /sure/ I had checked the "Reconnect
at Logon" box, and everything seemed to be working fine. I was able to access
the folder through the mapped drive, but not through the network. Good,
great.. it worked, though in a very rediculous, roundabout way.

I then rebooted the computer after installing something, and when I got back
in, the mapped drive was still there. I double clicked it, and, to my great
surprise, it told me I needed to enter a password. I spent thirty minutes
searching every dialog box I could find, as well as googling around, trying
to locate a simple little box that says "Remember password". Alas, I was
unable to locate said box and, therefore, was unable to create a secure
network folder that was persistant and useable without any input from the
user. I had to abandon the attempt because this was completely unacceptable.

So, is it possible to create a shared folder that is secure, while remaining
persistantly useable without any input from the user? This folder is not on a
computer that is part of a domain.

Thank you.

-Sastira

Yes, it's possible, but it's not easy. I've had conversations with
people at Microsoft about permissions on shared folders, and I don't
think that they understand the needs of users with workgroups.

Windows XP is based on Windows NT/2000, not on 95/98/Me. The NT/2000
branch has never had passwords for shared folders. It uses file
permissions, which are easy to set up and use in a domain and hard to
set up and use in a workgroup.

There should be no need to map a network drive or enter a password to
access the shared folder from other computers.

You say that you set permissions on the shared folder, so I assume
that the computer has Windows XP Professional. Windows XP Home
Edition can't set folder permissions.

Here's what I suggest:

1. Don't use mapped network drives.

2. Determine which user(s) should have access to the shared folder.

3. For each such user:

a. Create a user account on the main computer and on every other
computer that will use that account.

b. Specify the same user name and non-empty password
for the account on each computer.

4. If all of the users defined on the main computer should have access
to the folder, make sure that the "Everyone" group has permission.

5. If there are users defined on the main computer who shouldn't have
access to the folder:

a. Add each desired user to the permissions for the folder.

b. Remove permission from the "Everyone" group.

This article should help:

Windows XP Professional File Sharing
http://www.practicallynetworked.com/sharing/xp_filesharing/index.htm
--
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

 

[Guest]

Thank you VERY MUCH Steve!!!

I will definately give this method a try when I'm back at the client's
office next week!

I had actually considered something like what you said, but had been
considering it in the realm of mapping a network drive where it wouldn't have
worked.

Thank you again, Steve!

-Sastira

 

[Steve Winograd [MVP]]

Thank you VERY MUCH Steve!!!

I will definately give this method a try when I'm back at the client's
office next week!

I had actually considered something like what you said, but had been
considering it in the realm of mapping a network drive where it wouldn't have
worked.

Thank you again, Steve!

-Sastira

You're welcome, Sastira. Please reply to this message in the news
group next week and let everyone know how it works.
--
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

 

[Guest]

You're welcome, Sastira. Please reply to this message in the news
group next week and let everyone know how it works.
--
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

As requested, here is my update:

It worked wonderfully!!

Thank you, once again, for your generous donation of advice and time!!

-Sastira

 

[Steve Winograd [MVP]]

As requested, here is my update:

It worked wonderfully!!

Thank you, once again, for your generous donation of advice and time!!

-Sastira

You're welcome! I'm glad that my suggestions helped you set up your
network the way that you want. Thanks for posting the result.
--
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