View Full Version : One of my VM servers died today
She died suddenly of a failed motherboard, at home surrounded by her family and friends.
Her name means 'peace', and she is at peace now.
RIP mir.pentagon.lan 2009-2012
She is survived by her virtual machines, monolith.pentagon.lan, gamesvr.pentagon.lan, and distro.pentagon.lan
I will be retiring the 192.168.3.2/16 ip address in honor of your memory. May your entry stay in DNS to remind us of your life and the good times we had together.
(consequently the dns server lived on monolith and now has to be migrated to my other host, terra. what a pain in the ass.)
In lieu of flowers please send links to cheap 8 core barebones kits on newegg or tigerdirect
That usually only shows up when someone is using a vpn or a proxy, could be your dhcp server is screwy idk
Do you own the router or does the isp?
Assuming it's the router, and you pay a fee every month, let them deal with it. Also run a virus scan on your machine, sometimes infections will set up your browser to use a proxy so they can steal your shit as it passes through their server. There's no reason you should be using a proxy unless you're on a corporate network or flaggercat.
control panel > internet options > connections tab > lan button
'use a proxy' box should not be checked
DrHundos
10-24-2012, 01:49 AM
RIP in peace
i have a paid proxy service but it's disabled on startup.
then you probably set it up wrong and it's causing problems
RIP in peace
thanks, she was a good box and taught me a lot about life, love, and administrating a virtual machine server
yeah its not. i dunno i'll bitch comcast out and call them faggots until they send someone.
thanks for trying to help.
you sound pretty sure for someone who doesn't even know how to connect to a wifi... go ahead and google the error you're getting, without even looking I can guarantee that every single result involves vpns or proxys
I tried to move mir's network card to terra but it's not getting an ip address. ethtool doesn't detect a link, and it's cliaming that it's mac address is ff:ff:ff:ff:ff:ff. I'm guessing it probably cooked along with the motherboard and maybe even caused the motherboard to cook.
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.