Quote:
Originally Posted by MikeDeltaBrown
It looks like you have VM-Ware installed and it is configuring the interface 'vmnet8' with the same IP address as your router.
Try everything as before.
Then enter:
ifconfig vmnet8 down (assuming it was still assigned 192.168.2.1)
Try accessing the internet again.
If that fixes it, you'll have to figure out how to assign a different IP address to 'vmnet8' during boot.
Oh, and the reason the pings to 192.168.2.1 were working and the internet was not is because you were pinging yourself, not the router.
|
Well problem solved, thanks to your post! Thanks a lot!
The problem was from an installation of VMWARE which initializes a series of processes at startup, regardless if VMWARE is active.
Running:
Code:
sudo ifconfig vmnet8 down
and
Code:
sudo ifconfig vmnet1 down
was not enough, as this doesnt stop the startup processes. So, initially the proposed solution didn't work, but pointed to the correct direction.
Doing, however,
Code:
sudo /etc/init.d/vmware stop
immediately resolves the problem.
This post here also helped:
http://communities.vmware.com/thread...art=0&tstart=0
The reason this was not working only at my home router is because of a file (/etc/vmware/locations) overriding some configurations. Even at my workplace, the vmnet entry at the ifconfig call was giving as IP the one of my home router (which is why there was no conflict at any other location except at my place).
