View Full Version : Accessing shared folders problems
Carl Sjoblom
December 5th 03, 07:46 PM
I'm having some problems accessing shares on a specific
computer.
Our environment is NT4 servers running a domain and all
clients are running WinXP Pro.
On one specific computer (and this computer only,
support01), when I try to access the shares on it I get
an error message saying that the computer is not
accessible and that I do not have the permission to
access this network resource. When I try to access any
other computer on the network I get the standard shares,
printers and scheduled tasks.
This problem only exist if the computer I try to access
from is not a part of our domain but a workgroup.
I have checked that...
.... "Everyone" has read-access under the NTFS settings
.... "Everyone" has read-access under the Share permissions
.... "Everyone" can access the computer from the network
under the local security settings policy
The funny thing is that it won't even prompt me for
username and password when I try to access the
administrative shares (e.g. C$). The only workaround I've
found is using "map network drive", but this is not good
enough - I want a share that should be accessible to
everybody on the network, regardless if they're a part of
the domain or if they even have a login on our network.
Appreciate any suggestions!
Sincerely,
// Carl.
Dolemite
December 5th 03, 07:47 PM
First off is NT4 SP6a installed?
http://support.microsoft.com/default.aspx?scid=kb;en-us;313384
Secondly, read these and see if they help:
http://support.microsoft.com/default.aspx?scid=kb;en-us;812924
http://support.microsoft.com/default.aspx?scid=kb;en-us;314984
"Carl Sjoblom" > wrote in message
...
> I'm having some problems accessing shares on a specific
> computer.
>
> Our environment is NT4 servers running a domain and all
> clients are running WinXP Pro.
>
> On one specific computer (and this computer only,
> support01), when I try to access the shares on it I get
> an error message saying that the computer is not
> accessible and that I do not have the permission to
> access this network resource. When I try to access any
> other computer on the network I get the standard shares,
> printers and scheduled tasks.
>
> This problem only exist if the computer I try to access
> from is not a part of our domain but a workgroup.
>
> I have checked that...
> ... "Everyone" has read-access under the NTFS settings
> ... "Everyone" has read-access under the Share permissions
> ... "Everyone" can access the computer from the network
> under the local security settings policy
>
> The funny thing is that it won't even prompt me for
> username and password when I try to access the
> administrative shares (e.g. C$). The only workaround I've
> found is using "map network drive", but this is not good
> enough - I want a share that should be accessible to
> everybody on the network, regardless if they're a part of
> the domain or if they even have a login on our network.
>
> Appreciate any suggestions!
>
> Sincerely,
> // Carl.
Carl Sjoblom
December 5th 03, 07:48 PM
Thanks for answering!
>-----Original Message-----
>First off is NT4 SP6a installed?
Yes, we're running SP6a on all NT4 servers in the
network. They're carefully updated.
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;313384
I don't think this is the issue, since the machine where
the shares are is a Windows XP Pro machine.
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;812924
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;314984
I've read both these articles, unfortunately it does not
address my problem.
The affected computer is a small file server
called "support01", running winxp pro (all patches
applied).
The problem is *not* that the shares doesn't exist, I can
access them just fine as long as the computer trying to
reach the share are a part of our domain. When I try to
reach the share from a computer that is a part of a
workgroup (say a freshly installed computer) then it just
throws an error message at me - it doesn't even prompt
for a login.
Question is, is some kind of login saved in a cached
profile somewhere? If so, where?
What possible conflicts in the access permissions could
there be (both NTFS- and Share permissions
have "Everyone" for read).
I suppose I could always reinstall support01, but that
just wouldn't be a stylish solution to the problem. :-)
Thanks for your time and effort, deeply appreciate it.
Sincerely,
// carl.
Dolemite
December 5th 03, 07:48 PM
Not a problem. I have a bookmark on this thread.
"Carl Sjoblom" > wrote in message
...
> Thanks for answering!
>
>
> >-----Original Message-----
> >First off is NT4 SP6a installed?
>
> Yes, we're running SP6a on all NT4 servers in the
> network. They're carefully updated.
>
> >http://support.microsoft.com/default.aspx?scid=kb;en-
> us;313384
>
> I don't think this is the issue, since the machine where
> the shares are is a Windows XP Pro machine.
>
> >http://support.microsoft.com/default.aspx?scid=kb;en-
> us;812924
> >http://support.microsoft.com/default.aspx?scid=kb;en-
> us;314984
>
> I've read both these articles, unfortunately it does not
> address my problem.
>
> The affected computer is a small file server
> called "support01", running winxp pro (all patches
> applied).
>
> The problem is *not* that the shares doesn't exist, I can
> access them just fine as long as the computer trying to
> reach the share are a part of our domain. When I try to
> reach the share from a computer that is a part of a
> workgroup (say a freshly installed computer) then it just
> throws an error message at me - it doesn't even prompt
> for a login.
>
> Question is, is some kind of login saved in a cached
> profile somewhere? If so, where?
> What possible conflicts in the access permissions could
> there be (both NTFS- and Share permissions
> have "Everyone" for read).
>
> I suppose I could always reinstall support01, but that
> just wouldn't be a stylish solution to the problem. :-)
>
> Thanks for your time and effort, deeply appreciate it.
>
> Sincerely,
> // carl.
vBulletin® v3.6.4, Copyright ©2000-2012, Jelsoft Enterprises Ltd.