VirtualBox

Ticket #14790 (new defect)

Opened 4 years ago

Last modified 4 years ago

Network communication problem in newer versions of VirtualBox. Possible regression.

Reported by: misterpenguin Owned by:
Component: network/NAT Version: VirtualBox 5.0.8
Keywords: Cc:
Guest type: other Host type: other

Description (last modified by vushakov) (diff)

I recently found that VirtualBox could no longer communicate with my printer/scanner (same device). The device is attached via network ethernet cable (NAT).

The operating system of the guest is Linux Mint release 17 (qiana) Mate 64-bit. The driver has worked fine for years. After an update of !Virtualbox somewhere in version 4.x, I was able to send print commands but I could no longer communicate with the scanner.

To help narrow down the problem, I tested the exact same operating system and printer driver with 2 different versions of VirtualBox:

  1. VirtualBox v. 4.2.32 r101581: Scanner works
  2. VirtualBox v. 5.0.6 r103037: Scanner fails

Scanning hasn't worked for some time; at least since version 5.0 and possibly a bit before that. I estimate that it broke sometime after 4.3. Comments in VirtualBox's forum indicate that it's a possible regression because nothing has changed except for the VirtualBox version. Every time I downgraded or upgraded VirtualBox, I always installed the corresponding guest additions for that particular version. I tested with version 5.0.8 r103449 also; the problem persists.

To replicate the problem:

  1. Install Linux Mint 17 Mate 64-bit as the guest. The host can be anything. It's a guest problem.
  2. Install scanner and printer drivers for Lexmark Pinnacle Pro901. These are the respective files:

 http://support.lexmark.com/index?docLocale=en_US&page=content&id=DR21641&locale=EN&userlocale=EN_US

 http://support.lexmark.com/index?docLocale=en_US&page=content&id=DR21637&locale=EN&userlocale=EN_US

  1. When installing the printer driver, add the printer to the operating system. Let the operating system detect the printer, then use AppSocket/HP JetDirect. The IP of the printer will be automatically detected without having to choose AppSocket/HP JetDirect.
  1. There is a cups-insecure-filter error when you try to print. This is easily fixed:
    cd /usr/local/lexmark/v3/bin/
    sudo chmod 755 printfilter
    

Printing isn't the problem though. I include this just to be thorough.

  1. Install any scanning program. gscan2pdf and Simple Scan both work well. On older versions of VirtualBox (up to about the 4.2 I tested, possibly up to around 4.3), scanning will work just fine. All later versions cut off access to the scanner; the scanning program will say no scanners were detected.

End of steps for reproducing the problem

A log file has been attached. During the time the log was created, I powered on the virtual machine, successfully tested that a printed document could be sent to the printer, tested the scanner (which failed), and then powered it off. I'll be happy to provide more details that might be relevant.

Attachments

VBox.log Download (111.0 KB) - added by misterpenguin 4 years ago.

Change History

Changed 4 years ago by misterpenguin

comment:1 Changed 4 years ago by misterpenguin

I'm really sorry about forgetting to classify the bug. Could someone please modify the ticket to reflect these? I don't have the power:

Host type: Windows and Linux (tested on both) Guest type: Linux Mint 64-bit 17 (qiana) Component: Network (possibly Network: NAT)

comment:2 Changed 4 years ago by misterpenguin

Typo correction: The version of VirtualBox I tested is "v. 5.06 r103037", not "v. 5.064103037".

comment:3 Changed 4 years ago by vushakov

  • Component changed from other to network/NAT

Please, can you provide a packet capture of a failed attempt to communicate with the device?

comment:4 Changed 4 years ago by vushakov

  • Description modified (diff)

comment:5 Changed 4 years ago by misterpenguin

Sure. Would a Wireshark capture from within the guest suffice? I can run one showing the successful printer communciation, then a separate one showing the failed scanner communication if it helps.

comment:6 Changed 4 years ago by vushakov

Capturing successful connection to the printer is not necessary for now.

Please, capture the failed scanner connection. If you can capture simultaneously on both guest and host, that might come in handy.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use