Bah, Penguins!!

BrownSparrow · 6 May 2011 at 15:31

Boys and girls, i need me some help!

I noticed that my bigadv cruncher was behind on uploading a wu, when i checked the VM, linux had vomited a splurge of error gubbins. So i restarted the vm, but when linux booted i noticed that it said that ethn0 had timed out and therefore the local loopback was being displayed?

I reinstalled vmware and used a fresh image of the VM but i'm still getting this:

Anyone got any ideas? :confused:

Cheers

dekez · 6 May 2011 at 15:42

Looks like it can't get an IP from your DHCP server, have a check in the VM settings that the network adaptor is enabled, is the network type is set to "Bridged"?

I take it you don't have any connection issues on the rig the VM is hosted on?

BrownSparrow · 7 May 2011 at 12:08

The vm card is enabled, connected, and bridged.

I work with Vmware at work so i know it quite well, bit i'm foxed with this one, the fact that linux is throwing it up as an error is worrying.

I don't know why this started, as it had been running fine?

dekez · 7 May 2011 at 12:50

Strange it started acting up for no reason, I'm out of ideas, I was thinking you could set a static IP but the problem seems to be with the VM network adaptor so I don't think it would help. :confused:

dekez · 7 May 2011 at 12:53

Just found a thread where someone had the same problem, they got around it in the end by reinstalling VMware, seems a bit drastic but if nothing else works...

http://www.evga.com/forums/tm.aspx?m=163411&mpage=1&print=true

BrownSparrow · 9 May 2011 at 14:55

Thanks for the link dekez, seems a few people have been having problems with this one.

The solution for me was to set the connection to NAT, no matter what i did i couldn't get a bridged connection to work? The only thing i can think of that has changed is the ip range, it's not what i remember (the computer is in my parents garage), but then i could be completely wrong there.

Oh well, i guess this kind of thing keeps us on our toes!

dekez · 9 May 2011 at 14:59

Excellent, glad it's working again

dekez · 8 Jun 2011 at 17:49

Just had this happen to me as well. I got round it in the end by disabling the VMware network connections in the internet and sharing center and restarted the VM so it formed a new connection, just in case this happens to anyone else.

Berserker · 9 Jun 2011 at 00:32

You can also delete the cached connection info from the Guest OS and reboot the VM. Can't remember the file name right now but I've had to do it several times (grep for eth0 in /etc and you'll probably find it).