VB installation "breaks" SMB share connectivity

[kastevenson]

Hello,

For some reason, a few weeks back I noticed my mac (2018 MBP touch bar, OSX 10.14.4) no longer connected to SMB or CIFS shares. It took me a while to track it down but uninstalling VB 6 fixed the issue. I recently reinstalled VB 5.2 and the issue is back. Has anyone experienced this or have any thoughts on what is going on? Not finding much on the google machine other than a kext potentially causing the issue....

[kastevenson]

No one else is having this issue with OSX 10.14.4?

[andyp73]

I don't remember seeing any issues with accessing SMB and CIFS shares when my 2017 iMac was running OSX 10.14.4 and VirtualBox. It was a while ago though as I have been running 10.14.5 for a while.

I guess we need to start to narrow things down a bit. Is it as soon as you have installed VirtualBox? After installing the Extension Pack? Only whilst you have a guest running?

-Andy.

[kastevenson]

Thanks for the reply Andy,

The SMB/CIFS stops working immediately after installing VB 5.2 or 6, whether the VM is running or not. AFP still works. The only thing that fixes it is running the uninstaller followed by a restart.

[socratis]

I have never had such an issue such as the one that you're describing, neither do I remember anyone else. So, something must be unique in your setup...

From the symptoms you're describing, I think that this might be because of the Bridged filter that gets installed with VirtualBox. Which leads to the question; what's your network setup like? Do you have any 3rd party networking software installed? From Wireshark to VPN to something else?

Please post the output of:

• 
  kextstat | grep -v com.apple

[kastevenson]

Here's the output without virtualbox installed.

Index Refs Address            Size       Wired      Name (Version) UUID <Linked Against>
  143    0 0xffffff7f84869000 0x38000    0x38000    com.sentinelone.sentinel-kext (2657) F3A02CFC-4C0F-3A05-AFE4-890A03254269 <54 19 6 5 3 2 1>
  172    0 0xffffff7f84bb8000 0x13000    0x13000    com.waves.driver.soundgrid (9.7.99) no UUID <124 23 6 5 3 1>
  173    0 0xffffff7f84bcb000 0x5000     0x5000     com.Cycling74.driver.Soundflower (2) 2D779840-7439-31E5-8A66-D786C3F47B75 <124 6 5 3>
  175    0 0xffffff7f84bd3000 0x13000    0x13000    com.audinate.dante.driver.DanteVirtualSoundcard (1.0.0) 22043C9B-4CCD-3647-9437-FE392477CA65 <124 6 5 3 1>
  182    0 0xffffff7f850e9000 0x33000    0x33000    com.cisco.kext.acsock (4.5.0) D5CD13F0-0EAE-3A95-9ECB-970AFAFCB139 <6 5 1>
  186    0 0xffffff7f8649d000 0x48000    0x48000    com.facilis.factbfs_712 (7.1.2) ED2D16F3-0EF2-3BCF-9A46-6A50004715BF <8 6 5 3 1>
  187    0 0xffffff7f864e5000 0x6000     0x6000     com.getdropbox.dropbox.kext (1.10.3) F29DD0CB-48D6-311A-9B69-E39CF775493C <8 6 5 2 1>

[socratis]

Plenty of 3rd party kexts here, tough to know which might be responsible. For starters, you got to get rid of "com.Cycling74.driver.Soundflower", it's abandonware and a known troublemaker. The Cisco one seems pretty suspect too, just like the Facilis, the Sentinelone and the rest. Start by uninstalling all of them and see which one causes the conflict...