I am running a local network with several computers. Remote file sharing worked fine for quite a while, and was able to access every computer from any other computer. However, now I am not able to access one the laptops (Win 7 Ultimate 32 bits) from a desktop (running Win 7 Ultimate x64). I can access shared files if I use the IP as in \\192.168.0.x without any issues, but not if I use \\computername. On both pcs I have Netbios enabled over TPC/IP and have network discovery on, file and printer sharing on, etc. I have no problems accessing file shares through the \\IP, but it's often a nuisance that the name cannot be used. Firewalls are not the issue, as this happens even with firewalls off. Any help is appreciated. Thank you.

I also have this problem. I was on Microsoft 'Answers', but they just hand-balled me to here. Found your post, and now I want answers. I have included my original post: G'day! I have a problem (which happened intermittently before, but now is permanent) with connecting to our 'server' (\\BLS_SERVER\) from a laptop also running win 7 x64. Both computers can access the internet. From the laptop, i can ping all devices on our network. From the laptop i can ping 'BLS_SERVER' as well with no problems. However, from the laptop, trying to connect to \\BLS_SERVER\share or even a share on the laptop itself gives me Error Code0x80070035 . I have turned off windows firewall on both computers. I have enabled Netbios over TCP/IP If there is any more information needed, I will post a reply. Please help, as we are trying to run a business. Also, password protected sharing is OFF . The server can access all shares on the laptop. :P

Hi, Thanks for posting in Microsoft TechNet forums. As I understand that you encounter the following scenario: You can access share folder with IP address, but can’t access it with PC name. I will give you some suggestions you can try: 1 Try to access another pc with Windows 7 to see if the same issue appears. 2 Check the “Computer Browser” server is start or not. Also check control panel----- Network and Sharing Center-----Advanced sharing setting, make sure “Network discovery” , “File and printer sharing” and “Public folder sharing” has turned on. 3 Try to clean the cache: run cmd-----nbtstat –c Or use: nbstat –a 192.168.0.x to force search the pc name 4 The computer can’t resolve the name, you need to check the hosts file under the location: C:\Windows\System32\drivers\etc. Open it in notepad and add the IP address, save the change to test. Or reset the hosts file. http://support.microsoft.com/kb/972034/en-us Hope it helps. Best 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, Thanks for posting in Microsoft TechNet forums. As I understand that you encounter the following scenario: You can access share folder with IP address, but can’t access it with PC name. I will give you some suggestions you can try: 1 Try to access another pc with Windows 7 to see if the same issue appears. 2 Check the “Computer Browser” server is start or not. Also check control panel----- Network and Sharing Center-----Advanced sharing setting, make sure “Network discovery” , “File and printer sharing” and “Public folder sharing” has turned on. 3 Try to clean the cache: run cmd-----nbtstat –c Or use: nbstat –a 192.168.0.x to force search the pc name 4 The computer can’t resolve the name, you need to check the hosts file under the location: C:\Windows\System32\drivers\etc. Open it in notepad and add the IP address, save the change to test. Or reset the hosts file. http://support.microsoft.com/kb/972034/en-us Hope it helps. Best 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, Suggestion 1: Can't be applied as there are only two Windows 7 PCs here. The computer in question can be access from a Vista laptop, though. 2. Computer browser service is running. Have no issues accessing XP or Vista PCs from the computer where the problem occurs. All advised settings for the network configuration were already in place. 3. The nbtstat commands had no effect 4. There was already an entry in the hosts file for the pc in question. I had added it long ago and didn't solve the issue. Thank you for your reply, nonetheless. I did try every suggestion I could find here or elsewhere on the net.

Hi, did this issue occurs with Windows XP? How about try using Windows XP Mode to see if the same issue appear? Install and use Windows XP Mode in Windows 7 And please make sure the “Guest” account is enable. Check the Gpedit.msc, go to Local Computer Policy\Computer Configuration\Security Settings\Local Policies\User Rights Assignment, find “Deny access to this computer form the network”, remove “Guest” account form it. Hope it hleps. Regards, Leo Huang 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, Sorry for the delay, but subscriptions don't seem to be working on this forum. I tried to connect from Windows XP Mode running in the same Windows 7 64 PC where I am experiencing the issue and had no problems at all to connect to the laptop from XP mode. Using \\computername worked right from the first attempt.

Hi, try to disable IPv6 on the computer and check if it works: 1. In Control Panel, click on Network and Internet. 2. Click the Network Sharing Center 3. On the left, click Manage Network Connections. 4. Right-click your Local Area Connection (or the connection for the affected adapter) and select Properties. 5. Remove the checkmark next to Internet Protocol 6 (TCP/IPv6). 6. Click OK. Hope it works Regards, Leo HuangPlease 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 ruirib, Do your resolve the problem? Please feel free to give me any update. 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 Leo, Thank you for your help. Unfortunately, disabling IPv6 didn't help. I unchecked the option, made sure it was disabled by executing ipconfig (and it was), but it had no effect. You know this seems like there is some caching somewhere. The connection attempt failed once and it's like those failure results were stored somewhere in the system, as Windows takes no visible time to even try to connect. Just states immediately that the computer cannot be found... but accessing it through \\IPaddress always works. Regards Rui

Hi, rui try restore your pc back to earlier stage, if you did install any software that are related to network like logmein hamachi or etc.

Hi, Sorry, it's impossible to do that. It's a rather "old" situation and too much stuff has changed since this started. This seems to be an issue with Windows 7 networking. It seems like the info about a given computer not being reachable was stored somewhere and it's never checked again. I can work around it, but it's still very annoying. Thanks for your reply.

still no solution? i have the same problem, but cant even access it using the IP adress this is a SERIOUS problem

It seems pretty obvious Microsoft has no solution for this.