R
reader
I have a lingering problem on one Winxp home machuine on a lan with
several XP pro machines and one XP home. (also a linux samba server).
All have good connectivity thanks to recent thread with Chuck and many
visits to Pchuck.net.
The one machine remains inaccessable from the others. (except the
linux machine which has never had that problem).
These are some of the network settings:
netBT over tcp is turned on. C and D drive are setup as shares with
names. \\bjp\bjp-c \\bjp\bjp-d and are set to allow network access and
file manipulation.
All machines on the lan have common users `harry' and `reader'. Both
are admin accounts and have full access set in file sharing of above
shares.
There appears to be no `simple file sharing' switch to turn off on
WinXP home.
===================================================================
One clue is that from the subject machine (bjp). Attempting to access
any other winxp machine invokes a password exchange, and then works as
expected.
No other xp machine requires passwords when accessing a share on another
lan host.
So to summarize: Any attempt to access host bjp from any other winxp
machine on the lan receives the `no access' error.
When accessing remote local lan hosts from bjp, a password exchange is
invoked and then access is allowed.
several XP pro machines and one XP home. (also a linux samba server).
All have good connectivity thanks to recent thread with Chuck and many
visits to Pchuck.net.
The one machine remains inaccessable from the others. (except the
linux machine which has never had that problem).
These are some of the network settings:
netBT over tcp is turned on. C and D drive are setup as shares with
names. \\bjp\bjp-c \\bjp\bjp-d and are set to allow network access and
file manipulation.
All machines on the lan have common users `harry' and `reader'. Both
are admin accounts and have full access set in file sharing of above
shares.
There appears to be no `simple file sharing' switch to turn off on
WinXP home.
===================================================================
One clue is that from the subject machine (bjp). Attempting to access
any other winxp machine invokes a password exchange, and then works as
expected.
No other xp machine requires passwords when accessing a share on another
lan host.
So to summarize: Any attempt to access host bjp from any other winxp
machine on the lan receives the `no access' error.
When accessing remote local lan hosts from bjp, a password exchange is
invoked and then access is allowed.