Hi All,
I've been having an entertaining time trying to get a KM C309 to save to a Samba share on an Ubuntu 20 LTS server running Samba 4.11.6. The share has been set up with a user specific to the copier and the permissions set to give it full control. In order to test the permissions on the share, I have set up an account called Copier on the server, and have logged into on of the office PCs which allows me to create, edit and delete files in that share. If I then go to the copier, it goes through the motions of scanning before returning a server connection error.
To summarise the situation, I have checked the following:
Copier end:
The default domain name is correct
The IP address of the DNS server is the Samba DC
WINS is enabled and the IP of the DC is entered
The setup has been tried with both IP address and hostname with the hostname in lower and upper case
The username and password are both correct for the account (copied and pasted from Notepad into the copier and AD Users interface)
Both NTLMv1 and V2 are enabled as well as SMB1/2
Server end:
The ports listed in Microsoft's SMB networking documentation are all open
The desktop PCs can all access the samba share and have read/write access, they can access AD shared printers
The smb.conf file contains a valid users entry that includes both the Copier user and its group.
Wins is enabled in SMB.conf
There are no mentions in the firewall log of packets being dropped, nor connection errors relating to the copier.
So, my question is, are there any freaky ports that I'm unaware of or a more detailed error log on the copier that I can access to try and determine where it's going pear shaped?
Thanks in advance,
Jools
I've been having an entertaining time trying to get a KM C309 to save to a Samba share on an Ubuntu 20 LTS server running Samba 4.11.6. The share has been set up with a user specific to the copier and the permissions set to give it full control. In order to test the permissions on the share, I have set up an account called Copier on the server, and have logged into on of the office PCs which allows me to create, edit and delete files in that share. If I then go to the copier, it goes through the motions of scanning before returning a server connection error.
To summarise the situation, I have checked the following:
Copier end:
The default domain name is correct
The IP address of the DNS server is the Samba DC
WINS is enabled and the IP of the DC is entered
The setup has been tried with both IP address and hostname with the hostname in lower and upper case
The username and password are both correct for the account (copied and pasted from Notepad into the copier and AD Users interface)
Both NTLMv1 and V2 are enabled as well as SMB1/2
Server end:
The ports listed in Microsoft's SMB networking documentation are all open
The desktop PCs can all access the samba share and have read/write access, they can access AD shared printers
The smb.conf file contains a valid users entry that includes both the Copier user and its group.
Wins is enabled in SMB.conf
There are no mentions in the firewall log of packets being dropped, nor connection errors relating to the copier.
So, my question is, are there any freaky ports that I'm unaware of or a more detailed error log on the copier that I can access to try and determine where it's going pear shaped?
Thanks in advance,
Jools
Comment