none
Can Ping but can't access shared folder RRS feed

  • Question

  • 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

    Thursday, June 15, 2017 11:13 AM

All replies

  • 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.

    Thursday, June 15, 2017 12:21 PM
  • 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

    Friday, June 16, 2017 2:21 AM
  • 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.


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, June 16, 2017 10:17 AM
    Moderator
  • 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

    Friday, June 16, 2017 11:07 AM
  • Hi Surbaki,

    When did the issue occur? After you performed all the actions I suggested 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.


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, June 27, 2017 10:24 AM
    Moderator
  • Try to run first and make sure the user has the correct permissions to access the share. 

    net use * /delete

    Tuesday, June 27, 2017 11:15 AM
  • 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

    Wednesday, February 21, 2018 1:21 PM
  • you must set password for user in host machine 192.168.1.5
    Friday, August 30, 2019 11:59 PM