Re: File Sharing Nightmares

Think we're getting somewhere here. I was always thinking along the lines
that the server was the issue. When i try to run some of the snap ins in
security settings I'm getting an error

"The Group Policy security settings that apply to this machine could not be
determined. The error returned when trying to retreive these settings from
the local security policy database (%windir%\security\database\secedit.sdb)
was: The parameter is incorrect"

That kind of points to corruption too doesn't it?




"Mark L. Ferguson" wrote:

The error is saying there is some conflict. Is there a Machine named 'SHARE'
recently added to the net? Have the standards for the password been limited
in some way, like 8 character passwords or whatever? Since the error seems
to 'kick in', I would be looking for influence from the GPO or Policy.
--
Was this helpful? Then click the Ratings button. Voting helps the web
interface.
http://www.microsoft.com/wn3/locales/help/help_en-us.htm#RateAPostAsAnswer
Mark L. Ferguson
.

"tooner" <tooner@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F00C14DB-2DF2-4046-9956-08DEF0CDA7F7@xxxxxxxxxxxxxxxx
Thanks for replying so quickly. I am on site now so I can be a bit more
detailed with the error. When I originally arrived I could remove and add
drive mappings ok so I thought I'd try a reboot to see if it still worked.
The same problem has reappeared. I did try your suggestion and it found
some
errors but unfortunately has not resolved the it.

Please note, I am currently logged in as user "share" with password
"share"
The target also has an admin account with the same credentials and has
full
share and file system permissions.

1)
--------
C:\Documents and Settings\share>net use s: \\server\sage
The password or user name is invalid for \\server\sage.

To connect CLIENT\Guest to server, press ENTER, or type a new user name:
--------
2)
--------
C:\Documents and Settings\share>net use s: \\server\sage /user:share share
System error 1326 has occurred.

Logon failure: unknown user name or bad password.
--------

Does this help you work out what might be up? Next step is solution 9
again
followed by a reinstall.

Thanks
tooner


"Mark L. Ferguson" wrote:

Aside from trying solution 9) again, it seems to me that when you added
the
user name and password to the target, all that should not be happening,
no
matter what else is wrong. I think you are have some of the usual
Permissions trouble for the registry entries. Since it is intermittent, I
think you are going to have to consider some form of registry corruption
on
the client.

Although this might cause headaches with other shares, and make you
recreate
them again, I would try this utility on the client.
Aaron Stebner's WebLog Solving setup errors by using the SubInACL tool to
repair file and registry permissions:
http://blogs.msdn.com/astebner/archive/2006/09/04/739820.aspx
--
Was this helpful? Then click the Ratings button. Voting helps the web
interface.
http://www.microsoft.com/wn3/locales/help/help_en-us.htm#RateAPostAsAnswer
Mark L. Ferguson
.

"tooner" <tooner@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:DB83E466-3DDB-48BF-919E-15BDF15131A5@xxxxxxxxxxxxxxxx
I am having a problem I just can't seem to resolve no matter what I
try.
I
am trying to share 2 folders from one xp machine to another. They are
both
in the same workgroup and connected on same subnet etc. When I try
"net
use
s: \\server\share" sometimes it works and sometimes it doesn't. When
it
doesn't work I get a username and password error and it asks for the
password
for client\guest.

Things I've tried:

1) playing with local group policy (changed from guest to classic
amongst
other things)

2) turned on simple file sharing

3) added the user on the client machine onto the server with same
password
and added gave them permissions to the share and to ntfs

4) added EVERYONE user with full permissions to both the share and ntfs

5) turned off windows firewall

6) uninstalled security suites completely on both

7) net use s: \\server\share /user:server\serveruser serveruserpassword

8) created identical users with identical passwords on both machines
and
added permissions accordingly

9) kicked server hard

I was sure I had it solved after I completely uninstalled avast
security
suite (it was only disabled before) and I rebooted both machines and
the
shares both mapped fine from a bat file. It only worked until the next
day.

I've never had problems like this before and I just can't seem to work
it
out. There is only 2 machines on this network so I can't work out with
which
machine the problem lies.

Hopefully some genius out there can shed some light on this for me.

Thanks in advance
tooner

.