Leaderboard

2000 MTU is an abnormal network setting; 1500 bytes is standard (hence the Auto) and Jumbo frames are an optional standard (9000 bytes). Others should not think to adopt 2000 MTU as a solution. But this is exactly why I asked about Jumbo frames in the beginning. One of your other devices has a non-standard MTU setting for this change on DSM to have had any effect. The way this can be an issue is if you have a router in the data path and it is having to break up the packets and reform them because of dissimilar MTUs. This should not normally happen on a LAN (all devices should be able to directly deliver packets without a router) but if your network masks are wrong, it may force the packets into the router for processing when they would not normally be. Also something I asked about in the beginning. I'm bringing this up now, because there is still an underlying problem which has not been resolved, which you have now sidestepped by increasing MTU. And there is probably still a performance problem, but manifested in a different way. It may be negative impact to your NAS writes, or maybe your Internet upload speed is slower, etc. But it is possible that you might not care or the affected function is not heavily used by you. None of this is a DSM issue, it's simply basic networking. Really? Is that you being critical of this community, or you being critical of yourself? 'Cause we are all here for fun and pleasant exchanges, and we all participate for free.

Thanks for pointing me to the right place. I got the card to function. I will just briefly recap what I did that worked for me so that others that might encounter a similar issue knows what to do. Pre-requisite: Set MAC1-MAC4 in grub file (For my use case) 1. SSH into the NAS and type the following. 2. Look for NIC in question. In my case a X540-T2 with 2 ports, so it showed up as "ixgbe" 0000:01:00.0 Class 0200: Device 8086:1528 (rev 01) Subsystem: Device 15d9:0734 Kernel driver in use: ixgbe 0000:01:00.1 Class 0200: Device 8086:1528 (rev 01) Subsystem: Device 15d9:0734 Kernel driver in use: ixgbe 3. Since the card showed up with the correct drive loaded. I proceeded to modify the synoinfo.conf (in /etc AND /etc.defaults) Change maxlanport from 2 to 8 Original maxlanport="2" Modified maxlanport="8" Added the followings to the end eth4_mtu="1500" eth5_mtu="1500" eth6_mtu="1500" eth7_mtu="1500" 4. Save and rebooted the device. After performing these steps, I got X540-T2 to function. Results below: Hopefully somebody will find my recap useful. Thanks IG-88 for the prompt reply.

Hello again! It seems that I have found the sollution after all. After looking for any "BACKUP" entry in any file on the DSM through the console ( find / -type f -exec grep -H 'BACKUP' {} \; ) I found 2 refferences to the mentioned name in the /etc/samba/smb.conf file. [BACKUP] invalid users=nobody,nobody valid users=nobody,nobody comment="Backup D1" path=/volume3/BACKUP guest ok=yes browseable=yes fileindex=no mediaindex=no edit synoacl=yes win share=yes skip smb perm=yes enable recycle bin=no recycle bin admin only=no hide unreadable=no ftp disable list=no ftp disable modify=no ftp disable download=no read list=nobody,nobody write list=nobody,nobody writeable=yes [BACKUP 2] invalid users=nobody,nobody valid users=nobody,nobody comment="Backup disk 2" path=/volume1/BACKUP 2 guest ok=yes browseable=yes fileindex=no mediaindex=no edit synoacl=yes win share=yes skip smb perm=yes enable recycle bin=no recycle bin admin only=no hide unreadable=no ftp disable list=no ftp disable modify=no ftp disable download=no read list=nobody,nobody write list=nobody,nobody writeable=yes I then tried creating a new shared folder, and found out that there are 2 files that store information about the current SMB shares, the "smb.conf" and "smb.share.conf". But the newly created file is only visible in the smb.share.conf file. The other file smb.conf was probably the file used in the previous version of DSM. (In my case DSM 5.2) So it seems that DSM reads the samba configuration from both files, but only edits one of them. After I removed the "BACKUP" and "BACKUP2" from the smb.conf file, both of these shared folders were no longer visible on any client using samba/smb protocoll. I`m not sure if this is just a local bug on my DSM, but if not, i immagine that this will happen to a lot of people when they try to delete a shared folder that was created on a older version of the DSM. Hope this helps someone. @admins: Not sure how i can mark this topic as solved, so could you please do it? Thanks!