File: ts_win-host-host-only-network-adapters.dita

package info (click to toggle)
virtualbox 7.1.12-dfsg-2
  • links: PTS, VCS
  • area: contrib
  • in suites: sid
  • size: 565,672 kB
  • sloc: ansic: 2,330,854; cpp: 2,193,228; asm: 230,777; python: 223,895; xml: 86,771; sh: 25,541; makefile: 8,158; perl: 5,697; java: 5,337; cs: 4,872; pascal: 1,782; javascript: 1,692; objc: 1,131; lex: 931; php: 906; sed: 899; yacc: 707
file content (21 lines) | stat: -rw-r--r-- 1,079 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
<topic xml:lang="en-us" id="ts_win-host-host-only-network-adapters">
  <title>Host-Only Networking Adapters Cannot be Created</title>
  
  <body>
    <p>
        If a host-only adapter cannot be created, either with the
        <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> or the <userinput>VBoxManage</userinput> command, then
        the INF cache is probably corrupt. In this case, the install log
        at <filepath>%windir%\inf\setupapi.dev.log</filepath> would
        typically mention the failure to find a suitable driver package
        for the <filepath>sun_VBoxNetAdp</filepath> component. Again, as
        with the bridged networking problem described above, the
        solution is to uninstall <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, remove the INF cache
        (<filepath>%windir%\inf\INFCACHE.1</filepath>), reboot and try
        to reinstall <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.
      </p>
  </body>
  
</topic>