1 of many Win 7 Client unable to locate 1 of many shares on Win2k3 R2 server
I am at a loss for even where to look on this issue. We have one windows 7 client that connect access a share on a windows 2003 r2 server. That is not odd. What is odd is that he can access other shares with no issue. He is getting network name not found (0x80070035) This is very odd because it happens even when he browses to the server in explorer and tries to open the share that way. Multiple other users are able to access the share with no issue. I am have never seen a case of network name not found when you can browse to the server and are double clicking to open the share. Is there possibly some cache in Windows 7 that might somehow have been corrupted? Any insight would be greatly appreciated. ~joe
June 16th, 2011 2:05am

Hi, Thanks for posting in Microsoft TechNet Forum. We can try the following steps to narrow down cause: 1. Try to disable the shared folder and share this folder again to check how it works. 2. What is the result in Safe Mode with networking? 3. Could you access the specific shared folder via UNC path or IP address? 4. Disable the network adapter in Windows 7 and enable it to check what the result is. Alex Zhao TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.comPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
June 16th, 2011 1:06pm

Hi, I am just writing to check the status of this thread. Was the information provided in previous reply helpful to you? Do you have any further questions or concerns? Please feel free to let us know. Alex Zhao TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
June 20th, 2011 4:27am

Updates: Additional things tried: 1) Reboot of client - no effect 2) Reinitialize Offline Files Cache and database then reboot - no effect 3) Disable offline files for all shares on server - no effect 4) Access same files through administrative share ( \\servername\d$\directory ) - works properly 5) Tried access though 2 different network adapters (1 wired one 1 wireless) -- no difference (is this as good as your step 4?) Next steps: 1) Server will be rebooted tonight and tested again tomorrow 2) Verify CSC reinitialization steps to ensure that proper method was used Win7 vs. WinXP 3) Try access same share by IP instead of NBName 4) If issue persists Tuesday evening, rebuild share Sorry to be slow in responding, but this is a production server and modifications have be vetted, scheduled, and verified. Regards, Joe M.
Free Windows Admin Tool Kit Click here and download it now
June 21st, 2011 5:32am

Hi, How are things going? If you could update us at your earliest convenience that would be wonderful. Alex Zhao TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.comPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
June 22nd, 2011 1:00pm

Hi, As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as ‘Answered’ as the previous steps should be helpful for many similar scenarios. If the issue still persists, please feel free to reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish. BTW, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems. Thanks for your understanding and efforts. Regards, Alex Zhao TechNet Subscriber Support in forum If you have any feedback on our support, please contact tnmff@microsoft.com.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
June 27th, 2011 4:31am

The issue persists. Additional steps taken: 1) Delete and recreate Share on server -- No Impact Same behavior 2) Access share by IP instead of NBNAME -- Works properly 3) Checked client credential manager -- no stored credentials 4) Disbaled CSCSERVICE on client, then reboot -- No impact same behavior. Additional notes: 1) Previous attempt to clear offline files cache used XP mehtod. Did not retry with Win7 method, but service was disabled entirely in an attempt to rule out offline files. 2) Prior to this issue occurring, user had issues where only some files on this share would appear. If he came back 15 minutes later it would show all files. 3) Server was recently rebuilt from gold image we are using. Issues started shortly after, possibly concurrent with rebuild. Sorry to be slow in responding, I am juggling a number of high priority issues right now. ~joe
June 27th, 2011 7:30pm

Hi, Thanks for update. It sounds like something blocks this share folder; it may be caused by Windows 7 or Windows server. I would like to confirm the following details: What is the result in Safe Mode with networking? Can you ping the Windows Server via computer name? From the update information: delete and recreate Share on server --no impact. Does this issue occur to all share folders created newly? Currently, to find some useful clues on this problem, try to use process monitor to monitor this issue: Troubleshooting with Process Monitor Alex Zhao TechNet Subscriber Support in forum If you have any feedback on our support, please contact tnmff@microsoft.com.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
June 28th, 2011 5:42am

Hi, I'm just writing to see if you have had an opportunity to gather the requested information. I look forward to hearing from you. Alex Zhao TechNet Subscriber Support in forum If you have any feedback on our support, please contact tnmff@microsoft.com.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
June 30th, 2011 10:14am

Hi, As this thread has been quiet for a while, I would mark the suggestions above as "Answer". If the issue still persists, please feel free to reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish. Regards, Alex Zhao TechNet Subscriber Support in forum If you have any feedback on our support, please contact tnmff@microsoft.com.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
July 4th, 2011 4:05am

Have not tried safe mode with networking yet. Yes, the server can be pinged by IP, NBName, and FQDN. Mapping works to the share by IP but fails when NBName is used instead. There are multiple shares created before and after this one that do not experience the issue. What process should I be monitoring? How do I identify what to watch? ~joe
July 7th, 2011 12:27am

Hi, Thanks for update. According to your description, this would be related to the new built Windows Server. Please set full shared folder permission on Windows Server to check the result: 1. Right-click the new folder, and then click Properties. Click the Security tab. 2. Click Add. In the Select Users, Computers, or Groups dialog box, add Everyone to group list. 3. Give the full control permission to Everyone, and then click Apply and OK. Meanwhile, try to flush and reset a client resolver cache: Open a command prompt. To open an elevated Command Prompt window, click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator. At a command prompt, type the following command, and then press ENTER: ipconfig /flushdns You could launch the process monitor and then start the operation of accessing shared folder, then process monitor would record the process information automatically. Regards, Alex Zhao TechNet Subscriber Support in forum If you have any feedback on our support, please contact tnmff@microsoft.com. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
July 7th, 2011 6:30am

Alex: Please excuse my tone, but I am quite shocked at these suggestions. They run counter to my understanding of LANMan/SMB/CIFS. Please help me understand why these suggestions would be helpful. Just to save some reading here is a rundown of works vs not works. Only one users experiences the issue. No other user has this issue. \\NBNAME\share1 -- Gives network name not found error \\NBNAME\share2 -- works \\NBNAME\m$\directory_of_share1 -- works \\ip_of_server\share1 -- works Add user to local administrator group on server -- no effect on symptoms above. Disable offline files on all shares on server -- no effect on symptoms above. Disable CSCSERVICE on client -- no effect on symptoms above. Shut down client over the weekend -- no effect on symptoms above. Reboot server -- no effect on symptoms above. Delete and recreate share1 on server -- no effect on symptoms above. Delete and recreate share2 on server -- no effect on symptoms above. How can share permissions be the issue if the user can access the share using server by IP but not name? What does flushing the local DNS cache do that a reboot does not? Why would this be helpful when we can ping by name and access other shares on the same server when using server nbname? NOTE: this is not a DFS, or highly available share. This is on a plain Windows 2003 R2 server (not a DC) joined to a sizable domain. Thank you for taking the time to consider the issue fully. Regards, Joe M.
July 7th, 2011 7:38am

Hi, Please understand we need find the real cause of this issue. From your additional note, the issue may be related to the new built Windows Server, and you could not map the shared folder with computer name. Before we capture the process information, we can narrow down this issue with the suggestions above. When you launch process monitor, it would record the information about the path, the Process ID, the User and relevant DLL files, this would be helpful to find the cause. Regards, Alex Zhao TechNet Subscriber Support in forum If you have any feedback on our support, please contact tnmff@microsoft.com.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
July 7th, 2011 9:07am

Please consider this issue resolved. The workaround of using IP instead of name for that one share is sufficient for the user. I do not see much hope of finding root cause working through the issue here. Regards, Joe M.
July 7th, 2011 8:19pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics