yoichiro / chromeos-filesystem-cifs

BSD 3-Clause "New" or "Revised" License
56 stars 21 forks source link

Cannot connect to Windows 2008R2 with domain account #132

Closed Sanmina closed 8 years ago

Sanmina commented 9 years ago

Hi I can connect to the 2008R2 Server using a local account created on the server, but when i try to use a domain account i get NT status logon failure. I know that i have the NTLMV authentication right. Can you point me in the right direction to start looking ?

Debug log: Looked up with chrome.mdns: Array[0] background.js:6388 connect background.js:6388 Header {types: Types, protocol: "SMB", command: 114, errorClass: 0, errorCode: 0…} background.js:6388 NegotiateProtocolRequest {types: Types, dialects: Array[0], dialects: Array[2]} background.js:6388 Packet {types: Types, data: ArrayBuffer, dataLength: 58, packetHelper: PacketHelper} background.js:6395 Negotiated with SMB2 background.js:6388 Asn1Obj {tag: 96, value: null, children: Array[2]} background.js:6395 SPNEGO = true background.js:6395 Supported mechType: 1.3.6.1.4.1.311.2.2.30 background.js:6395 Supported mechType: 1.2.840.6144018.1.2.2 background.js:6395 Supported mechType: 1.2.840.14532626.1.2.2 background.js:6395 Supported mechType: 1.2.840.14532626.1.2.2.3 background.js:6395 Supported mechType: 1.3.6.1.4.1.311.2.2.10 background.js:6388 Header {types: Types, protocol: "SMB", structureSize: 64, creditCharge: 0, channelSequence: 0…} background.js:6388 NegotiateResponse {types: Types, structureSize: 65, securityMode: 1, dialectRevision: 514, serverGuid: "����ԫwL�����w"…} background.js:6388 Header {types: Types, protocol: "SMB", structureSize: 64, creditCharge: 1, channelSequence: 0…} background.js:6388 SessionSetupRequest {types: Types, flags: 0, securityMode: 1, capabilities: 1, channel: 0…} background.js:6388 Packet {types: Types, data: ArrayBuffer, dataLength: 163, packetHelper: PacketHelper} background.js:6388 Header {types: Types, protocol: "SMB", structureSize: 64, creditCharge: 1, channelSequence: 22…} background.js:6388 Asn1Obj {tag: 161, value: null, children: Array[1]} background.js:6395 Response OID = 1.3.6.1.4.1.311.2.2.10 background.js:6395 NTLMSSP_NEGOTIATE_UNICODE: true background.js:6395 NTLMSSP_NEGOTIATE_OEM: false background.js:6395 NTLMSSP_REQUEST_TARGET: true background.js:6395 NTLMSSP_NEGOTIATE_SIGN: false background.js:6395 NTLMSSP_NEGOTIATE_SEAL: false background.js:6395 NTLMSSP_NEGOTIATE_DATAGRAM_STYLE: false background.js:6395 NTLMSSP_NEGOTIATE_LM_KEY: false background.js:6395 NTLMSSP_NEGOTIATE_NETWARE: false background.js:6395 NTLMSSP_NEGOTIATE_NTLM: true background.js:6395 NTLMSSP_NEGOTIATE_OEM_DOMAIN_SUPPLIED: false background.js:6395 NTLMSSP_NEGOTIATE_OEM_WORKSTATION_SUPPLIED: false background.js:6395 NTLMSSP_NEGOTIATE_LOCAL_CALL: false background.js:6395 NTLMSSP_NEGOTIATE_ALWAYS_SIGN: false background.js:6395 NTLMSSP_TARGET_TYPE_DOMAIN: true background.js:6395 NTLMSSP_TARGET_TYPE_SERVER: false background.js:6395 NTLMSSP_TARGET_TYPE_SHARE: false background.js:6395 NTLMSSP_NEGOTIATE_NTLM2: true background.js:6395 NTLMSSP_REQUEST_INIT_RESPONSE: false background.js:6395 NTLMSSP_REQUEST_ACCEPT_RESPONSE: false background.js:6395 NTLMSSP_REQUEST_NON_NT_SESSION_KEY: false background.js:6395 NTLMSSP_NEGOTIATE_TARGET_INFO: true background.js:6395 NTLMSSP_NEGOTIATE_128: true background.js:6395 NTLMSSP_NEGOTIATE_KEY_EXCH: false background.js:6395 NTLMSSP_NEGOTIATE56: false background.js:6388 Header {types: Types, protocol: "SMB", structureSize: 64, creditCharge: 1, channelSequence: 0…} background.js:6388 SessionSetupRequest {types: Types, flags: 0, securityMode: 1, capabilities: 1, channel: 0…} background.js:6388 Packet {types: Types, data: ArrayBuffer, dataLength: 458, packetHelper_: PacketHelper}

Sanmina commented 9 years ago

Do you have a Answer for the Problem??

yoichiro commented 9 years ago

@Sanmina Hey, I already read this issue, therefore, don't close and re-open for notifying!

yoichiro commented 9 years ago

@Sanmina Change the log level to Debug on the setting panel where clicking the gear icon on the login panel of this app, re-collect the console logs on the DevTools and post them here.

yoichiro commented 9 years ago

@Sanmina I found a bug regarding authentication. It was described at the following post: https://plus.google.com/u/0/+YoichiroTanaka/posts/EEJyicfnSqK I have already released a new version 2.4.0 including code to fix the problem.

Could you check whether or not this new version works on your environment?

yoichiro commented 9 years ago

@Sanmina Ping.

Sanmina commented 9 years ago

Thxs i will check it and let you know

yoichiro commented 8 years ago

@Sanmina Ping.

yoichiro commented 8 years ago

I close this issue, because @Sanmina didn't provide more information to fix this issue. Thank you for the reporting.