Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Drayoute]

Hello all,

after some research sessions, I decided to post a message on the forum.
To make it simple, I use the local backup in LAN mode to backup some folders on my PC.
Until now, the backup was working well. Then for no reason, the process went wrong.
Since then, the URL test has ended with an error.
I would like to point out that password-protected sharing is already disabled, and that I can access my folders from another PC on the network.
Only the 320LW is unable to communicate with these folders

If anyone has an idea for a solution to the problem.

Thank you in advance

Drayoute

[FurryNutz]

Link>Welcome!

• What Hardware version is your DNS? Look at the sticker behind or under the device.
• Link>What Firmware version is currently loaded? Found on the DNSs web page under status.
• What region are you located?

What Mfr and model is the main host router?

So you can access the folder on the DNS from one PC and not this one particular PC?

[Drayoute]

Hi,

What Hardware version is your DNS? Look at the sticker behind or under the device. A2
Link>What Firmware version is currently loaded? Found on the DNSs web page under status. 1.11
What region are you located? I'm from France
What Mfr and model is the main host router?  I have the router from my ISP Orange (France) with model livebox 3 FR (Sagemcom)

So you can access the folder on the DNS from one PC and not this one particular PC? I want to setup a local backup on LAN. But i can access the folder on my Pc i want to save. When i test the URL, test result = fail.

I have no problem accessing my NAS from my PC. The problem occurs only from the NAS interface to access the directory of my PC to be backed up

Thx for your help !

[ivan]

Sorry but a few more questions.

1) have you tried accessing a different directory on your computer from the NAS local backup page?

2) can you access the directories of another computer from the local backup page of the NAS?

3) what operating system do you use on your computers?

4) does the NAS have a fixed IP address?  If yes is that IP outside the DHCP range of the livebox (I can't remember if you can set the dhcp range on a livebox it has been a rather long time since I set one up)?

I ask those questions to try and determine if it is a NAS problem, a network problem or something else.
The usual cause of what you are seeing is a change of IP address for the target computer or lately win 10 doing stupid things with SAMBA/CIFS.
 

[Drayoute]

Hello Ivan,

1) have you tried accessing a different directory on your computer from the NAS local backup page? Yes, i tried to create new folder with access for everybody, doesn't work. I'm also sure that the authorized accounts on shared folders work. (This was the case before)

2) can you access the directories of another computer from the local backup page of the NAS? No, same issue

3) what operating system do you use on your computers? W10on my 2 computers

4) does the NAS have a fixed IP address?  If yes is that IP outside the DHCP range of the livebox (I can't remember if you can set the dhcp range on a livebox it has been a rather long time since I set one up)? They are on the same range (192.168.1.X)

For now, I would tend to think that the problem comes from Windows, since everything was working perfectly, and only windows was updated before encountering the problem.

[ivan]

From what you say I would agree with your assumption that win 10 is the problem.

I have friends that use win 10 on some of their computers that started having problems with SAMBA/CIFS.  We solved that problem by using the FTP server built into the NAS and FileZilla as the client on the computers (for that to work you need the NAS to be on a fixed IP address).  The other drawback is that it is not automated - you have to select what you need to copy to the NAS.  Their computers that don't have win 10 on them (win 7 Pro and Linux Mint) have continued working as normal with the net backup.

Sorry I don't have a magic wand that makes win 10 and most small NAS boxes work together - only Microsoft can do that if they ever decide to.

[FurryNutz]

Windows 10 Info:
http://forums.dlink.com/index.php?topic=65722.0

[Drayoute]

I have already seen this post and I have already checked these settings.
I will nevertheless test with a PC under Seven, and check if I have the patch presented in the second post.

Thanks for the help.

[pfmp]

Hi all,
I have the same problem but I'am not using W10. The NAS is giving allways error on the local backup for the PC (with Fedora), it fail's all the time, and before of August of 2019 it was working well.
Thanks in advance, thanks.

[ivan]

and before of August of 2019 - are you sure it was 2019?

That being said, were any changes to your computer (updates etc.), NAS or network made in August?

There are very few things that can stop a working backup system. 1) a change of router which changes the DHCP address range. 2) a change in the computer OS that changes the SMB/CIFS version to one incompatible with the NAS. 3) a NAS firmware update that didn't complete correctly.

The first two are the usual ones to look for - a router change may change the subnet from 192.168.0.X to 193.168.1.X or even start usinf IPv6 addresses which the NAS knows nothing about.  The OS change is what win 10 did and we all know the consequences of that.
 

[pfmp]

Hello ivan,
my mistake, 2018 August...
The network continous the same, the Fedora is the dhcp server, the network continous in 192.168.0.0/24.
The computer have updates since that time, but the configuration file of the samba server continous the same.
The NAS firmware as been update and rested to test...
Accessing the NAS by ssh, it can reach the folder on the Fedora share. But the Local Backup fails all the time. I'm somewhat lost with this problem.

Thnaks for the help.

[ivan]

Very odd indeed.  I am not familiar with Fedora, I have always used the IBM OS/2 since long before windows but I do have a couple of computers with Mint on them.  One thing I have noticed with Mint and the latest update is that it tries to use IPv6 addresses even though my network uses IPv4 which did cause problems with connecting to other computers and the NAS boxes on the network until I managed to force it back to using IPv4.  You might have the same problem since IPv6 appears to be incompatible with DHCP.