Opened 17 years ago
Closed 17 years ago
#169 closed defect (fixed)
Problem with TAP Devices under windows
| Reported by: | Reiner | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 1.3.6 |
| Keywords: | Cc: | ||
| Guest type: | other | Host type: | other |
Description
Hi,
I had uses TAP devices under 1.3.2 ... then deinstalled it, installed (without reboot) the 1.3.6 ... the TAP-Device wouldn't be installed till this action.
And it crashed my TCP/IP stack under windows... I had to remove TCP/IP in Windows and reinstall the protocoll. I tried to use the normal procedure afterwards (deinstall VirtualBox, reboot, install VirtualBox, reboot)... but this didn't help ... If I try to create a new device, the "Creating host network interface" windows opens and stays with 0% till i kill the process...
Greets Reiner
Change History (2)
comment:1 by , 17 years ago
comment:2 by , 17 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Closing this defect. If it still happens with 1.4.0, then reopen please.
Note:
See TracTickets
for help on using tickets.
The createhostif command for VBoxManage was buggy (at least in 1.3.8). Fixed this already. (included in the next release)
As for the TAP driver crashing your TCP/IP stack. That sounds rather strange. Unless you are using Windows Vista with an older VBox (not 1.3.8).