Solved Backup to SMB using domain credentials when DNS of 3cx is google

[Alphabetic]

Is it possible to backup to an SMB share this way?

Got a server 2016 share and cannot put in settings in a way that will allow.

Im getting invalid credentials.

This is a DC also.

A bit like this but apparently was addressed:

https://www.3cx.com/community/threads/smb-backup-location.70518/

 

[JohnS_3CX]

Hi @kieferschild

Are you seeing traffic going to the SMB server when this error message appears?

 

[Lee Cramman]

How are you formatting the credentials?

 

[SteveITS]

I would expect the DNS should only matter to look up the server name so if you're using an IP that shouldn't apply at all.

This setting was enabled in the Feb. updates, might be worth reviewing if those were installed: https://support.microsoft.com/en-us...020-1472-f7e8cc17-0309-1d6a-304e-5ba73cd1a11e

 

[Lee Cramman]

I would expect the DNS should only matter to look up the server name so if you're using an IP that shouldn't apply at all.

This setting was enabled in the Feb. updates, might be worth reviewing if those were installed: https://support.microsoft.com/en-us...020-1472-f7e8cc17-0309-1d6a-304e-5ba73cd1a11e

I've seen Windows server get upset when using the format [email protected] rather than username@domainname or domainname\username. Given the server is a DC this shouldn't be the case here but I instinctively avoid IP addresses in credentials as I've come across quite a few occasions where switching to domain name fixed a credential problem.

The other thing I've come across across a few times is a mismatch of SMB versions. e.g. DC group policy requires a higher SMB version (3) than browsing machine (debian) is capable of.

I've no specific examples of this as a 3CX / debian problem, it's more stuff I've generally come across in my previous life as a Windows Admin so don't disappear down a rabbit hole on the basis of the potentially out-of-date musings I've made!

 

[Alphabetic]

Hi All

Server is seeing the requests but apparently its not receiving the credentials.

SMB Session Authentication Failure

Client Name: \\192.168.183.1
Client Address: 192.168.183.1:35820
User Name:
Session ID: 0x24002A800000D
Status: The attempted logon is invalid. This is either due to a bad username or authentication information. (0xC000006D)
SPN: session setup failed before the SPN could be queried
SPN Validation Policy: SPN optional / no validation

Guidance:

You should expect this error when attempting to connect to shares using incorrect credentials.

This error does not always indicate a problem with authorization, but mainly authentication. It is more common with non-Windows clients.

This error can occur when using incorrect usernames and passwords with NTLM, mismatched LmCompatibility settings between client and server, an incorrect service principal name, duplicate Kerberos service principal names, incorrect Kerberos ticket-granting service tickets, or Guest accounts without Guest access enabled

 

[Alphabetic]

How are you formatting the credentials?

domain\username

 

[Alphabetic]

Alright boys and girls it was as firewall issue on the server, all sorted now. thanks for replying.