I've recently noticed that when trying to access network shares located on one of the servers (Windows 2008 R2 Enterprise SP1) that the local accounts on the domain joined workstations running (Windows 7 Enterprise x64 SP1) are unable to view or access anything. When you click the "Network" icon in Windows 7 to view the network and click on the server, when it opens, nothing is visible, let alone accessible. This only seems to be a problem for the domain joined workstations since upgrading to Service Pack 1. When I was preparing some new machines for deployment they had access to view the shares and when accessing the server I was prompted with the normal access dialog (domain/username and password) like I was able to do on the domain joined PC's before this issue happened. Once those workstations are joined to the domain they end up like the rest with no visible shares or access. Accessing shares on other servers and workstations work like normal and have no problems. The server in question is one of the file servers and the networks PDC (only domain controller) running Windows 2008 R2 Enterprise SP1. All workstations are running Windows 7 Enterprise x64 SP1. The shares permissions are set to allow access for the domain joined computers and file sharing/network discovery is enabled on both the server and workstations. Nothing has changed in configurations on either side except for upgrading to Service Pack 1. A test workstation with a clean copy of Windows 7 Enterprise x64 without SP1 was joined to the domain and was able to access the shares like I was able to do so before. The other Windows 2008 R2 SP1 server is able to access the shares like normal from a local account. I use local accounts for certain users (limited accounts with restrictions) and for IT (local administrators) to manage the workstations, (the built-in admin and guest accounts are disabled). Any help will be greatly appreciated. Thanks. Regards, Derek Thompson MSPS LLC <Public Safety Solutions>

Hi, Before going any further, I would like to verify this issue happen with all Windows 7 64bit or an especial one? I suggest to perform these tests to troubleshoot the issue: 1 Login with Safe Mode with networking or Clean Boot 2 Temporally disable firewall or antivirus program on Windows 7 3 Check client for Microsoft networks is installed and enabled on your Local Area connection properties 4 Enable NetBIOS over TCP/IP 5 Try using \\servername\\sharefolder or \\serverIPaddress\\sharefolder to see if it can access Furthermore, you can try to login with domain administrator for test. Hope that helps. Regards, Leo Huang 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.

Mr. Huang, Thanks for your response! I logged into all the workstations this morning and found that only a few of the machines operate like normal. The rest of the computers are experiencing the same problem as described above with the exception of a couple things. I found that if a network share has been made available offline on a particular machine, then those shares are visible when accessing the server. When I click the cached shares, I'm prompted for my credentials, and once I gain access I'm able to view/access the remaining shares like normal using any method. NetBIOS over TC/IP was on the default setting; I changed the setting to enabled and the Client for Microsoft Networks is enabled. I'm still unable to view/access the shares by the Windows "Network" location or using Explorer navigating to the server name e.g: "\\SERVER", but now I'm able to access the server using the LAN IP address e.g: "\\1.1.1.1", and I'm prompted for my credentials, once provided, I'm able to view and gain access to the server shares without a problem using the IP method only. I'm able to perform most of the tasks using this method, but if you have any further advice on how to further resolve this issue I will be more then willing to troubleshoot further. Please advise. Thanks. Edit: I did a once over and compared settings on the machines that are working properly to the ones that are not, and everything seems to be set the same. Also note that some of the computers are identical machines where one is not experiencing the issue while the other one is. _______________________________________________________ Regards, Derek Thompson | MSPS LLC <Public Safety Solutions>

Mr. Huang, Thanks for your response! I logged into all the workstations this morning and found that only a few of the machines operate like normal. The rest of the computers are experiencing the same problem as described above with the exception of a couple things. I found that if a network share has been made available offline on a particular machine, then those shares are visible when accessing the server. When I click the cached shares, I'm prompted for my credentials, and once I gain access I'm able to view/access the remaining shares like normal using any method. NetBIOS over TC/IP was on the default setting; I changed the setting to enabled and the Client for Microsoft Networks is enabled. I'm still unable to view/access the shares by the Windows "Network" location or using Explorer navigating to the server name e.g: "\\SERVER", but now I'm able to access the server using the LAN IP address e.g: "\\1.1.1.1", and I'm prompted for my credentials, once provided, I'm able to view and gain access to the server shares without a problem using the IP method only. I'm able to perform most of the tasks using this method, but if you have any further advice on how to further resolve this issue I will be more then willing to troubleshoot further. Please advise. Thanks. Edit: I did a once over and compared settings on the machines that are working properly to the ones that are not, and everything seems to be set the same. Also note that some of the computers are identical machines where one is not experiencing the issue while the other one is. _______________________________________________________ Regards, Derek Thompson | MSPS LLC <Public Safety Solutions>

Hi Derek, Thank you for your update. Did you receive any error message when you open Network? Have you tried login with Safe Mode with networking and disable firewall on that issue PCs? I noticed that these PCs cannot access server via \\servername but can access via \\ipaddress. Please try to Register DNS via command on Windows 7: 1 ipconfig /flushdns 2 ipconfig /registerdns Since the issue appear with a number of PCs, that’s seem a common issue and might related with Server GPO settings, please check if you have set any GPO on server to restrict PC to access share folder. In addition, could you make a screenshot to show the result of opening the Network. You can Upload to SkyDrive Thank you for your cooperation. Regards, Leo Huang 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.

Hi, Did your issue solved? Please feel free to give me any update. Thanks. Regards, Leo Huang 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.

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, Leo Huang 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.

I apologize for the slow response. I've been away from the office and I haven't yet been able to perform what was requested in your latest post. This weekend I will try the DNS flush/re-register DNS and record a screen video of what happens when I try and connect to the server as requested via IP and server name with a local account. As for the GPOs that are in effect, I will have to double check, but I don't think anything is applied that may be causing my issue. To experiment, I will install a clean copy of Windows 7 Enterprise x64 SP1 on a test machine with all the updates and join it to the domain with no GPO settings in effect to test the GPO theory. Thanks. Derek Thompson | MSPS LLC <Public Safety Solutions>

Hi Derek, Have you tried my suggestions? Or have you do the experiment of install a clean copy of Windows 7 SP1? Please feel free to give me any update. Thanks. Regards, Leo Huang 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.

I have tried your recent suggestions (dns flush/re-register, safe mode with networking/disable firewall) and was still unable to access the shares via "\\servername" or "\\servername\share". I performed a clean install of Windows 7 SP1 and joined it to the domain with no GPO settings applied and was still unable to access the shares. I do not receive any error messages or dialogs once I click into SERVER in NETWORK; it opens up a blank page. If I try and navigate to a share e.g. "\\servername\apps" it will remain blank unless I keep clicking the enter key or search button, then a dialog requesting my credentials to the server will appear. Once provided, several seconds later I am able to access the shares like normal but once I reboot or logoff, I am back at square one. The steps were taking are getting closer to the solution, if we could only find one to stick after a logoff/re-logon or reboot we will be all set. If no solution can be found though, I may just stick to the desktop shortcut pointing to the server IP "\\1.1.1.1" to gain access since that's been working so far. I appreciate all your responses and patience with this problem. If you have any more options to try I'll be glad to try them. Please note that with the recent storms/tornadoes in the area, I will be busy on service calls the remainder of this week and will not be in the office to troubleshoot other options till this Friday/Sat. Regards, Derek Thompson | MSPS LLC <Public Safety Solutions>

Hi Derek, Now seems that Windows 7 can access share folder by IP address but cannot access by \\uservername, I found a similar thread may be helpful to you: http://social.technet.microsoft.com/Forums/en/winservergen/thread/da258cb9-9b13-4ff2-a72a-d54c2e39adfc In addition, you can try to add a record in host file on Windows 7: C:\Windows\System32\drivers\etc\HOSTS Furthermore, since the issue still persists on a clean install Windows 7 SP1, that’s a possible that the issue related with Share Server, I suggest to ask Server Forum for further help, may be you can found the solution there: http://social.technet.microsoft.com/Forums/en-US/category/windowsserver Regards, Leo Huang 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.