uTorrent kills Internet but not INSIDE of a virtual machine

[lakecityransom]

I've had the same settings on uTorrent for about 9 months. Verizon DSL sold to Frontier Communications and I figured they just destroyed my Internet, because I couldn't run uTorrent as it resulted in slow peer connections on uTorrent and 15 sec page load periods when Internet browsing.

It seems its more complicated and I want to understand why a virtual machine is running IE6 full steam ahead with instant page loading, while I test Firefox and IE6 outside of it and they are still stuck trying to load the pages? I've done everything from resetting equipment, custom DNS servers, bridge modem to router (as recommended by Verzion DSL), reinstalling the nForce network driver for the mobo, and also coincidentally a windows file repair for integrity a week ago because of early stages of chkdsk failure...

It just boils down to this: uTorrent running = Internet browsing dies, yet virtual box runs browsers just fine with it on. The only rationale I can begin to understand behind this is that the virtual machine software has its own virtual network driver in device manager and connection in network properties, but it still relies on the main Internet connection in network properties being active to work.

If there is any curiosity, the virtual machine is Virtual Box.

Here's a dual screen image to illustrate my point: http://img59.imageshack.us/img59/1280/loadtest.jpg

[DreadWingKnight]

Are you using the forceware network access manager when you set up the nForce network driver?

[lakecityransom]

No, I try to keep things as simple as possible to prevent problems. The firewall has been off as of late and only a freshly installed Kaspersky which asks permissions when there is a problem.

I have reinstalled uTorrent and reloaded the resume.dat and recreated ipfilter.dat and left the rest to scratch. I'll report back in a day or two, but so far its been okay. I really didn't want to do lose all my torrents, but so far its been okay reloading resume.dat

[Ultima]

That the virtual machine sets up its own separate virtual NIC in the host is the only explanation I can think of too. What are your µTorrent settings like though? Have you checked the thread linked to as the first link in my signature for suggestions (and for what kinds of information we'd like if nothing helps)?

[Firon]

Have you tried uninstalling Kaspersky altogether?

[lakecityransom]

Hey again, everything seems to be fine. The problem was just I needed to un/reinstall uTorrent. I guess maybe there was some failure in file integrity if chkdsk failure has started happening.

Before this I had no torrents actually running, maybe 16 set to seed. 350/64kbps bandwidth. I had even set it to recommended also to test that. I just pulled out the nuclear options too early I guess, because I felt so certain resume.dat had to go but I was wrong.

Thanks anyway though