Network Drive Is Not Accessible An Unexpected Network Error Occurred
Contents |
tech Search Tags: Builds Cases Cooling CPUs Graphics Laptops Memory Monitors Motherboards more Peripherals PSUs Storage VR ForumNetworking Solved Unable to navigate to shared drive SamuraiDaveJul 23, 2012, 4:57 PM Hello,I am on Windows 7. Up an unexpected network error occurred windows 2012 until a week or so ago, I used to be able to navigate, using Windows
An Unexpected Network Error Occurred Windows 10
Explorer, ( Network > ServerName > SharedDrive) , to a particular shared network drive. I can no longer do this as I
0x8007003b: An Unexpected Network Error Occurred
get the following message:"\\ServerName>\
An Unexpected Network Error Occurred Windows 8
I modify the name of the server in the explorer address bar to include the fully qualified domain name, I am able to get to the shared folder. There are other folders on that same server where i CAN navigate to WITHOUT having to modify the server name.This does not appear to be a simple permissions issue as i can get to the folder using FQDN. Also, a permissions error has a an unexpected network error occurred mapped drive windows 10 different message:"Windows cannot access \\Walfile1\psgYou do not have permission to access \\Walfile1\psg. Contact your network administrator to request access."This seems to me to be some sort of routing or DNS issue.Sorry for the long winded message but my local IT is of no help, they just tell me that I have to use FQDN, - which doesn't make sense and is less than satisfactory because no one else in the organization has to, I can navigate to other folders on the same server with no problem, and in order to access links that people send me to those folders, I need to modify them.I used navigating as an example but of course, all access to that shared drive now requires me to use FQDN, links, command line access, shortcuts etc.Any help would be very much appreciated 5 answers Last reply May 20, 2014 Best Answer Jul 23, 2012 More about unable navigate shared drive eibgradJul 23, 2012, 6:21 PM It does sound to me like a naming conflict, as if when you use the unqualified name, it's resorting to DNS naming instead of Windows naming, or vice versa. IOW, using the unqualified name makes the search for resolution different, changing it to either DNS or Windows. It’s hard to be more specific because either is possi
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Asked by: An unexpected network error occurred Windows Server > Network Access Protection Question 0 Sign in to vote Dear c# an unexpected network error occurred all, I have a DC Windows Server 2003 which is a File Server error 0x8007003b windows 10 too. There is a shared drive and I used the NET USE command in the Server in order to open the error 0x8007003b: an unexpected network error occurred windows 10 shared drive/folder in the client computers Windows XP and Windows 7 when they turn on their computers. It was working normally in the past. It is about two weeks that when the client turn http://www.tomshardware.com/forum/41171-42-unable-navigate-shared-drive on his/her computer the shared drive does not open, when double-click on the share drive from client computer we receive the error message "An unexpected network error occurred" and we can not get access to the share drive in the Server. of course I can ping the server, if I try to connect to DC by \\servername or \\Server-IP address, still I got the same error message. Would you https://social.technet.microsoft.com/Forums/en-US/09d56607-b1f3-45ec-b424-89d5b3cea45d/an-unexpected-network-error-occurred?forum=winserverNAP kindly help me, and thanks in advance for support. Best regards, Ahmad Tuesday, March 06, 2012 10:36 AM Reply | Quote All replies 0 Sign in to vote A few things to try. Confirm that the share is still running on the DCConfirm the NTS permissions on the file shareCheck that there is no time skew between the DC and the Client as this will cause issuesRestart the computer browser service on the clientRestart the computer browser service on the server (out of hours) Tuesday, March 06, 2012 1:53 PM Reply | Quote 0 Sign in to vote I would say that this post is probably in the wrong forum and may get more answers in the general windows serve forum. Tuesday, March 06, 2012 1:54 PM Reply | Quote 0 Sign in to vote - share is still running on DC, confirmed - NTFS permission, confirmed - Same time zone in DC and all clients which is +4:30 - The computer browser services restarted I would like to add one more issue, some times a client computer can access to the share drive but some times cant. Wednesday, March 07, 2012 5:16 AM Reply | Quote 0 Sign in to vote Hi
the domain successfully accessing Mapped drives just gave the error "An unexpected network error has occured" there is nothing logged in Event Viewer or next to no diagnostics to run to figure out this problem.After a little testing I found that you can access the server manually running its DNS name and then disconnect and re-map the drives you use and this clears the error.Probably not the best fix - but a fix none the less, If anyone has any other solutions feel free to post. Posted by Kris Haynes D.C.M.T at 09:27 Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: networking, windows 7 2 comments: ElectroFunkDaddy11 March 2010 at 11:58Hey Man,We have the same problem here, happens on daily occurance, I havent had time to really investigate. doesnt make much difference mapping drives via Netbios name, hostname, FQDN.but very strange,Drives are Mapped at logon, :- SuccessfulAccessing the Mapped Drive Root :- SuccessfulAccessing a Subfolder :- Results in the same Error as you have.Also @ anypoint in the day a user will double click on a file to open, they receive this error on 1st time. if they immediatly double click again it opens?ReplyDeleteAvi00320 May 2014 at 08:10In the Local Group Policy Editor, go to- Run --> gpedit.msc --> Local Computer Policy-> Computer Configuration-> Windows Settings-> Security Settings-> Local Policies-> Security OptionsFind the policy:Microsoft network client: Digitally sign communications (always)If this is enabled, change it to Disabled. Be sure and restart your machine for the change to take effect! Pressing the "Apply".After restart the system may be any pop will come just click on yes buttonReplyDeleteAdd commentLoad more... Newer Post Older Post Home Subscribe to: Post Comments (Atom) Support this site: Any donations are kindly received and are used to keep the Site and its content going. Search This Blog Loading... About Me Kris Haynes D.C.M.T Chesterfield, Derbyshire, United Kingdom I work at a company in Milford, Derbyshire called Axess Systems as a Enterprise Cloud Architect. I also run a number of my own firms, with my most busy being Del