Print

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

[felipemb09]

Hi to all,

I have a problem a long time ago... i searching in Google a solution but nothing works!

The problem is when you try to copy files to the NAS DNS-320 approx 200GB or more! the NAS show the next error in the logs:

CIFS: [10.0.0.2] closed the connection to service [Volume_1].

It is necessary to reboot to bring it back to operate normally but after a while back and it happens. I have disabled "oplocks" but the problem remains!

I appreciate a help with this problem that every day looking for a solution without success!

Thanks! 

This is the full log:

Feb 26 05:47:59 nas smbd: CIFS: [10.0.0.2] connected to [Volume_1] as user [nobody].
Feb 26 05:48:40 nas smbd: CIFS: [10.0.0.2] closed the connection to service [Volume_1].
Feb 26 05:49:42 nas smbd: CIFS: Authentication for user [Administrador] has FAILED.
Feb 26 05:49:45 nas smbd: CIFS: [10.0.0.2] connected to [Volume_1] as user [nobody].
Feb 26 05:50:17 nas smbd: CIFS: [10.0.0.2] closed the connection to service [Volume_1].
Feb 26 05:50:44 nas fan_control: Set Fan Speed To "STOP".
Feb 26 05:51:31 nas smbd: CIFS: Authentication for user [Administrador] has FAILED.
Feb 26 05:51:34 nas smbd: CIFS: [10.0.0.2] connected to [Volume_1] as user [nobody].
Feb 26 05:52:08 nas smbd: CIFS: [10.0.0.2] closed the connection to service [Volume_1].
Feb 26 05:53:18 nas smbd: CIFS: [10.0.0.2] closed the connection to service [Volume_1].
Feb 26 05:53:24 nas smbd: CIFS: Authentication for user [Administrador] has FAILED.
Feb 26 05:53:26 nas smbd: CIFS: [10.0.0.2] connected to [Volume_1] as user [nobody].
Feb 26 05:55:11 nas smbd: CIFS: Authentication for user [Administrador] has FAILED.
Feb 26 05:55:13 nas smbd: CIFS: [10.0.0.2] connected to [Volume_1] as user [nobody].
Feb 26 05:55:23 nas smbd: CIFS: [10.0.0.2] closed the connection to service [Volume_1].
Feb 26 05:56:56 nas smbd: CIFS: Authentication for user [Administrador] has FAILED.
Feb 26 05:56:57 nas smbd: CIFS: [10.0.0.2] connected to [Volume_1] as user [nobody].
Feb 26 05:57:06 nas smbd: CIFS: [10.0.0.2] closed the connection to service [Volume_1].
Feb 26 05:57:07 nas smbd: CIFS: [10.0.0.2] closed the connection to service [Volume_1].
Feb 26 05:57:50 nas smbd: CIFS: [10.0.0.2] closed the connection to service [Volume_1].
Feb 26 05:58:43 nas smbd: CIFS: Authentication for user [Administrador] has FAILED.
Feb 26 05:58:45 nas smbd: CIFS: [10.0.0.2] connected to [Volume_1] as user [nobody].
Feb 26 06:00:33 nas smbd: CIFS: Authentication for user [Administrador] has FAILED.
Feb 26 06:00:35 nas smbd: CIFS: [10.0.0.2] closed the connection to service [Volume_1].
Feb 26 06:00:35 nas smbd: CIFS: [10.0.0.2] connected to [Volume_1] as user [nobody].
Feb 26 06:02:00 nas smbd: CIFS: [10.0.0.2] closed the connection to service [Volume_1].
Feb 26 06:02:16 nas smbd: CIFS: Authentication for user [Administrador] has FAILED.
Feb 26 06:02:18 nas smbd: CIFS: [10.0.0.2] connected to [Volume_1] as user [nobody].
Feb 26 06:04:08 nas smbd: CIFS: Authentication for user [Administrador] has FAILED.
Feb 26 06:04:10 nas smbd: CIFS: [10.0.0.2] connected to [Volume_1] as user [nobody].
Feb 26 06:05:16 nas smbd: CIFS: [10.0.0.2] closed the connection to service [Volume_1].
Feb 26 06:05:53 nas smbd: CIFS: Authentication for user [Administrador] has FAILED.
Feb 26 06:05:56 nas smbd: CIFS: [10.0.0.2] connected to [Volume_1] as user [nobody].
Feb 26 06:07:45 nas smbd: CIFS: Authentication for user [Administrador] has FAILED.
Feb 26 06:07:46 nas smbd: CIFS: [10.0.0.2] connected to [Volume_1] as user [nobody].
Feb 26 06:09:39 nas smbd: CIFS: Authentication for user [Administrador] has FAILED.
Feb 26 06:09:42 nas smbd: CIFS: [10.0.0.2] connected to [Volume_1] as user [nobody].
Feb 26 06:11:20 nas fan_control: Set Fan Speed To "LOW".
Feb 26 06:11:24 nas smbd: CIFS: [10.0.0.2] closed the connection to service [Volume_1].
Feb 26 06:11:29 nas smbd: CIFS: Authentication for user [Administrador] has FAILED.
Feb 26 06:11:32 nas smbd: CIFS: [10.0.0.2] connected to [Volume_1] as user [nobody].
Feb 26 06:13:16 nas smbd: CIFS: Authentication for user [Administrador] has FAILED.
Feb 26 06:13:32 nas smbd: CIFS: [10.0.0.2] connected to [Volume_1] as user [nobody].
Feb 26 06:13:32 nas smbd: CIFS: [10.0.0.2] closed the connection to service [Volume_1].
Feb 26 06:13:37 nas smbd: CIFS: [10.0.0.2] closed the connection to service [Volume_1].
Feb 26 06:14:47 nas smbd: CIFS: [10.0.0.2] closed the connection to service [Volume_1].
Feb 26 06:14:55 nas smbd: CIFS: [10.0.0.2] closed the connection to service [Volume_1].
Feb 26 06:14:56 nas smbd: CIFS: Authentication for user [Administrador] has FAILED

[ivan]

Tell us about your network.

1)  Are you using DHCP or fixed IP? 
2)  If DHCP what is the IP range?
3)  What router are you using?
4)  Are there any other devices on your network that could cause a conflict?
5)  What are you using to copy files to/from the NAS?

I am asking these questions because 10.0.0.2 is a rather strange IP address for the NAS (default 192.168.0.32) and I need to get a mental picture of your network be be able to have some idea of what might be going wrong.

[felipemb09]

Hi Ivan

Thanks for your reply...

1) IP for DHCP, the network is 10.0.0.0/24. The NAS IP: 10.0.0.56
2) Range 10.0.0.10 to 10.0.0.100
3) The IP is from Windows Server 2008 Service DHCP
4) The copy files is from Cobian Backup (Software)

The problem is rare because when i copy files small Example 6GB its no problem, but i need to realize a backup all days of 200GB approx. the NAS show the error : CIFS: [10.0.0.2] closed the connection to service [Volume_1].

Some days the copy files finished success! but the most of the days the problem it's present!

Can what be the problem?

Thanks again!

[ivan]

OK, another question.  If the DHCP range is 10.0.0.10 to 10.0.0.100  and the nas is 10.0.0.56 where does the 10.0.0.2 come from?

Are you doing full backups every day to get that 200 GB if so how do you store the historical versions?  We have clients that are large industrial concerns that might reach that for a full backup when we image their systems as well.

To try and solve the problem you need to find out what is using 10.0.0.2.  Since you are using windows download a copy of Netscan http://www.softperfect.com/products/networkscanner/ and use that to search your network and find the apparent rogue IP address that is closing down samba.  Once you know that we might be able to solve the problem.

I would think it would be better for you to do incremental daily backups, keep three days active and transfer anything beyond that to cold storage off site.  That way you can go back to an earlier version of documents etc. should the need arise.

[felipemb09]

Thank you Ivan for your reply

1. The IP address 10.0.0.2 is my Windows Server 2008 here is all the data
2. The full backup are approx. 800GB and the incremental start in 30GB, 50GB, 100GB, 200GB until 300GB and back to made a full backup (800GB)
3. All data transfer are made with Cobian Backup

At the beginning I had no problems but now the problem is recurrent. the NAS has a total capacity of 2TB and has 500GB free, the hard disk is well, I changed the network cable, I changed the switch port, but nothing has worked...

Do you have another idea?

Thanks!

[ivan]

OK, you have two fixed IP addresses 10.0.0.2, your server, and 10.0.0.56, your NAS.  Can I assume that you use a managed switch to oversee the network and if so what do its logs say about the traffic between server and NAS?

Another thing to look at any updates you have made to the server.  Is there anything that might interfere with CIFS/SMB?  We don't use windows here (our servers run WSeB and workstations are a mixture of WSeB client and OS/2 Warp 4, although we do have a VM win 7 we can use for testing).

My service manager said that with those sized daily backups you should be using a high speed storage array rather than a simple NAS box.  Our 24 workstations might, on the end of the month 'create all the paperwork', generate about 50 MB of incremental backup so I have to ask out of curiosity how are you managing your backups.  That leads to another thought - is there something you are trying to backup that interferes with the CIFS/SMB implementation on your server?  Either the server logs and/or the switch logs should show what point the data transfer fails.  Also, if Cobian Backup has logging you should enable that as well.

Sorry I can't be more helpful.