Opened 3 years ago

Last modified 2 years ago

#315 new defect

Samba client and server on AcaOS 5.0.0 do not talk to each other

Reported by: Gerry Prosser Owned by:
Priority: blocker Milestone:
Component: Unknown Version: Server 3.6.x
Keywords: Cc:


Samba Client on laptop and Server on desktop, both with wired ethernet connections to central router. They can ping each other, by name and by number, yet samba will not connect.

Client ArcaMapper? Connections shows continual 'Refreshing Network' whilst on Server, 'Find SMB/CIFS Machines' says 'No machines responded on this subnet!'

Change History (4)

comment:1 Changed 3 years ago by Paul Smedley

You might need to enable NTLMv1 authentication on the second page of the ArcaMapper? settings

comment:2 Changed 3 years ago by Gregg Young

Actually with the current build support kerberos5, support NTLMv1 and support encryption are all on by default. Try turning them all off on the second page (you will need to do this each time you reopen ArcaMapper? as it reverts to the defaults). If this doesn't help try adding the server IP address and netbios name to the hosts file on the client. The hosts file is in the %etc% directory (default is Bootdrive:\MPTN\ETC\hosts). You may need to restart ArcaMapper? or even reboot to get all this to take effect. If it still fails try re-selecting Support NTLMv1.

comment:3 Changed 3 years ago by Gerry Prosser

Thanks, both, played with the authentication options but still no joy. I presume that 'netbios name' is the same as 'hostname ? They have always been set. Just noticed that you both refer to NTLMv1 .... but my ArcaMapper? says NTLMv2 ...... ?

comment:4 Changed 2 years ago by Lewis Rosenthal

Hi, Gerry...

NetBIOS name and hostname are not the same. Be sure to use the TCP/IP hostname (just type hostname at a prompt or look for the SET HOSTNAME param in CONFIG.SYS).

ArcaMapper uses Samba 4, which defaults to NTLMv2. Samba Server uses Samba 3.6, which defaults to NTLMv1. ArcaMapper has three checkboxes:

  • Support NTLMv1
  • Support Kerberos5
  • Support encryption

NTLMv1 is incompatible with Kerberos (different authentication entirely from NTLM) and encryption (supported in SMB3 and above). Uncheck all and just check the top one. If you still can't connect, perhaps Samba Server is configured for NTLMv2 (Samba 3.6 can do NTLMv2, just not by default). Uncheck Support NTLMv1 in ArcaMapper, and try that way.

Under no circumstances (in your configuration) should you check either Support Kerberos5 or Support encryption, as Samba 3.6 in Samba Server is not capable of either.

Note: See TracTickets for help on using tickets.