Error connecting to ethernet device

[keycoldstorage]

I am seeing the "error connecting to ethernet device" on DSlaunch5 when trying to connect to previously operational links. This is on Windows7 64, a fresh install. While the system had worked for weeks, this occurred approximately fourteen hours after having installed VirtualBox on the machine and configured a Linux server to run there over a bridged network adapter. Yes, disabling the VirtualBox network adapter and rebooting the machine makes DirectSoft happy again; however, I suspect there is a bug either in the DirectSoft ethernet implementation for Windows 7 or possibly the VirtualBox network adapter (although the latter seems less likely as it would have received Microsoft's driver certification).

The problem doesn't happen right away, that is, if I enable the "VirtualBox Host-Only Network" adapter and then run a virtual machine on it, DirectSoft is fine, for hours, before it stops working.

Anybody else have this problem?

[Greg]

This error is usually caused by having 2 (or more) NIC (Network Interface Cards). It is because Winsock allocates which NIC is to be used. We have no control over that whatsoever. You can reprioritize your NICs (take the one that uses DirectSOFT5 link to the top). Or, as you have discovered, disable the "troublemaker".