Share folder access problem

Question

0.00/5 (No votes)

See more:

Hi Frnds

One of the pc having a shared folder that is working fine. My user often shutdown the pc when leaving from the office. But Next day, the share folder is not accessible and there is no ping between the computers. If I change the ip address to a different one, then it will work. This is a big headache for me and the users. Its a brand new pc. I am using kapersky end point security antivirus.

The error coming is

//An error occurred while reconnecting W: to \\192.168.0.233\sharefolder
Microsoft windows network: the network path was not found. This connection has not
been restored
//
Pls help me to resolve this

What I have tried:

Changed the IP address.. did not tried by disabling antivirus

Posted 30-Apr-18 19:56pm

jay krishnan

Updated 2-May-18 10:51am

v3

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Accepted Answer · 2018-04-30T22:25:00

Solution 1

The simple - and rather obvious - solution is this: don't use IP addresses to establish your shares, use the MachineName instead:

\\MYOTHERPC\sharefolder

Since most DHCP controllers use dynamic IP addressing by default, relying on a specific IP address is going to cause problems like this quite often.

Posted 30-Apr-18 22:25pm

OriginalGriff

Comments

jay krishnan 2-May-18 1:14am

Hi..Thanks for your help.I tried by estabilishing sharing using the pc name also. But the same result again.The error replaced with pc name instead of ip address. Is there anything else i can try. The host pc having windows 10 and client pc having windows 7.

This started happening after I changed the old computer to a new one.

**`Randor`** · Accepted Answer · 2018-05-02T10:52:00

Hi,

"Windows 10" and "Windows 7" are probably using completely different SMB protocols. The SMBv1 protocol has been deprecated since 2015.

The Deprecation of SMB1[^]

Which version of the SMB protocolare you using?[^]

Make sure both machines are using the same SMB version. Recent updates to Windows 10 have disabled the SMBv1 protocol.

SMBv1 is not installed by default in Windows 10 Fall Creators Update and Windows Server, version 1709 and later versions[^]

I do not recommend enabling SMBv1.

Best Wishes,
-David Delaune