Yes unsharing it works and then you can adjust permissions but I bet I just broke some things doing that! :eek:
Printable View
Yes unsharing it works and then you can adjust permissions but I bet I just broke some things doing that! :eek:
Have you this thing enabled? It's disabled by default...Quote:
Originally posted here by RoadClosed
Yes unsharing it works and then you can adjust permissions but I bet I just broke some things doing that! :eek:
Well... I had a similar problem a few month ago. I couldn't reach C$ on my WinXP Pro box with \\192.168.0.2\C$. But then I tried another "trick". I used \\computer_name\C$ instead and it worked! Weird isn't it? :rolleyes:
You cannot change the share permissions, that's correct. But you can change the file permissions. So then you would be able to connect to the share (because of the share permissions) but you cannot read anything (because of the ACL on the files/directories).Quote:
Originally posted here by RoadClosed
SirDice, maybe that doesn't work from the actual PC you are trying it on? I have never been successful, of course I just chalked it up to Windows and never pursued it? If I try and change permisions on the default share of c$ I always get an error saying that I cannot change permissions. Hmmm maybe I have to be local box admin vs. domain admin? (edit: nope doesn't work either)
There are several things that could be the source of the problem.
1) Firewall (WinXP or 3rd party)
This will prevent all connections. But deadfrog is able to make a connection to IPC$. This wouldn't work when a firewall is active.
2) Admin shares disabled.
This will prevent connections to c$, d$ etc. It will allow you to connect to IPC$. When this is active it will give an error 51 if you try to connect to c$, d$ etc.
3) File level permissions (ACL).
This is the most likely candidate and when set to disable access for the administrator it will respond with an Access Denied. So check the ACLs on the machine you are connecting to.