Cant connect to Network share get error 0x80004005

Anonymous
2018-04-11T22:37:56+00:00

I can't connect to a file server on our network.

I do this by typing

\192.168.22.10\ into the entry box on windows file manager.

For one sever only I get an error box pop up that says

Windows can not access \192.168.22.10

Check the spelling of the name. Otherwise there might be a problem with your network.  To try to identify and resolve network problems, click Diagnose.

Error code:0x80004005 Unspecified error

It has a button to click to run a troubleshooter that tells me "Troubleshooting couldn't identify the problem"

I can connect to two other file servers on our network at different IP addresses using the same method.

I used to be able to connect to the .22.10 box but now I can't.

I can ping the 192.168.22.10 box and get a reply.

I can use my web browser to see a web page that the 192.168.22.10 box serves out

I can use a different PC on the same LAN as my normal PC and connect to the 192.168.22.10 box.  It prompts me for a user name and password as one would expect and then connects.

I have tried turning off windows defender firewall - No difference.

The common problem seems to be my pc.

I am running a Toshiba Z20.  Win 10 Pro.  Registered and up to date.

Help!

Windows for home | Windows 10 | Internet and connectivity

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} votes
Accepted answer
  1. Anonymous
    2018-04-12T03:03:44+00:00

    Ah ha Fixed

    Start>Control Panel>Programs and Features

    Click "Turn Windows features on or off"  (Left hand side).

    Scroll down to SMB 1.0/CIFS File Sharing Support

    Tick the SMB 1.0/CIFS Client

    Untick SMB 1.0/CIFS Automatic Removal and

    Untick SMB 1.0/CIFS Server

    Note SMB 1.0 is apparently a very insecure protocol and should not be used.

    Off to ask the network guy to upgrade the server


    Moderator's note:

    Please note that SMBv1 protocol is not installed by default in Windows 10 V1709 or later.  Microsoft publicly deprecated the SMBv1 protocol back in 2014.

    For details, refer this support article: https://support.microsoft.com/en-us/help/4034314/smbv1-is-not-installed-by-default-in-windows


    382 people found this answer helpful.
    0 comments No comments

2 additional answers

Sort by: Most helpful
  1. Anonymous
    2018-04-11T22:57:17+00:00

    Try changing your network profile to private:

    https://www.groovypost.com/howto/change-network...

    Open Start > Settings > Network & Internet > Status

    Scroll to the bottom

    Click Network and Sharing Center

    Click Change advanced sharing settings

    Expand All Networks

    Under Password protected sharing

    Switch between 'Turn on password protected sharing and Turn off password protected sharing'

    Then choose 'Turn off password protected sharing'

    Then click 'Save changes'

    Try again.

    17 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2018-04-12T00:15:23+00:00

    I checked thewireless network profile as described above and it was already set to private.

    I followed the instructions and turned the password protected sharing on and off.  I tried several times and it made no difference.  (I don't see its related as that seems to be related to other people connecting to my computer)

    I then tried to connect by ethernet cable.  I switched off the wireless.

    (The Toshiba Z20 laptop has an ethernet connector)

    I get a different error it says:

    "Windows can't find '\192.168.22.10'.  Check the spelling and try again."

    I also double checked that I could still connect to everything else with this wired connection and I could.  That is I could see the internet and reply here.  I could connect to the other two servers and I could ping the 22.10 box and see it's web page on my browser.

    10 people found this answer helpful.
    0 comments No comments