NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ant
Sep 21, 2021Prodigy
W10 unable 2 reconnect to my 12 yrs. old Linux (Debian Jessie v8) PC's Samba after rebooting Orbi.
This is with network cables with static IP addresses. I have to reboot my 64-bit W10 Pro. PC to make it work again. I am have all the updates for everything including Orbi RBK753S-100NAS router's.
Does anyone have this problem too and know how to fix it?
Thank you for reading and hopefully answering soon. :)
4 Replies
- titaniumrx8Apprentice
ant wrote:This is with network cables with static IP addresses. I have to reboot my 64-bit W10 Pro. PC to make it work again. I am have all the updates for everything including Orbi RBK753S-100NAS router's.
Does anyone have this problem too and know how to fix it?
Thank you for reading and hopefully answering soon. :)
Can you ping the Linux box from the W10 PC?
If you can ping it then the issue is probably a windows setting ie network discovery or UPNP.
- antProdigy
titaniumrx8 wrote:
ant wrote:This is with network cables with static IP addresses. I have to reboot my 64-bit W10 Pro. PC to make it work again. I am have all the updates for everything including Orbi RBK753S-100NAS router's.
Does anyone have this problem too and know how to fix it?
Thank you for reading and hopefully answering soon. :)
Can you ping the Linux box from the W10 PC?
If you can ping it then the issue is probably a windows setting ie network discovery or UPNP.
Yes. Even SSH2 still connects and works. It's just file sharing (Samba) stops working after the router is rebooted.
- titaniumrx8Apprenticeant
Yes. Even SSH2 still connects and works. It's just file sharing (Samba) stops working after the router is rebooted.
I use a different linux distro but a recent linux update killed Samba for me also. I had to change the SMB version on the server to SMB3 which is the minimum required for W10. For some reason the linux update reverted to SMB1.
- antProdigy
Disabling and re-enabling my network device fixes it without needing to reboot my PC. Still weird/odd.