Shared Docs Access Denied

  • Thread starter Thread starter Dick Kling
  • Start date Start date
D

Dick Kling

I have two desktops running XP Pro & a notebook running XP Home. When I view
the workgroup I can see all three and I can access the shared drives -
CD-ROMs and a zip drive - but I cannot access the SharedDocs folders on any
of the computers. When I try to access the folders I get the error message

"\\ name of computer\ shareddocs is not accessible. You might not have
permission to use this network resource. Contact the administrator of the
server to find out if you have access permissions. Access is denied."

I'm not running the XP firewall and I get this message with Norton Internet
Security running or disabled.

There is only one user account on each of the computers. The drives are
formatted as NTFS. They each access the Internet on their own - no ICS.
I can see the shared folders in My Network Places but there is one peculiar
thing - one of the computers is identified correctly under the Comments
heading but under the Computer heading it is listed as Unknown whereas the
shared CD-ROM drive on that computer is listed correctly.

I don't know what other info to post.

I'm about to give up on trying to share a folders and just burn the files
to a CD and then copy them wherever I need them.


Thanks for listening!
Dick
 
I've been pulling my hair out over what looks like the
same problem for a couple of days now. In one location
Friday I went into a SOHO environment to network some XP
Pro machines and allow them to share a cable broadband
internet connection. I followed the XP guidelines and the
ICS host was setup first, no problem. The second PC went
smoothly, immediately was sharing the internet connect
via the host over a 10/100 net using XP ICS--also
immediately had access to the shared files on the host
drive. Then I connected an XP laptop and ran the
identical setup, it found the internet via the host
immediately, then coughed up the exact message you are
getting when I tried to access a shared folder on the
host (in exactly the way I did on the previous machine).
I didn't have time to deal with it, so I went on to set
up another laptop with XP on the same net and that went
without a hitch. The access denied anomaly is
inexplicable to me. Then I spent today experimenting with
my XP laptop at home trying to net with an ME machine--
the same bizarre message cropping up when I look from the
XP machine into the ME, though the ME can see into the XP
machine fine. I poked and prodded the protocols on both
machines and finally get the XP machine to obtain access
to the ME machine on the second try (each time), first
time access denied (as your message below, exactly), then
second time presents with a logon and password prompt,
which I answer correctly having setup a password share on
the ME machine once it became clear it was insisting on
it. Don't know how to get around that, the only other
option is user/group list access and I don't really know
how to set that up--never ran into this can of worms
before. I still can't use the printer connected to the ME
machine via the net from my XP machine. The add printer
wizard seems to work fine then when I try to print to the
printer, which appears online, it times out access
denied. I am not using ICS on this mini-network. Using
Client for MS Networks, File and print sharing for MS
Networks, DHCP automatic private addressing, primary
logon (on ME machine) Client for MS Networks. I think I
need a better grasp of the horde of detail involved here--
when it works smoothly, i.e., the more or less automated
network setup process, it looks rational enough, but once
things go wrong myriad interacting settings, many of
obscure significance, particularly in their interaction
with one another, come into play. Anyone have any
suggestions (other than to reformat the ME machine and
reinstall the OS, which I would if I had the system disk,
but I don't). Are our problems related (the original
posting here as well as my other problem Friday with the
identical error message) or the error message simply
pretty general in response to a number of different modes
of failure?
 
Back
Top