Rundown on sharing between two xp pro computers

[Guest]

Archived from groups: microsoft.public.windowsxp.general,microsoft.public.windowsxp.configuration_manage,microsoft.public.windowsxp.security_admin (More info?)

Group,
Everytime I install winxp pro it seems I go round and round for a while
before I get sharing to work like I want it to.

I want:
Two computers running xp pro to share everything. No passwords, no bs.
Right clicking C:\ and then sharing I set `everyone' to have full
control in the permissions. (On both machines)

In the Folder Options/view/ disable `simple sharing'.
Finally at C:\sharing ..\ tab =>security... again give full control to
`everyone'.

Both machines have the above settings. Both machines have been
rebooted after making these settings.

Machine A: When attempting to add Machine B in network places:
I am prompted for a uid and password. (none have ever been set)
Machine B: Has no problem finding machineA in network places.
Full sharing works in that direction.

Both machines are running the same patched and up to date OS. installed
from the same CD and updated thru windows update.

No SP2 is installed on either.

Can someone coach me as to why one direction works but not the other?

 

[Guest]

Archived from groups: microsoft.public.windowsxp.general,microsoft.public.windowsxp.configuration_manage,microsoft.public.windowsxp.security_admin (More info?)

Harry Putnam wrote:
> Group,
> Everytime I install winxp pro it seems I go round and round for a
> while before I get sharing to work like I want it to.
>
> I want:
> Two computers running xp pro to share everything. No passwords, no
> bs. Right clicking C:\ and then sharing I set `everyone' to have full
> control in the permissions. (On both machines)
>
> In the Folder Options/view/ disable `simple sharing'.
> Finally at C:\sharing ..\ tab =>security... again give full control to
> `everyone'.
>
> Both machines have the above settings. Both machines have been
> rebooted after making these settings.
>
> Machine A: When attempting to add Machine B in network places:
> I am prompted for a uid and password. (none have ever been set)
> Machine B: Has no problem finding machineA in network places.
> Full sharing works in that direction.
>
> Both machines are running the same patched and up to date OS.
> installed from the same CD and updated thru windows update.
>
> No SP2 is installed on either.
>
> Can someone coach me as to why one direction works but not the other?

In a workgroup, you should set up each computer to include the identical
username/password used for any other computer that needs to connect to it.
Have you done that?

 

[Guest]

Archived from groups: microsoft.public.windowsxp.general,microsoft.public.windowsxp.configuration_manage,microsoft.public.windowsxp.security_admin (More info?)

"Lanwench [MVP - Exchange]" <lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> writes:

>> Can someone coach me as to why one direction works but not the other?
>
> In a workgroup, you should set up each computer to include the identical
> username/password used for any other computer that needs to connect to it.
> Have you done that?

If you mean each machine has to have the same `owner' or administrator
then maybe not. But I have never done that. And have had machines
that could transfer files between without problems.

I've used no passwords so far. And again, I have had that working
before too. With winxp (this same cd version)

One machine has User Harry Putnam as `owner' or administrator, the
other ended up with `Harry' some how. But surely it isn't required
that every machine have the same user for them to be able to share
files?

Isn't it possible to set permissions in such a way that anyone can
connect thru the lan. IF not then what is the meaning of such things
as allowing full control that one sees on the share dialog?

 

[Guest]

Archived from groups: microsoft.public.windowsxp.general,microsoft.public.windowsxp.configuration_manage,microsoft.public.windowsxp.security_admin (More info?)

Harry Putnam <reader@newsguy.com> writes:

> "Lanwench [MVP - Exchange]" <lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> writes:
>
>>> Can someone coach me as to why one direction works but not the other?

Lanwench wrote:
>> In a workgroup, you should set up each computer to include the identical
>> username/password used for any other computer that needs to connect to it.
>> Have you done that?

[...]

Harry replied:
>
> Isn't it possible to set permissions in such a way that anyone can
> connect thru the lan. IF not then what is the meaning of such things
> as allowing full control that one sees on the share dialog?

Rereading your post, I think I got your meaning a little better.
I went back and created user `soandso' on each machine with same
password.

Now all file actions work in either direction. Many thanks.

But again, is that just a work around or is it supposed to be possible
to do that without creating special users?

 

[Guest]

Archived from groups: microsoft.public.windowsxp.general,microsoft.public.windowsxp.configuration_manage,microsoft.public.windowsxp.security_admin (More info?)

Harry Putnam wrote:
> Harry Putnam <reader@newsguy.com> writes:
>
>> "Lanwench [MVP - Exchange]"
>> <lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> writes:
>>
>>>> Can someone coach me as to why one direction works but not the
>>>> other?
>
> Lanwench wrote:
>>> In a workgroup, you should set up each computer to include the
>>> identical username/password used for any other computer that needs
>>> to connect to it. Have you done that?
>
> [...]
>
> Harry replied:
>>
>> Isn't it possible to set permissions in such a way that anyone can
>> connect thru the lan. IF not then what is the meaning of such things
>> as allowing full control that one sees on the share dialog?
>
> Rereading your post, I think I got your meaning a little better.
> I went back and created user `soandso' on each machine with same
> password.
>
> Now all file actions work in either direction. Many thanks.

Glad it worked.

>
> But again, is that just a work around or is it supposed to be possible
> to do that without creating special users?

Unless you have a domain, or enable guest, then you need to do this.
Workgroups don't scale well - anything more than a handful, and I think it's
time for a domain & a server ;-)

 

[george]

Archived from groups: microsoft.public.windowsxp.general,microsoft.public.windowsxp.configuration_manage,microsoft.public.windowsxp.security_admin (More info?)

"Harry Putnam" <reader@newsguy.com> wrote in message
news:m3mzzl4uv8.fsf@newsguy.com...
> Harry Putnam <reader@newsguy.com> writes:
>
>> "Lanwench [MVP - Exchange]"
>> <lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> writes:
>>
>>>> Can someone coach me as to why one direction works but not the other?
>
> Lanwench wrote:
>>> In a workgroup, you should set up each computer to include the identical
>>> username/password used for any other computer that needs to connect to
>>> it.
>>> Have you done that?
>
> [...]
>
> Harry replied:
>>
>> Isn't it possible to set permissions in such a way that anyone can
>> connect thru the lan. IF not then what is the meaning of such things
>> as allowing full control that one sees on the share dialog?
>
> Rereading your post, I think I got your meaning a little better.
> I went back and created user `soandso' on each machine with same
> password.
>
> Now all file actions work in either direction. Many thanks.
>
> But again, is that just a work around or is it supposed to be possible
> to do that without creating special users?

(Short answer) This is the behaviour by design.
(Longer) Workgroups do not have any way of centralizing username/password
information, which means you have to make sure each machine 'knows' the
other machine's usernames/passwords in order to 'recognize' a user coming in
over the network as someone 'known' (be it from it's own definitions held
locally)
This is one of the reasons why workgroups quickly become an administrators
nightmare if there are more then just a few machines/users in it.
eg. one user decides (without telling anyone) to change his password because
the old one is compromized.
Ooops, sharing access is out the window.....

Now there is a 'quick fix' to get this working without a lot of hassle and
that is to enable the guest account and assign the required permissions
(file and share level) to the guests group. The OS first tries to validate
with the userid/password passed upon accessattempt and failing that, checks
if the guest account is enabled and will then grant access to the guest
account. Real user does not know he basically is 'only' guest on the other
system, so will only be able to access anything where the guest account also
has permission. (And obviously Everyone includes Guest, duh.)

hth

george