Timeline for Samba share across two subnets
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 6, 2018 at 9:06 | history | edited | dice | CC BY-SA 4.0 |
added 182 characters in body
|
| Dec 30, 2017 at 1:59 | answer | added | user857430 | timeline score: -3 | |
| Jul 21, 2017 at 10:15 | comment | added | dice | The firewall was the problem. | |
| Feb 21, 2017 at 14:41 | comment | added | dice | @djsmiley2k I tried this, but it doesn't help. But I think I found the problem: The router firewall may block the ports used by SMB (135 - 139 and 445). I will give an update when IT opened the ports. Thanks | |
| Feb 20, 2017 at 13:57 | comment | added | djsmiley2kStaysInside | I think you need to setup the devices in subnet B to use the Samba server, as a WINS server. You can do this by assigning the value via DHCP, or manually. I'm leaving this as a comment as I'm not 100% sure and can't test currently. | |
| Feb 20, 2017 at 13:55 | history | asked | dice | CC BY-SA 3.0 |