Windows 10: Message: "Windows cannot access \\pcname\e" How to solve this?

Hi. I've got my laptop connected to my desktop PC with a crossover cable and managed to creat a private network. I want to acess certain partitions on the desktop from the laptop. Of course, I made the partitions on the desktop shared. However, When I click on the folder icon on the laptop representing a partition on the desktop I get the message "Windows cannot access \\pcname\e". Of course I've made up pcname for the purpose of this post. On the desktop every user (admin, system etc) has full control. But special permissions is greyed out. What more do I have to do so I can access the folders on the desktop from the laptop? Thanks. Rich

:)

 

Message: "Windows cannot access \\pcname\e" How to solve this?

Hi. I've got my laptop connected to my desktop PC with a crossover cable and managed to creat a private network. I want to acess certain partitions on the desktop from the laptop. Of course, I made the partitions on the desktop shared. However, When I click on the folder icon on the laptop representing a partition on the desktop I get the message "Windows cannot access \\pcname\e". Of course I've made up pcname for the purpose of this post. On the desktop every user (admin, system etc) has full control. But special permissions is greyed out. What more do I have to do so I can access the folders on the desktop from the laptop? Thanks. Rich

 

Message: "Windows cannot access \\pcname\e" How to solve this?

HI. Let me relate an happenstance I just had. I happened to look at Network in File Explorer and lo and behold the laptop had discovered a 2nd laptop I have. Must have done that wirelessly (possibly via the router). Clicking on the name of the 2nd laptop that's now in a network, a dialogue box came up asking for a user name and password. Well, using netplwiz on the target laptop, I managed to discover the user name and I then set up a password. I then set a partition sharable. I then used the user name and password to gain access to files and folders, including the partition I'd set to share, in this 2nd laptop. Now, if only my laptop would discover the desktop I want to bring into a network. If it did I would expect a dialogue box to show, and I do know the user name and password for the desktop, so then I would get the access.

EDIT: My laptop under network sees, the desktop I'm trying to access and the 2nd laptop I have. When I click on the 2nd laptop a dialogue box shows, and I can gain access by entering the user name and password. But, clicking on the desktop, I see folders which I cannot access. No dialogue box shows. I wish I could get to see a dialogue box asking for user name and password. Crossover cable is not used.

- - - Updated - - -

OK, I decided to connect the desktop and laptop1 and laptop2 to the router by ethernet cables. On WiFi setting I went to "Manage known networks" and on one of them (not my router) chose "forget". That got rid of whatever network I created with the crossover cable at the beginning. OK, my current situation is that in File Explorer under Network I can see the remote deskop (I'm trying to access) plus laptop1 (the local laptop) and remote laptop2. I now get a dialogue box for the desktop as well as for laptop2. I can access laptop2 by entering user name & password. But, when I use what I feel sure is the user name and password for the desktop, I get "\\pcname is not accessible. You might not have permission to use this network resource.". I thought I'd get access by merely entering the correct user name and password in the dialogue box. Desktop has Win10, laptop1 has Win10, laptop2 has Win7 on it.

 

Solved

I wouldn't, I',m pretty sure you're gonna need it for those XP PC's. SMBv1 has been patched for Win10 (don't know about XP) against WannCry and the risk is low on a home network IMO.

Yea, as I mentioned before this is known issue with Win10 and accessing network shares by hostname (i.e. \\PCNAME). By having SMBv1 installed it also installed the Computer Browser Service(it's tied to SMBv1). If you're using Static IP's for all your PC's and you can access shared PC's by \\ipaddress ... you can just map them by IP and bypass all this mess.

People have had success fixing this Win10 issue, but with varying methods.
1. Disabling IPv6 on ALL PC's
2. Renaming the problem PC's
3. Editing the hosts file on ALL PC's and mapping the IP to PCNAME ... Must have static IP's and if you have more than two PC's this can be a PITA ... personally if you have static IP's, just map the network shares by ip and avoid this unless necessary.
4. Enabling SMBv1 (which you've already done)

Note: Since HomeGroups have been removed from Win10. You might want to consider leaving any WinXP HomeGroups you've created and disable the two HomeGroup Services .. if you haven't done so already. I really don't know if/how this affects the Win10 accessing shares by \\PCNAME.