How share program files folder on LAN?

[jtsnow]

On my home LAN I cannot see the contents of the Program Files Folder on
other PCs.
On those PCs the entired "C" drive is set to share, yet that folder will
still not allow access.
When attempting to set share permission on that particular folder, the
option is shaded out and not available to make as share.

Is there a way to set the sharing for ALL folders on the C drive? I am the
admin on all PCs.

thanks for any tips

 

[Malke]

On my home LAN I cannot see the contents of the Program Files Folder
on other PCs.
On those PCs the entired "C" drive is set to share, yet that folder
will still not allow access.
When attempting to set share permission on that particular folder, the
option is shaded out and not available to make as share.

Is there a way to set the sharing for ALL folders on the C drive? I
am the admin on all PCs.

thanks for any tips

You apparently are running XP Home on those machines. You are not able
to share the Windows and Program Files folders on XP Home. If this is
crucial that you share those directories, upgrade to XP Pro and disable
Simple Sharing. You are not able to disable Simple Sharing on XP Home.

Malke

 

[Steve Winograd [MVP]]

On my home LAN I cannot see the contents of the Program Files Folder on
other PCs.
On those PCs the entired "C" drive is set to share, yet that folder will
still not allow access.
When attempting to set share permission on that particular folder, the
option is shaded out and not available to make as share.

Is there a way to set the sharing for ALL folders on the C drive? I am the
admin on all PCs.

thanks for any tips

I'm sorry, but that's how Windows XP works by default when it's
installed on an NTFS disk partition. It blocks access to the Program
Files and Windows folders and to individual users' folders within
Documents and Settings.

You can share subfolders within those folders, e.g. you can share
"C:\Program Files\Outlook Express" or "C:\Documents and
Settings\Username\Desktop" and access that folder from another
computer on the network.

If you have Windows XP Professional, you can disable simple file
sharing, which removes those restrictions:

1. Open My Computer and click Tools | Folder Options | View.
2. Scroll to the end of the advanced settings.
3. Un-check "Use simple file sharing (recommended)".

If you have Windows XP Home Edition, there's no easy solution. The
safest thing is to share individual subfolders, as mentioned above.

You can re-install the operating system on a FAT or FAT32 disk
partition -- those disk formats don't have any sharing restrictions.
However, that would lose the benefits of NTFS, which is more reliable
and efficient and can use larger disks. You'd also need to re-install
all of your applications.

I've heard of two possible solutions for XP Home Edition on an NTFS
disk partition, but:

1. They're un-supported, un-documented, and un-tested by Microsoft.
2. There's no guarantee that they'll work.
3. They might cause data loss or corruption.

I haven't tried them, and I don't know whether they're safe. If you
want to try them, at your own risk:

1. Back up your important data first so that you can restore it in
case of problems.

2. Run System Restore to create a restore point that you can go back
to in case of problems.

Here they are:

1. Start Windows XP in "Safe Mode with Networking" (which temporarily
disables "Simple File Sharing"), share the desired folder(s), set the
permissions, and reboot normally, or:

2. Follow the procedure shown here:

http://www.dougknox.com/xp/tips/xp_home_sectab.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

 

[jtsnow]

nice explanation. Maybe the individual folder sharing will work.
thanks

 

[Don Dunlap]

I'm sorry, but that's how Windows XP works by default when it's
installed on an NTFS disk partition. It blocks access to the Program
Files and Windows folders and to individual users' folders within
Documents and Settings.

You can share subfolders within those folders, e.g. you can share
"C:\Program Files\Outlook Express" or "C:\Documents and
Settings\Username\Desktop" and access that folder from another
computer on the network.

If you have Windows XP Professional, you can disable simple file
sharing, which removes those restrictions:

1. Open My Computer and click Tools | Folder Options | View.
2. Scroll to the end of the advanced settings.
3. Un-check "Use simple file sharing (recommended)".

If you have Windows XP Home Edition, there's no easy solution. The
safest thing is to share individual subfolders, as mentioned above.

You can re-install the operating system on a FAT or FAT32 disk
partition -- those disk formats don't have any sharing restrictions.
However, that would lose the benefits of NTFS, which is more reliable
and efficient and can use larger disks. You'd also need to re-install
all of your applications.

I've heard of two possible solutions for XP Home Edition on an NTFS
disk partition, but:

1. They're un-supported, un-documented, and un-tested by Microsoft.
2. There's no guarantee that they'll work.
3. They might cause data loss or corruption.

I haven't tried them, and I don't know whether they're safe. If you
want to try them, at your own risk:

1. Back up your important data first so that you can restore it in
case of problems.

2. Run System Restore to create a restore point that you can go back
to in case of problems.

Here they are:

1. Start Windows XP in "Safe Mode with Networking" (which temporarily
disables "Simple File Sharing"), share the desired folder(s), set the
permissions, and reboot normally, or:

2. Follow the procedure shown here:

http://www.dougknox.com/xp/tips/xp_home_sectab.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

I am having the same problem as jtsnow and I have XP PRO installed on both
computers. I still cannot access the Program Files or Windows directories.
I have unchecked "Simple File Sharing" on both computers and in Permissions,
I have allowed Everyone full control. I still cannot access the other
computer's Program Files or Windows directory.

Don Dunlap

 

[Chuck]

I am having the same problem as jtsnow and I have XP PRO installed on both
computers. I still cannot access the Program Files or Windows directories.
I have unchecked "Simple File Sharing" on both computers and in Permissions,
I have allowed Everyone full control. I still cannot access the other
computer's Program Files or Windows directory.

Don Dunlap

Don,

Are you using an administrative userid from both computers, and have you enabled
non-Guest authentication?

On XP Pro with SFS disabled, check the Local Security Policies (Control Panel -
Administrative Tools). Under Local Policies - Security Options, look at
"Network access: Sharing and security model", and ensure it's set to "Classic -
local users authenticate as themselves".

On XP Pro with SFS disabled, if you set the above Local Security Policy to
"Classic", setup and use a common non-Guest account on all computers. Whichever
account is used, give it an identical, non-blank password on all computers.

On XP Pro, check your Local Security Policy (Control Panel - Administrative
Tools) - User Rights Assignment, look at "Access this computer from the
network", and make sure that Everyone is in this list.

Do any of the computers have a software firewall (ICF / WF, or third party)? If
so, you need to configure them for file sharing. Firewall configurations are a
very common cause of (network) browser, and file sharing, problems.

--
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
My email is AT DOT
actual address pchuck sonic net.

 

[Don Dunlap]

On Mon, 17 Jan 2005 10:18:22 -0500, "Don Dunlap"
<[email protected]>
wrote:

SNIP


Don,

Are you using an administrative userid from both computers, and have you
enabled
non-Guest authentication?

On XP Pro with SFS disabled, check the Local Security Policies (Control
Panel -
Administrative Tools). Under Local Policies - Security Options, look at
"Network access: Sharing and security model", and ensure it's set to
"Classic -
local users authenticate as themselves".

On XP Pro with SFS disabled, if you set the above Local Security Policy to
"Classic", setup and use a common non-Guest account on all computers.
Whichever
account is used, give it an identical, non-blank password on all
computers.

On XP Pro, check your Local Security Policy (Control Panel -
Administrative
Tools) - User Rights Assignment, look at "Access this computer from the
network", and make sure that Everyone is in this list.

Do any of the computers have a software firewall (ICF / WF, or third
party)? If
so, you need to configure them for file sharing. Firewall configurations
are a
very common cause of (network) browser, and file sharing, problems.

--
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
My email is AT DOT
actual address pchuck sonic net.

Chuck,

That did it. I appreciate your help. I had everything set right except
that I had no password set on either computer. Since this is a home network
with only my wife and myself, I never thought it necessary to establish
passwords. It appears that setting the passwords did the trick. What I
don't understand is - I wasn't asked for the password at all, but after
establishing them, I was immediately able to access the Program Files and
Windows directory on each computer. Anyway, it worked and I thank you for
your help.

Don Dunlap

 

[Chuck]

Chuck,

That did it. I appreciate your help. I had everything set right except
that I had no password set on either computer. Since this is a home network
with only my wife and myself, I never thought it necessary to establish
passwords. It appears that setting the passwords did the trick. What I
don't understand is - I wasn't asked for the password at all, but after
establishing them, I was immediately able to access the Program Files and
Windows directory on each computer. Anyway, it worked and I thank you for
your help.

Don Dunlap

That's great news, Don. Thanks for the feedback.

--
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
My email is AT DOT
actual address pchuck sonic net.

 

[Steve Winograd [MVP]]

Chuck,

That did it. I appreciate your help. I had everything set right except
that I had no password set on either computer. Since this is a home network
with only my wife and myself, I never thought it necessary to establish
passwords. It appears that setting the passwords did the trick. What I
don't understand is - I wasn't asked for the password at all, but after
establishing them, I was immediately able to access the Program Files and
Windows directory on each computer. Anyway, it worked and I thank you for
your help.

Don Dunlap

By default, XP Pro denies networked access by users that don't have
passwords. To change that behavior:

1. Go to Control Panel | Performance and Maintenance | Administrative
Tools | Local Security Policy.

2. Expand Local Policies | Security Options.

3. Double-click "Accounts: Limit local account use of blank passwords
to console login only", which is enabled by default. Disable this
option and click OK.
--
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

 

[Don Dunlap]

By default, XP Pro denies networked access by users that don't have
passwords. To change that behavior:

1. Go to Control Panel | Performance and Maintenance | Administrative
Tools | Local Security Policy.

2. Expand Local Policies | Security Options.

3. Double-click "Accounts: Limit local account use of blank passwords
to console login only", which is enabled by default. Disable this
option and click OK.
--
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

Steve,

Thanks - I like that better now. I didn't want to have to enter a password
every time I started up and this cured it. I can see how it is a valuable
tool in certain environments, but at my home with only my wife and me, it is
an extra step that I can avoid.

With your help and with Chuck's, I now have the system set up the way that I
wanted. I would like to ask one more question. I currently have the
application that I want to run on both systems installed on both, but have
the database only on computer #1. This naturally avoids having two
different databases. I could only install the application on one computer
and link to it from the second one to execute it. This is much slower
though and I was wondering about the pitfalls with each setup.

Don Dunlap

 

[Steve Winograd [MVP]]

Steve,

Thanks - I like that better now. I didn't want to have to enter a password
every time I started up and this cured it. I can see how it is a valuable
tool in certain environments, but at my home with only my wife and me, it is
an extra step that I can avoid.

With your help and with Chuck's, I now have the system set up the way that I
wanted. I would like to ask one more question. I currently have the
application that I want to run on both systems installed on both, but have
the database only on computer #1. This naturally avoids having two
different databases. I could only install the application on one computer
and link to it from the second one to execute it. This is much slower
though and I was wondering about the pitfalls with each setup.

Don Dunlap

You're welcome, Don.

I'm sorry, but I don't understand your question about the application
that you've installed on both computers:

1. What are the different setups that you're asking about the
pitfalls?

2. What do you mean by "This is much slower" -- what is "This", and
what is it much slower than?

3. How did you "link to it from the second one to execute it"?

--
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

 

[Don Dunlap]

You're welcome, Don.

I'm sorry, but I don't understand your question about the application
that you've installed on both computers:

1. What are the different setups that you're asking about the
pitfalls?

2. What do you mean by "This is much slower" -- what is "This", and
what is it much slower than?

3. How did you "link to it from the second one to execute it"?

--
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

OK - let me see if I can explain it.
Option 1: Install the application on both computers.
When I do this, I am able to execute the program on either computer, but I
need to have only one data base that I am modifying. I accomplish this by
only having it on one of the computers and linking to it during program
executiion on the other computer. There should only be one program working
on the database at any one time, so there is no interference between the
two. I don't think that the application will support multiprogramming.

Option 2 Install the application on only one computer - say #1.

With this option, I would have to establish a link from computer #2 to the
program on computer #1 and start execution. This would involve transferring
the program to computer #1 each time it is executed, which is the slower
process. I tried this with Quicken once and while it worked, it was very
slow.

I believe option 1 is the best, but I am just wondering if there are any
problems with it that I don't see. Naturally the major problem is if both
computers are trying to access the database at the same time. Even if they
could do it, there would be no way of keeping track of who is doing what.

Did I make myself clear? After thinking it over, it appears that option 1
is the only way to go. I just have to ensure that the users don't both try
to access the database at the same time. I will be working with a business
that will start with only two computers, with one at the managers desk and
one for the secretary to enter data into the database. The manager wants to
access the database to ensure that everything is normal. She will just have
to make sure the secretary is not using the program.

Don

 

[Steve Winograd [MVP]]

[snip]
With your help and with Chuck's, I now have the system set up the way that
I
wanted. I would like to ask one more question. I currently have the
application that I want to run on both systems installed on both, but have
the database only on computer #1. This naturally avoids having two
different databases. I could only install the application on one computer
and link to it from the second one to execute it. This is much slower
though and I was wondering about the pitfalls with each setup.

Don Dunlap

You're welcome, Don.

I'm sorry, but I don't understand your question about the application
that you've installed on both computers:

1. What are the different setups that you're asking about the
pitfalls?

2. What do you mean by "This is much slower" -- what is "This", and
what is it much slower than?

3. How did you "link to it from the second one to execute it"?

OK - let me see if I can explain it.
Option 1: Install the application on both computers.
When I do this, I am able to execute the program on either computer, but I
need to have only one data base that I am modifying. I accomplish this by
only having it on one of the computers and linking to it during program
executiion on the other computer. There should only be one program working
on the database at any one time, so there is no interference between the
two. I don't think that the application will support multiprogramming.

Option 2 Install the application on only one computer - say #1.

With this option, I would have to establish a link from computer #2 to the
program on computer #1 and start execution. This would involve transferring
the program to computer #1 each time it is executed, which is the slower
process. I tried this with Quicken once and while it worked, it was very
slow.

I believe option 1 is the best, but I am just wondering if there are any
problems with it that I don't see. Naturally the major problem is if both
computers are trying to access the database at the same time. Even if they
could do it, there would be no way of keeping track of who is doing what.

Did I make myself clear? After thinking it over, it appears that option 1
is the only way to go. I just have to ensure that the users don't both try
to access the database at the same time. I will be working with a business
that will start with only two computers, with one at the managers desk and
one for the secretary to enter data into the database. The manager wants to
access the database to ensure that everything is normal. She will just have
to make sure the secretary is not using the program.

Don

Thanks for the explanation. I don't think that Option 2 will work.
Most programs must be installed on a computer in order to run on that
computer. The installation process copies necessary files and creates
registry entries that control the program's execution.
--
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

 

[Don Dunlap]

[snip]

Thanks for the explanation. I don't think that Option 2 will work.
Most programs must be installed on a computer in order to run on that
computer. The installation process copies necessary files and creates
registry entries that control the program's execution.
--
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

Thanks Steve. I think I have all the information to resolve my problem. I
appreciate the help and ypur patience.

Don Dunlap