Bah, Penguins!!

[BrownSparrow]

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?

Cheers

 

[BrownSparrow]

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?

 

[BrownSparrow]

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!