[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 680
  • Last Modified:

Access denied when trying to open newly created local mapped network drive.

I have a Windows 2003 Server R2 standard setup.  When I map a drive on a new account created ON the server it shows that it is mapped, however, when I try to access the mapped drive it says access denied.  However, I can go to the folder locally on the server and access all of the information.  I have to have the drive mapped for the application we are using to work properly.  I have checked the permissions and I am stuck.  I do know that the administrator account maps fine and works properly.  Please advise
0
stallings123
Asked:
stallings123
  • 11
  • 10
1 Solution
 
sirbountyCommented:
You're looking at the security permissions - you need to modify the sharing permissions, which be default in W2k3 is Everyone/Read Only.
Change it to Everyone/Full and you should be all set! :^)
0
 
sirbountyCommented:
From the server - right-click the folder where the share is housed, and choose properties (or sharing and security) and then from the sharing tab, adjust the permissions there to Everyone/Full (or for tighter security, Authenticated Users/Full)
0
 
stallings123Author Commented:
That is already shared that way.
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
sirbountyCommented:
Can you post the results of the following: (run from the server)

Start->Run->CMD /C Cacls C:\YourFolderName > C:\Cacls.txt && c:\cacls.txt
0
 
stallings123Author Commented:
e:\apps\OMNI7 BUILTIN\Administrators:(OI)(CI)F
              CREATOR OWNER:(OI)(CI)(IO)F
              Everyone:(OI)(CI)F
              NT AUTHORITY\SYSTEM:(OI)(CI)F
              BUILTIN\Users:(CI)(special access:)

                                SYNCHRONIZE
                                FILE_WRITE_DATA
 
              BUILTIN\Users:(CI)(special access:)

                                SYNCHRONIZE
                                FILE_APPEND_DATA
 
              BUILTIN\Users:(OI)(CI)R
0
 
stallings123Author Commented:
e:\ BUILTIN\Administrators:(OI)(CI)F
    CREATOR OWNER:(OI)(CI)(IO)F
    Everyone:(OI)(CI)F
    NT AUTHORITY\SYSTEM:(OI)(CI)F
    BUILTIN\Users:(CI)(IO)(special access:)

                          SYNCHRONIZE
                          FILE_WRITE_DATA
 
    BUILTIN\Users:(CI)(special access:)

                      SYNCHRONIZE
                      FILE_APPEND_DATA
 
    BUILTIN\Users:(OI)(CI)R

0
 
stallings123Author Commented:
e: drive partition is shared then omni7 which is buried within e:\apps shared
0
 
sirbountyCommented:
Try unsharing it...use this method if you'd like (from a command prompt)
(and I'd remove "Everyone:F" from the security...

net share Omni /delete
net share Omni=e:\apps\omni

Then right-click the share and double-check Everyone account - it should be set to Read by default - change it to Full.

Next, on the security - open it up and click Advanced on the security tab, checking the 'change permissions on all child objects' as well...
0
 
stallings123Author Commented:
Still did not work.
0
 
stallings123Author Commented:
This is driving us crazy.  We can access all day with the administrator account.  If we make and user member of the administrator group it still does not work.  We tried copying to another folder and recieved the same error.  
0
 
sirbountyCommented:
Just a stab in the dark, but can you check tcp filtering?

Start->Run->ncpa.cpl
Right-click your lan, choose properties
Internet Protocol, Properties
Advanced, Options, Properties
Is that enabled and/or set to All?
0
 
stallings123Author Commented:
set to permit all
0
 
sirbountyCommented:
Okay, so locally you can access e:\apps\OMNI7 as the administrator 'or' any other account?

But remotely, you can only access \\servername\omni7 as the administrator - that correct?
0
 
stallings123Author Commented:
Yes I think that is it.  If I log in under the administrator account I can access the mapped o: drive which is mapped to e:\apps\omni7 (which omni7 is the shared folder) the executable is netomni.exe which is in a folder called progs e:\apps\omni7\progs.  I can map an o: drive to e:\apps\omni7\progs and run the executable but not if I do it the way the admin account is setup.  With any user that has rmeote access permissions I can map to any folder and access with no problems.  It is only this folder I am having the troubles with.  Also, if I am logged in as one of the remote users(not administrator account) I can run the program from a shortcut directly to the e: drive just not if it is mapped to the o:
0
 
sirbountyCommented:
Wait...are you mapping it to omni like this:

net use o: \\servername\e$\apps\omni7 ??
0
 
stallings123Author Commented:
there is an e$ administrative share.  I am not using the command line to map the drive.  I am right clicking on the folder.  
0
 
sirbountyCommented:
Right - ordinary users won't have access to e$, you'll need to use a share name.

Instead of \\server\e$\apps\omni7
they'll need to use
\\server\omni7
0
 
stallings123Author Commented:
that is what we are doing.  when we map o: to \\ibsldc\omni7 it will show the shared drive in my computer but when you click on it you will get a red x and says access denied.
0
 
sirbountyCommented:
Hmm - tough one to troubleshoot remotely, I'm afraid...
I'll take another peek at this in the morning when my brain is fresh...hopefully we'll get something sorted for you soon!
0
 
stallings123Author Commented:
Did you come up with anything?
0
 
sirbountyCommented:
http://support.microsoft.com/kb/310399 details how to turn on auditing (just do it on the server).  Check the security log afterwards (you'll need to enable auditing on that specific folder) and see if you can identify what's actually being restricted (audit both success and failures).

Also - while in the security of that folder, click Advanced - and from the Effective Permissions tab, enter the account that you're testing with - and see what the effective permissions are returning...I can't help but wonder that there's a deny in there somewhere...
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

  • 11
  • 10
Tackle projects and never again get stuck behind a technical roadblock.
Join Now