Open wmunyan opened 4 years ago
Judging from the logs, the file did indeed transfer successfully, can you confirm?
The exception happens in the packetreader, after an SMB_CLOSE was sent. Somehow the connection is immediately dropped on the remote side is what my guess is. Can you look at the server logs to see whether anything can be learned from those?
The file doesn't transfer successfully and the application exits. There should be a subsequent application log message indicating the file was copied and the number of bytes. The SMB connection isn't supposed to be closing after this one file is transferred, either - there are another 4 or 5 files to be copied onto the share.
Where can I look in server logs to find further information? Event viewer? The system being connected to is a Windows Server 2019.
Thanks again!
UPDATE: I'm trying to work with folks to check server logs and get back to me. Hopefully there will be more to follow to detail the issues.
Great, let me know whether you've learned anything from there.
It fails when it sends the SMB2_CLOSE Message which closes the filehandle and finishes the transfer.
Hello, I am using v0.8.0 of your library and am running into an issue. Authentication seems to execute successfully, the SMB share creation indicates success as well. However, I am using the
SmbFiles.copy
method to move a file from my local machine to the SMB share and receive the following stack trace:As far as I can tell, permissions are correct on the share and I am authenticating as a member of the Administrators group.
The negotiated connection info looks like this:
Any ideas on causes of this issue? I've tried other folders on the same box to no avail. The machine is a domain controller, if that makes a difference. Thanks for any help!