Can Ping but can't access shared folder - Windows 10 Networking
Can Ping but can't access shared folder - Windows 10 Networking
Dear All,
I can ping the server but I can't access the shared folder with error:
"Windows Cannot access \\192.168.1.5\Shared"
but if I check on 1.5 with net share, there are Shared Folder in net shared list.
My IP 192.168.1.14 and OS Windows 10 pro.
Firewall and anti virus both are turn off and Turn on file sharing also has been turn on.
how can I fix this problem?
Best regards,
Surbakti
Can Ping but can't access shared folder - Windows 10 Networking
You can try to check it from other pcs if it is accessible or not and if so then check the client system.
You can also check if they have joined to the same network or workplace.
Check to see if file and print share are allowed for all .
Try to restart the system .
If it does not fix them reset the password for the machine and do a reboot again.
Can Ping but can't access shared folder - Windows 10 Networking
Other PC is good, can browse and mapping drive to shared folder.
File and print share are allowed for all.
Before I change the password, I can connect to shared folder using server administrator password.
After I change the server password, I can't connect but I can ping the server.
Best Regards,
Surbakti
Can Ping but can't access shared folder - Windows 10 Networking
Hi Surbakti,
At first, please make sure you entered correct password when you access share folder. Try to share the folder with everyone.
How did you access the folder? From Windows Explorer directly or a map drive?
If you access from a map driver, try to run “net use * /d” to delete the mapped drive and re-map it again.
Clear the Credential manager from Control Panel\All Control Panel Items\Credential Manager.
Run the following command:
netsh int ip reset (reset ip settings)
netsh winsock reset (Reset Winsock Catalog)
Best regards,
Joy.
Can Ping but can't access shared folder - Windows 10 Networking
Now the problem is "The semaphore timeout period has expired"
I using \\192.168.1.5 and the error was "The semaphore timeout period has expired"
How to fixed that?
Best regards,
Surbakti
Can Ping but can't access shared folder - Windows 10 Networking
Hi Surbaki,
When did the issue occur? After youperformed all the actionsIsuggested right?
Is it available to access other share folder?
Are you using a wireless or LAN cable?
Try to update you network driver (Wireless network driver) to the latest from manufacturer website and check the issue again.
Bests,
Joy.
Can Ping but can't access shared folder - Windows 10 Networking
Try to run first and make sure the user has the correct permissions to access the share.
net use * /delete
Can Ping but can't access shared folder - Windows 10 Networking
I realize this reply come way too late but I recently ran into this problem and could not find a solution in any post I searched.
In the end I started reviewing all running services one by one and found that TCP/IP NetBIOS Helper Service was not running even though it was set to automatic (so red flag there); I tried to started and it failed with an error 1079.
It turned out a windows update switched the account running the service from localService to localSystem. Following the instructions on this link and starting the service fixed my issue:
https://support.microsoft.com/en-us/help/2478117/services-fail-to-start-and-you-receive-an-error-1079-on-a-computer-tha
Can Ping but can't access shared folder - Windows 10 Networking
Can Ping but can't access shared folder - Windows 10 Networking
I have exactly the same problem with a new install and reading this thread i remember about SMB.
Did you try to activate Windows features:
SMB 1.0/CIFS File Sharing Support
- SMB 1.0/CIFS Client
Can Ping but can't access shared folder - Windows 10 Networking
I have exactly the same problem with a new install and reading this thread i remember about SMB.
Did you try to activate Windows features:
SMB 1.0/CIFS File Sharing Support
- SMB 1.0/CIFS Client
This is exactly what I needed to do! Thank you!
Also this is not what I needed to do! SMB 1.0 is baaaad! Thank you for replying to this 3 year old thread just 4 days ago so I could fix this problem, haha.
We have a legacy application running on a Windows Server 2003R2 box, which only supports SMB 1.0. Looks like we're going to spend the day decommissioning this server and spinning up a new VM to migrate the legacy application over to!
