-
Notifications
You must be signed in to change notification settings - Fork 180
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
STATUS_SERVER_UNAVAILABLE - STATUS_OTHER(0xc0000466) #830
Comments
compared the debug logs between working and non-working share, What I am seeing is in non-working is "Signing with NTLM Extended Session Security" [main] DEBUG com.hierynomus.protocol.commons.socket.ProxySocketFactory - Connecting to server1.test.net |
IT team applied below patch and it resolved the issue. |
Hello,
Thank you for making this utility available. Have been using it for 1+year. 2 months back some changes were made on the networking side, vlan switch etc. What used to be 95% successful calls are now 50-60%. The error is 466. It's like pass,pass......fail, fail...pass,pass and so on. While researching, came across this similar issue here jborean93/smbprotocol#61. looking to see if you have any suggestions that I can try.
[main] INFO com.hierynomus.smbj.connection.PacketEncryptor - Initialized PacketEncryptor with Cipher << AES_128_GCM >>
[main] INFO com.hierynomus.smbj.connection.Connection - Successfully connected to: server
Exception in thread "main" com.hierynomus.mssmb2.SMBApiException: STATUS_OTHER (0xc0000466): Authentication failed for 'AD profile' using com.hierynomus.smbj.auth.NtlmSealer@1003cfeb
at com.hierynomus.smbj.connection.SMBSessionBuilder.setupSession(SMBSessionBuilder.java:154)
at com.hierynomus.smbj.connection.SMBSessionBuilder.setupSession(SMBSessionBuilder.java:152)
at com.hierynomus.smbj.connection.SMBSessionBuilder.establish(SMBSessionBuilder.java:119)
at com.hierynomus.smbj.connection.Connection.authenticate(Connection.java:202)
at CIFS_List_Dir_v2.main(CIFS_List_Dir_v2.java:175)
Thank you for your any input. Was using 0.13 version.
The text was updated successfully, but these errors were encountered: