16
Networking / Samba connection - how to troubleshoot what gets sent and received?
« on: January 25, 2022, 03:59:19 am »
Guys!
I've had a pesky problem on my OS/2 box for a while now, that being on Samba connections Lucide takes far too long to open a PDF that's sitting out there on my NAS box. This is not just a Lucide issue, GSView as well as QPDFView show the same behaviour.
We are talking here PDF files that are about 70-150k in size that take 5-10 secs to open up.
To be clear, I am using NetDrive Samba plugin to make this work, and that could certainly be adding, I just can't tell.
What I can see is that as I open a PDF file my TCP/IP monitor shows multiple traffic spikes, they continue (back and forth) until the file is opened up. Now nearly each one of these are spikes are actually larger than the actual PDF file itself, so that's literally flooring me as I can't for the life of me understand what is causing the traffic to happen.
Alright...so how can I troubleshoot this in order to figure out what all that "overhead" is that appears to be moving back and forth?
I've got Wireshark installed, so I could capture the packets as the transactions start...but is there something a little more human-digestable? I'm thinking Samba logging perhaps?
Thanks!
I've had a pesky problem on my OS/2 box for a while now, that being on Samba connections Lucide takes far too long to open a PDF that's sitting out there on my NAS box. This is not just a Lucide issue, GSView as well as QPDFView show the same behaviour.
We are talking here PDF files that are about 70-150k in size that take 5-10 secs to open up.
To be clear, I am using NetDrive Samba plugin to make this work, and that could certainly be adding, I just can't tell.
What I can see is that as I open a PDF file my TCP/IP monitor shows multiple traffic spikes, they continue (back and forth) until the file is opened up. Now nearly each one of these are spikes are actually larger than the actual PDF file itself, so that's literally flooring me as I can't for the life of me understand what is causing the traffic to happen.
Alright...so how can I troubleshoot this in order to figure out what all that "overhead" is that appears to be moving back and forth?
I've got Wireshark installed, so I could capture the packets as the transactions start...but is there something a little more human-digestable? I'm thinking Samba logging perhaps?
Thanks!