Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

RST packets sent by both client and server during file transfer

I am trying to troubleshoot why a file upload from a client to Linux server fails in our network. From the workstation, I want to upload a file to the server, so I run the command

scp scan-20170710.pdf [email protected]:/tmp/

After entering the password, I get the message: "packet_write_wait: Connection to 10.11.12.26 port 22: Broken pipe"

I tried capturing the communication between the client and the server. There are no hops between the two, only two switches and an AP. I am linking the server side capture and the client side capture.

The client and the server seem to communicate perfectly fine until suddenly they start sending RST packets to each other. What seems also odd to me is the fact that each RST packet can be seen on the receiving side but not on the sending side.

The file that I am uploading from the workstation is 1.8 MB in size. If I try uploading a smaller file ~100 kB, the issue never occurs. In addition, this error never occurs if I download a file bigger than 1 MB from the server.

I have been looking online for potential solutions, but everything seems to be linked to the timeout time of the session being too short, which I don't think is the problem in this case because the error message pops up less than a second after I enter the password.

Has anyone ever seen a similar case?

RST packets sent by both client and server during file transfer

I am trying to troubleshoot why a file upload from a client to Linux server fails in our network. From the workstation, I want to upload a file to the server, so I run the command

scp scan-20170710.pdf [email protected]:/tmp/

After entering the password, I get the message: "packet_write_wait: Connection to 10.11.12.26 port 22: Broken pipe"

I tried capturing the communication between the client and the server. There are no hops between the two, only two switches and an AP. I am linking the server side capture and the client side capture.

The client and the server seem to communicate perfectly fine until suddenly they start sending RST packets to each other. What seems also odd to me is the fact that each RST packet can be seen on the receiving side but not on the sending side.

The file that I am uploading from the workstation is 1.8 MB in size. If I try uploading a smaller file ~100 kB, the issue never occurs. In addition, this error never occurs if I download a file bigger than 1 MB from the server.

I have been looking online for potential solutions, but everything seems to be linked to the timeout time of the session being too short, which I don't think is the problem in this case because the error message pops up less than a second after I enter the password.

Has anyone ever seen a similar case?

RST packets sent by both client and server during file transfer

I am trying to troubleshoot why a file upload from a client to Linux server fails in our network. From the workstation, I want to upload a file to the server, so I run the command

scp scan-20170710.pdf [email protected]:/tmp/

After entering the password, I get the message: "packet_write_wait: Connection to 10.11.12.26 port 22: Broken pipe"

I tried capturing the communication between the client and the server. There are no hops between the two, only two switches and an AP. I am linking the server side capture and the client side capture.

The client and the server seem to communicate perfectly fine until suddenly they start sending RST packets to each other. What seems also odd to me is the fact that each RST packet can be seen on the receiving side but not on the sending side.

The file that I am uploading from the workstation is 1.8 MB in size. If I try uploading a smaller file ~100 kB, the issue never occurs. In addition, this error never occurs if I download a file bigger than 1 MB from the server.

I have been looking online for potential solutions, but everything seems to be linked to the timeout time of the session being too short, which I don't think is the problem in this case because the error message pops up less than a second after I enter the password.

Has anyone ever seen a similar case?

RST packets sent by both client and server during file transfer

I am trying to troubleshoot why a file upload from a client to Linux server fails in our network. From the workstation, I want to upload a file to the server, so I run the command

scp scan-20170710.pdf [email protected]:/tmp/

After entering the password, I get the message: "packet_write_wait: Connection to 10.11.12.26 port 22: Broken pipe"

I tried capturing the communication between the client and the server. There are no hops between the two, only two switches and an AP. I am linking the server side capture and the client side capture.

The client and the server seem to communicate perfectly fine until suddenly they start sending RST packets to each other. What seems also odd to me is the fact that each RST packet can be seen on the receiving side but not on the sending side.

The file that I am uploading from the workstation is 1.8 MB in size. If I try uploading a smaller file ~100 kB, the issue never occurs. In addition, this error never occurs if I download a file bigger than 1 MB from the server.

I have been looking online for potential solutions, but everything seems to be linked to the timeout time of the session being too short, which I don't think is the problem in this case because the error message pops up less than a second after I enter the password.

Has anyone ever seen a similar case?

RST packets sent by both client and server during file transfer

I am trying to troubleshoot why a file upload from a client to Linux server fails in our network. From the workstation, I want to upload a file to the server, so I run the command

scp scan-20170710.pdf [email protected]:/tmp/

After entering the password, I get the message: "packet_write_wait: Connection to 10.11.12.26 port 22: Broken pipe"

I tried capturing the communication between the client and the server. There are no hops between the two, only two switches and an AP. I am linking the server side capture and the client side capture.

The client and the server seem to communicate perfectly fine until suddenly they start sending RST packets to each other. What seems also odd to me is the fact that each RST packet can be seen on the receiving side but not on the sending side.

The file that I am uploading from the workstation is 1.8 MB in size. If I try uploading a smaller file ~100 kB, the issue never occurs. In addition, this error never occurs if I download a file bigger than 1 MB from the server.

I have been looking online for potential solutions, but everything seems to be linked to the timeout time of the session being too short, which I don't think is the problem in this case because the error message pops up less than a second after I enter the password.

Has anyone ever seen a similar case?