I setted up a ESX server at work, (http://www.vmware.com/products/vi/esx/) basically you can run multiple servers on one single physical server, it's actually pretty sweet.
Anyway, so everything went smooth, but I realized I could not connect to a VM's console from a different subnet (but can connect to the main interface), and I'm still having that issue. As I was troubleshooting this, I tried connecting to it from a different machine, but with same config, as I was setting my IP to a static in that range just to be able to work on other issues related to one of the VMs itself. I could not connect at all, not even ping. I'm going all wtf and stuff and took me most of the afternoon and before lunch break to solve.
Turns out, when I set the IP, I set it wrong, and not only did I set it wrong on the server, but when I added my ssh profile, and my VMX client profile but when I switched machines, I used the "right" IP and could not connect.
I feel like I need to go take an intro to computers course after doing such a noob move.
Today's lesson: connecting to an IP, and verifying that the IP you are connecting to is actually the RIGHT one
Tomorow's lesson: Did you turn it off and on again?
Next week's lesson: Is it plugged in?
Archived topic from Iceteks, old topic ID:4416, old post ID:35488
N00b moment
- Red Squirrel
- Posts: 29209
- Joined: Wed Dec 18, 2002 12:14 am
- Location: Northern Ontario
- Contact:
N00b moment
Honk if you love Jesus, text if you want to meet Him!
N00b moment
and then check the outlet you plugged it into to see if it's powered.
Archived topic from Iceteks, old topic ID:4416, old post ID:35491
N00b moment
lol no wonder you had a hard time figuring that one out. Could get confusing after awhile.
Archived topic from Iceteks, old topic ID:4416, old post ID:35496
Archived topic from Iceteks, old topic ID:4416, old post ID:35496