Jump to content
Sign in to follow this  
TheEvilHammer

Error while trying to send drive report (Samsung SE-S084)

Recommended Posts

I have a Samsung SE-S084 external USB DVD writer and every time I try to submit a drive report I get an error. See the screenshots below. It's not a network issue because this laptop can reach the Internet without any problems and I am able to send a drive report from another laptop on the same network.

[attachment=1]report-working-drive.PNG[/attachment]

[attachment=0]error.PNG[/attachment]

Share this post


Link to post
Share on other sites

Still seeing this on a different computer with a different drive:

Computer: Dell Latitude D430 Laptop

Drive: HL-DT-ST CDRW/DVD GCC4244

Bus: USB

Trying to submit a working drive report yields the error message "Error while trying to send drive report."

Share this post


Link to post
Share on other sites

Hm, stupid error message. For the next version I'll add logging, try again then. Probably some connection problem with proxies or whatever, is actually of minor importance to me.

Share this post


Link to post
Share on other sites
Hm, stupid error message. For the next version I'll add logging, try again then. Probably some connection problem with proxies or whatever, is actually of minor importance to me.

I used Wireshark to take a network trace while submitting the drive report; the capture file is attached to this message. Everything appears to work correctly, up to a point. This is what I see the client doing in the network trace:

  • [*:sb6m9bqq]DNS lookup for
http://www.cdburnerxp.se
[*:sb6m9bqq]Initiation of a TCP connection to port 80
[*:sb6m9bqq]HTTP POST to submit_drive.php with the drive information

So far, so good, but here's what happens next:

  • [*:sb6m9bqq]Client sends a FIN to the server
    [*:sb6m9bqq]Server sends back a 200 OK HTTP message (acknowledging the previous POST)
    [*:sb6m9bqq]Client sends a RST to the server

Based solely on the network trace, it would appear that something happened that the client didn't like, causing a RST to be sent to the server and an error message to be displayed to the user. It does seem odd that the client would start to tear down the TCP connection (by sending a FIN to the server) before waiting for the 200 OK response to come back.

Share this post


Link to post
Share on other sites

I am attaching a network trace taken on another laptop on the same network showing a successful working drive report submission. In this trace, you can see that the client does not send a FIN to the server after sending the POST message. Rather, the client waits for the 200 OK to come back from the server. Another big difference is that in this trace, the server actually terminates the connection by sending a FIN to the client.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.