windows can’t communicate with the device or resource
Cause of windows can’t communicate with the device or resource
We will address the issue of Windows being unable to communicate with the device or resource in this blog. The user reinstalled Ubuntu 16.04 Desktop 32bit on an outdated laptop and set up Samba in line with the directions. When attempting to connect from a Windows 10 or Windows 7 PC, we get the following message: Windows cannot access the object or resource (192.168.1.50) The resource is reachable but does not respond to connection requests.
Solution
The problem is that Windows did not ask for my samba user credentials; instead, it merely generated the error 0x80070035. The request that follows can be used to solve this:
- Access “This PC”
- Simply select “Map network drive.”
- Create a folder called “samba server IP share name”.
- Ensure that the option to “Connect using alternate credentials” is chosen.
- Finish
SMB v1 or a change to the registry are not required to fix this issue with Windows 10 and Ubuntu 20.04 Focal Fossa; only a few locations in /etc/samba/smb.conf need to be changed.
passdb backend = tdbsam
security = user
In Windows 10, you should modify this by going to Computer Configuration -> Administrative Templates -> Network -> Lanman Workstation -> Enable Insecure Guest Logon – Enabled (search in Windows).
[global]
client min protocol = SMB3
client max protocol = SMB3
Also Read: Consider evaluating a polynomial