Opened 15 years ago
Closed 11 years ago
#6051 closed defect (obsolete)
Scanning of network is really slow with activated host-only network
Reported by: | Karl Loncarek | Owned by: | |
---|---|---|---|
Component: | network | Version: | VirtualBox 3.1.2 |
Keywords: | Cc: | ||
Guest type: | Windows | Host type: | Windows |
Description (last modified by )
similar to Bug 4103:
- WinXpSp3 prof. Host
- Virtualbox 3.1.2
This problem persists since very long time... (I think since version 2.x, maybe earlier)
Preparation: Clean install of Virtualbox 3.1.2. All options (also host-only interface) are installed.
Problem: When scanning the network through network environment takes very long time. What I mean: I'm searching for a printer or connectable network drive within the network. This scanning process lasts up to 30secs. Normally (before install of virtualbox) the same process takes mayb 1-2secs. The scanning does work though but takes ages.
Additional problem that occurs: Accessing a computer within the same domain who made a folder available for public is not possible. I'm always asked for user and password.
Partial Workaround: Deactivating Host-only interface helps. Scanning speed is as before. I'm still asked for username and password.
What I tried: I checked the order of network interfaces (host-only is last one in list).
Change History (3)
comment:1 by , 15 years ago
comment:2 by , 15 years ago
Version 3.1.4 improved the situation somewhat. So searchign now lasts only around 10-15secs, but still way too slow.
At least I'm now not asked for a login name and password anymore.
comment:3 by , 11 years ago
Description: | modified (diff) |
---|---|
Resolution: | → obsolete |
Status: | new → closed |
Addition: This problem occurs even when virtualbox is not running! Removing the host-only interface from within Virtualbox and rebooting the computer fixes this issue. Access to a network share is then possible as before. Scanning time is short and I'm not asked for a username and password.
I guess it has something to do with the host-only interface. maybe the computer identifies as something else or with a different (unkown) name within the domain. Nevertheless logging in to the domain was never a problem. Hope this description helps somehow fixing the bug.