![]() ![]() NetBIOS is old and rubbish so I have no idea why DSM wants to play this way but this recent errata may help explain your issues. I am currently experimenting with killing DSM services (synosamba) and have gained control of almost all the recent DSM NetBIOS madness but with some impact to macOS smbutil. Something has changed in the DSM7 network stack and it isn't pretty. ![]() SMB_ENCRYPT_ALGORITHMS AES_256_GCM_ENABLED SMB_ENCRYPT_ALGORITHMS AES_256_CCM_ENABLED SMB_ENCRYPT_ALGORITHMS AES_128_GCM_ENABLED ![]() SMB_ENCRYPT_ALGORITHMS AES_128_CCM_ENABLED They are full-fat NetBIOS packets (1514 bytes) at a machine-gun rate: My primary NAS (Rivendell) is continually broadcasting NetBIOS Session Service packets at clients (MacBook Pro over wifi in this example). The Wireshark screenshot below show the magnitude of the issue. Unhelpfully, macOS lists this inbound traffic under kernel_task, so no clues to its actual purpose or source. Not good at all for wired network performance and a kicking for wifi. My symptoms included an unexpected amount of network traffic, including over wifi APs, to clients that have no shares mounted, on an almost continuous basis. I have also helped many other macOS / Synology users to fully realise the capability within DSM and macOS.īut I have been shaken from my nirvana by inexplicable NetBIOS issues, even though my tuned macOS SMB config and DSM settings should preclude anything to do with SMB 1 or NetBIOS in any way. Type netsh int IP reset C:resetlog.txt in the Command Prompt shell, and then press the Enter key. Right click on Command Prompt and select Run as Administrator. I'm not sure if my contribution will help as my network is almost exclusively macOS and until the most recent DSM7 update everything worked flawlessly as my SMB configurations were carefully tuned and honed to perfection. Reinstall and reset TCP/IP (Internet Protocol) for Windows 7 (32 and 64): Click on Start button. Issue this command: netsh int ip reset logfilename, where logfilename is the name of a file where the actions taken. Obvious synonas and 192.168.1.100 are the same device, the ports are not in a bond, its all running through a 24 port gigabit switch, and I can immediately see a speed difference by using the device name vs its ip. I get similar results from different pcs on the lan, different files, and the results almost always the same, give or take a few mbs/sec. If it show synonas its about half speed.? any clue? This is a repeatable experiment. So if the window shows a direct ip in the location, the speed is nearly doubled. I get a maximum transfer of 60mb/sec ( \\synonas\temp)Ĭhange location in windows explorer to direct ip ( \\192.168.1.100\temp) I get 110mb/sec. In windows, open network, open icon for SYNONAS, open temp shared folder, now drag and drop 1.1gb file. If I use \\IP\folder its a faster transfer by about double! vs \\syno\folder I am getting different speeds copying files over the network on my Windows machines to my Nas. I am no network engineer, so I dont know if this is normal or not, but this is absolutely repeatable for me give or take a few mbs/sec. ![]()
0 Comments
Leave a Reply. |