- Thread Author
-
- #1
One laptop can not access a properly shared folder on a Host system.
Host Name: akl4
Other Laptops, using WiFi, can access akl4
Desktops, using E-Net, can access akl4
All laptops and desktops are using Windows (10/11)
The host system is a desktop with Win 10
The user system is a laptop with Win 11
Again: This laptop is the only system (win 11) that cannot access the host.
Any suggestions?
Host Name: akl4
Other Laptops, using WiFi, can access akl4
Desktops, using E-Net, can access akl4
All laptops and desktops are using Windows (10/11)
The host system is a desktop with Win 10
The user system is a laptop with Win 11
Again: This laptop is the only system (win 11) that cannot access the host.
Any suggestions?
Solution
Hey akl80537, It sounds like you've got a bit of a rogue laptop on your hands! Let’s see if we can round up this outlier and get it back in the fold. Here are some steps to troubleshoot and potentially resolve the issue:
1. Verify Network Discovery and Sharing Settings:
- On the Laptop (Win 11):
- Open Settings > Network & Internet > Advanced network settings.
- Click on Advanced sharing settings.
- Ensure that Network discovery is turned on.
- Ensure that File and printer sharing is enabled.
2. Check Hostname Resolution:
akl4. []Open Command Prompt and run...
- Joined
- Mar 14, 2023
- Messages
- 97,035
Hey akl80537, It sounds like you've got a bit of a rogue laptop on your hands! Let’s see if we can round up this outlier and get it back in the fold. Here are some steps to troubleshoot and potentially resolve the issue:
1. Verify Network Discovery and Sharing Settings:
- On the Laptop (Win 11):
- Open Settings > Network & Internet > Advanced network settings.
- Click on Advanced sharing settings.
- Ensure that Network discovery is turned on.
- Ensure that File and printer sharing is enabled.
2. Check Hostname Resolution:
akl4. []Open Command Prompt and run:[]If it fails, try pinging the IP address directly ofCode:sh ping akl4akl4to rule out DNS/NetBIOS issues.3. Credentials Issues:
[]Ensure that the laptop has the correct credentials to access the shared folder. []Go to Control Panel > Credential Manager and ensure that there are no saved incorrect credentials for the host machine (akl4).4. SMB Protocol Issues:
[]Make sure that the SMB protocol version used byakl4is compatible with the laptop running Win 11. Ensure SMB 1.0/CIFS File Sharing Support is enabled if your network requires it (although this is a security risk and generally not recommended).5. Network Profiles:
[]Your laptop might be on a Public network profile instead of Private. []Go to Settings > Network & Internet > Status > Change connection properties. []Ensure it is set to Private.6. Firewall/Antivirus:
[]Temporarily disable any third-party antivirus or firewall software on the laptop and see if it resolves the issue. []Ensure Windows Firewall allows File and Printer Sharing:- Open Windows Security > Firewall & network protection.
- Click on Allow an app through firewall and check that File and Printer Sharing is allowed on private networks.
7. Group Policy (for advanced users):
- Computer Configuration > Administrative Templates > Network > Lanman Workstation.
8. Share Permissions & Security:
[]Double-check the specific shared folder's permissions onakl4:- Right-click the shared folder > Properties > Sharing tab > Advanced Sharing.
- Ensure appropriate permissions (
Everyonewith at least read access).
9. Network Reset:
[]A more drastic step, but resetting network settings can sometimes clear up weird discrepancies. []Go to Settings > Network & Internet > Status, scroll down to Network reset.10. Logs & Error Messages:
[]Try accessing the shared folder from the laptop and note any error messages. []Check event viewer (Win+X > Event Viewer) for any logs under Windows Logs > System or Security. By following these steps, you should be able to isolate where the issue lies. Let us know if any specific step resolves the problem or if you need further insight into any of these troubleshooting steps. There is hope for that pesky laptop yet! Good luck, and happy troubleshooting!
- Thread Author
-
- #3
Step 2 says to Ping akl4. Failed
IF failed, Ping 192.168.1.67 Works!
Added akl4 to Windows Credentials
After adding the Windows Credentials, I was able to connect to akl4.
Can you tell me why I had to add the credentials for akl4?
I did not have to add the credentials for the IP address.
Thank you very much for your help.
Similar threads
- Solved
- Replies
- 1
- Views
- 2K