Tell me more ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free, no registration required.
up vote 1 down vote favorite

I got a new machine for work and was already using Ubuntu before that with a chain loader setup to load Windows 7 on another disk. My employer likes that cause he can just rip out the ubuntu disk and no trace is left of it.

My most recent problem is that he wanted to limit the reboots from Windows to Ubuntu so he asked me to setup myself as a VMWare VM. I used the second physical disk to install all my stuff directly on the disk and it was working quite well, just as it was before on my old machine.

I decided this morning to boot directly into Ubuntu and try it out outside of the VM cause the VM made my ubuntu kinda slow to work with. But since i rebooted in Ubuntu, compared to my last machine, network access is horribly slow. It can be a windows share, the internet in general, it takes a lot of time to resolve names, about 10s and if i want to browse a server share (where all our projects are located for instance) i can take up to 2-3 minute to get a listing of the files on the main share (Contains all our client's folders, around 500 folders)

Needless to say this is really not productive :)

It doesn't seem to happen when i'm in the VM in bridged networking but here in standalone mode, same machine, same hard disk, same OS, just not virtualized, everything seems more slugish in terms of internet...

Can anyone help out?

share|improve this question
Ok i confirm, i'm in the same disk but running from the VM right now and my internet in general is much faster and so is the windows shares... can anyone explain that? – Mathieu Dumoulin Dec 16 '11 at 18:02
"it takes a lot of time to resolve names" == DNS issue. Find out how the networking configuration differes between bridged Ubuntu (VM), native Ubuntu, and Windows? Are the nameservers (listed in /etc/resolv.conf) identical? – Jan Dec 19 '11 at 19:01
What hardware do you have ? pastebin the output of sudo lshw -c network -sanitize – bodhi.zazen Dec 19 '11 at 20:06
All signs point to a network driver issue here. The driver for Ubuntu may be buggy, or you may be using the wrong driver, or you need to install a proprietary driver. However, when on the VM, the actual network access is done by the Windows driver, and the network driver the virtualized Ubuntu uses is a very generic one, known and tested to work well. So as bodhi.zazen says, having data on your hardware and also perhaps output of lsmod to see which driver you're actually using would prove useful. – roadmr Dec 22 '11 at 23:41
"A lot of time to resolve names" also makes me suspect the nameservers. Try using something like google's DNS (8.8.8.8) to see if that's the problem (it won't be useful for internal stuff, but if the internet becomes much more usable, it shows you that that's where the problem is) – tumbleweed Dec 23 '11 at 23:16
show 1 more comment

closed as too localized by Stefano Palazzo♦ Jan 27 '12 at 11:02

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, see the FAQ.