~ overflow ~

Problem:

Windows Virtual PC Network is slow.

Solution:

- On the host computer, backup the Registry, just in case, and then:

- Run Registry Editor (regedit.exe) and select the following key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

- Create new DWORD value named DisableTaskOffload and set its value to 1.

- Restart the computer.

Yes this is a ripoff article!!!

Source:

http://www.softblog.com/2009-12/slow-network-virtual-pc-windows-7/

Problem:

After instaling a language pack on the system some services apparently restarted and then network stopped working. I was able to ping and IP but couldn’t resolve anything. Even with the resolv.conf filled with DNS.

Solution:

The issue wasn’t on the resolv.conf, looks like that NetworkManager was conflicting with something, when i logged at gnome it was stating that i was “disconnected”, but i had 2 wired connections on that machine, so something was very wrong.

I decided to shutdown NetworkManager and manually configure the ips and gateways, this is the config i made:

ifconfig eth0 192.168.1.5 netmask 255.255.255.0
ifconfig eth1 1.0.0.1 netmask 255.255.255.0
route add default gateway 192.168.1.253
route add 1.0.0.0 gateway 1.0.0.1

my router is on 192.168.1.253 and i have a internal network with the 1.0.0.* on the secondary NIC. route commands are the most importaint, they were avoiding me to resolve the addresses. Also when you disable the networkmanager NICs will not have ips unless you define them manually.

So, it’s just add this to /etc/rc.d/rc.local and everytime you boot you will have your network working just fine without networkmanager crappyness. Obviously that you don’t need to reboot to make this work.

Problem: Connecting a RDC to localhost will loopback and windows will say you can’t do this, because it’s ugly.

Solution: use 127.0.0.2 instead of localhost or 127.0.0.1; This will work on windows xp and older. Another solution is do a different port workaround on mstsc service configuration.