Solved

Net Use - System error 53 has occurred. The network path was not found

Posted on 2010-11-14
3
2,453 Views
Last Modified: 2012-08-13
I have a SBS 2003
I map to three drives with a bat file in default domian policy (at logon) which works fine
I have one other drive I want to map to only a few users. I created a group for the users, created the share and add the group to that share under sharing/permissions. I added the group to the few users as well. The drive mapping does not work for that one drive

When use explorer to access the drive \\server\drive and I access and create files on the drive. When I do net use X: \\server\drive I get "System error 53 has occurred. The network path was not found"
Only on that one drive. If I net use Y: \\server\drive on the drive where everyone has access to it works fine with no erros.

Any ideas why?
0
Comment
Question by:Gerhardpet
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
3 Comments
 
LVL 27

Accepted Solution

by:
KenMcF earned 500 total points
ID: 34131041
The new share does it have a space in the sahre name?

You would have to use this
net use y: "\\server\share name"
0
 
LVL 77

Expert Comment

by:Rob Williams
ID: 34131130
You can share a drive, did you, or a folder?

You should set the share permissions to everyone full control and then set access permissions with NTFS (security) permissions. When doing so make sure you add the system account with full control.
0
 
LVL 1

Author Closing Comment

by:Gerhardpet
ID: 34131205
Thank you! Yes I have spaces....almost lost my hair over it....
0

Featured Post

Enterprise Mobility and BYOD For Dummies

Like “For Dummies” books, you can read this in whatever order you choose and learn about mobility and BYOD; and how to put a competitive mobile infrastructure in place. Developed for SMBs and large enterprises alike, you will find helpful use cases, planning, and implementation.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Is your Office 365 signature not working the way you want it to? Are signature updates taking up too much of your time? Let's run through the most common problems that an IT administrator can encounter when dealing with Office 365 email signatures.
This article outlines the process to identify and resolve account lockout in an Active Directory environment.
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
Are you ready to implement Active Directory best practices without reading 300+ pages? You're in luck. In this webinar hosted by Skyport Systems, you gain insight into Microsoft's latest comprehensive guide, with tips on the best and easiest way…

733 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question