Re: Shared Folder NIGHTMARE!!!!

From: Jason G (msft-ngroups_at_zz9.biz)
Date: 09/04/04 

Date: Sat, 4 Sep 2004 15:57:02 -0700

Hi again,

The net use should, at least, not give you an error, it is a way to tell
your computer that when attempting to connect to the server (we'll call it
SVR1) it should use the user name (we'll calll him FRED1), so should appear:

net use \\svr1 /user:fred1

IF however your system has already has an established link then you should
do this:

net use \\svr1 /delete

first - to break any link - don't worry its just a session based security
command and won't actually delete anything real!

You can then try the net use again.

I'm assuming your server is a Windows XP machine too - or at least is NOT a
domain controller (these are quite differernt for security purposes)
therefore security is pretty similar to your other XP systems. Within what is
know as a peer-to-peer or workgroup environment each system should know the
usernames and passwords for the users on other systems that it should trust -
if you have totally open file sharing (NOT recommended) then this is not
essential, but I wouldn't go there.

You have a couple of levels of permissions to look at:
1) Share level permissions - these define who can connect to the share on a
system and the MAXIMUM rights of that user for the session - this is usually
one of : NONE, READ-ONLY, CHANGE or FULL - this is set under the Permissions
button on the Sharing tab for a folder - default on XP (SP2) is Everyone -
READ

2) file level permissions - this is only a concern when you are using an
NTFS formatted drive - you can easily tell as if you go to the properties of
a file or folder on an NTFS drive you will get a Security tab - settings are
found there for file level security.

Give the net use \\svr1 /delete a go with the /user net use after doing that
and see how you go.

I'm off soon but will probably be around for a little while if you re-post,
otherwise I'll look forward to hearing of your progress tomorrow.

Regards,

Jason

"Darren M Taylor" wrote:

> Hi Jason
>
> OK....i'll try and follow that.
> when i use net view i get error 53. I tried the net use \\servername
> /user:username that you suggested, but somehow the format wasn't accepted
> and it didnt work.
> However, I have this evening managed to access the shared folder on the
> server from my laptop, although my laptop uses the same account name and
> paasword as the 'server'. perhaps this may account for how i am able to see
> the shared folders on the server???
> However, i can see shared folders from 1laptop to another laptop, both of
> which have different usernames and passwords!!!
> I am convinced that the problem must lie in the permissions allowing access
> to the shared folders although just how to set that up is a different
> matter!!!!
> If i go into permissions on the server, i am able to set permissions for
> local users on the 'server' however i am not able to set permissions for any
> other users/computers on the network (workgroup).
> I guess what i may need to know is how to set permissions for other
> workgroup pc's / users....????
>
> Darren
>
>
> "Jason G" <msft-ngroups@zz9.biz> wrote in message
> news:7A560490-E0B2-4F84-945C-DEB21E1E1F2D@microsoft.com...
> > Hi again Darren,
> >
> > The HOSTS file just allows you to set an association between an IP address
> > and a host name - if you only have the .SAM files, then you aren't using
> > the
> > file, thats fine.
> >
> > If you are getting a permissions error on NET VIEW then this may suggest
> > that the user context that you are in does not have permissions on the
> > server
> > - when you use the NET USE method, do you then get prompted for a
> > password?
> >
> > If you try
> >
> > net use \\servername /user:username
> >
> > where the servername is the name of your server and the username is the
> > name
> > of a user with known good permissions on that server, - you will probably
> > be
> > asked for the password for that user ... then retry your other access
> > methods (briefcase etc) and see if you have success - if this does work
> > then
> > you need to add the user name under which you log on to the client PC to
> > the
> > server's user list - and make sure you do have passwords (and that they
> > match
> > across systems!)
> >
> > Let me know if this reveals anything new.
> >
> > Regards,
> >
> > Jason
> >
> > "Darren M Taylor" wrote:
> >
> >> I am having one hell of a nightmare.
> >> Having spent the last 3 days trying to resolve a shared folder problem...
> >>
> >> Background.... I have 6 pc's all wired/wireless networked very happily.
> >> All
> >> running XP pro SP2 and all able to access internet with no problems at
> >> all.
> >> Several of the PC's have shared folders/drives which until recently were
> >> accessible by all the other PC's.
> >>
> >> NOT ANY MORE....
> >>
> >> Since Thursday, I have 1 PC (which i shall call server because it has
> >> most
> >> of the shared folders and is the only PC wired to the network) which will
> >> not allow any of the others to access it's shared folders/printers.
> >> I have meticulously searched all the websites, KB etc and followed all
> >> the
> >> advice they can offer but still no luck
> >> I can ping from any PC to the server and vice versa, it is listed on the
> >> workgroup and yet still no luck connecting to the shared folders.
> >> Now, I followed one help thread and it did take me a little further
> >> forward.
> >> Basically, if i use the
> >> net use x: \\servername\sharedfolder command to connect to the shared
> >> folder
> >> it works!!!!! and i see the shared folder as a mapped network drive. BUT
> >> THAT ONLY HELPS SO MUCH... and i have briefcase files which will not work
> >> that way.
> >>
> >> I have tried renaming, re-installing TCPIP, disabling simple file
> >> sharing,
> >> everything ...but nothing has worked.
> >>
> >> I would really be very appreciative if anyone could possibly help coz i
> >> really am tearing whats left of my hair out!!
> >>
> >> Many TIA
> >>
> >> D
> >>
> >>
> >>
>
>
>