-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, Jun 06, 2017 at 11:11:32AM +0100, Rodolfo Medina wrote:
[...] [Case 1:] > >>> $ smbclient -L 192.168.0.1 > >>> WARNING: The "syslog" option is deprecated > >>> Enter rodolfo's password: > >>> Connection to 192.168.0.1 failed (Error NT_STATUS_IO_TIMEOUT) [...] [Case 2:] > >>$ smbclient -L 192.168.1.2 > >>WARNING: The "syslog" option is deprecated > >>Enter rodolfo's password: > >>Domain=[WORKGROUP] OS=[Unix] Server=[Samba 2.2.12] > >>Server requested LANMAN password (share-level security) but 'client lanman > >> auth = no' or 'client ntlmv2 auth = yes' > >>tree connect failed: NT_STATUS_ACCESS_DENIED [...] > All right, but to do then now...? Why no response comes from 192.168.1.1? To be fair, a response *is* coming from 192.168.1.1 (case 2 above), and this response is "NO, you are not allowed"). As opposed to case 1, where the client gives up (...TIMEOUT) after a while of silence. So you'll have to fix the permissions on your CIFS server now. No, sorry, I have no idea on how to do that, but perhaps the router's web "GUI" has something on this. Cheers - -- tomás -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlk2ikQACgkQBcgs9XrR2kYsCwCeO0ZRJbdUair97pDDcg4jGGiw 0nsAniJSn3HMYuWsoNrYIjlJjMS858Ek =VpFr -----END PGP SIGNATURE-----
