D
Dave Shaw
Being relatively new to networking problems, I have
several related networking questions related to my XP
(SP1) laptop connected to a LAN in our office. We all
work under a common workgroup name, not a domain name. We
experimented with some of our options regarding this
configuration and got stuck in several areas, as described
below.
If I sit at one of the Win 2000 systems on the network
and try to drill down into my laptop (as one of the list
of machines in our workgroup), I get a popup asking me
to "Enter network password". (We thought setting up a
user account and password on the laptop would work, but
it didn't)
QUESTION #1: How do I set up this "network
password" on my laptop?
When we first did this, nothing was shared on the laptop,
and thinking that might have had an effect, we set out to
share the Shared Documents folder. Accessing the "Shared
Documents Properties" for this folder revealed the
text "As a security measure, Windows has disabled remote
access to this computer." and suggests running the
network Setup Wizard. However, the popup also states "If
you understand the security risks." you can share files
without running the wizard. We chose that option,
received the "hand" under the folder, and were then able
to see it from the Win 2000 system on the LAN.
Unfortunately, the sharing was then available to anyone,
with no authentication required.
QUESTION #2: Is there any way to password protect
a shared folder in this configuration?
Thinking we then wanted to back out of this (unsecure)
sharing option, we tried to determine what exactly XP had
done when we enabled sharing. Unsharing the folder did
not re-engage authentication into my laptop. In addition,
trying to share any other folder no longer gave us
the "As a security measure." message, etc., implying XP
has done something global to the machine configuration.
QUESTION #3: What did XP do to enable sharing,
and how can it be undone?
We finally ran System Restore on a previous restore point
and that brought us back to where we started. Doesn't
seem like the optimal way to do things...
Thanks for any info explaining any of this. Please
respond to this newsgroup.
several related networking questions related to my XP
(SP1) laptop connected to a LAN in our office. We all
work under a common workgroup name, not a domain name. We
experimented with some of our options regarding this
configuration and got stuck in several areas, as described
below.
If I sit at one of the Win 2000 systems on the network
and try to drill down into my laptop (as one of the list
of machines in our workgroup), I get a popup asking me
to "Enter network password". (We thought setting up a
user account and password on the laptop would work, but
it didn't)
QUESTION #1: How do I set up this "network
password" on my laptop?
When we first did this, nothing was shared on the laptop,
and thinking that might have had an effect, we set out to
share the Shared Documents folder. Accessing the "Shared
Documents Properties" for this folder revealed the
text "As a security measure, Windows has disabled remote
access to this computer." and suggests running the
network Setup Wizard. However, the popup also states "If
you understand the security risks." you can share files
without running the wizard. We chose that option,
received the "hand" under the folder, and were then able
to see it from the Win 2000 system on the LAN.
Unfortunately, the sharing was then available to anyone,
with no authentication required.
QUESTION #2: Is there any way to password protect
a shared folder in this configuration?
Thinking we then wanted to back out of this (unsecure)
sharing option, we tried to determine what exactly XP had
done when we enabled sharing. Unsharing the folder did
not re-engage authentication into my laptop. In addition,
trying to share any other folder no longer gave us
the "As a security measure." message, etc., implying XP
has done something global to the machine configuration.
QUESTION #3: What did XP do to enable sharing,
and how can it be undone?
We finally ran System Restore on a previous restore point
and that brought us back to where we started. Doesn't
seem like the optimal way to do things...
Thanks for any info explaining any of this. Please
respond to this newsgroup.