I was doing stuff on my computer tonight at home, then I realized I had
updated my calendar at work but hadn’t pushed the changes to the server (I
did a git commit, but not a git push, I was in a hurry to leave to pick up
aiden from school).
no prob, I thought, I’ll just log in to the vpn, get on my computer at work (fission), and push the changes.
got on the vpn, but fission was timing out on ssh, and wouldn’t answer a
then I started getting nervous, because I actually got a lot of work done
today, and hadn’t pushed those patches anywhere else (not even to my
laptop). again, I was in a hurry to get out.
looked on the backup server: fission got backed up at 9am today, but all backups for
fission failed after that. (at 11, and 2, and 5pm)
brief moment of panic, thinking I had lost a day’s work (thinking the
worst, that fission’s hard drive had died)!
then I thought through it a bit more, and theorized that sometime between
9am and the next backup at 11am, fission got a new ip address from the
dhcp server. I thought of this theory, because I knew I had been using the machine all day during the times the backups failed.
ok, I thought, there’s only 256 possibilities, I can start sshing. but I
didn’t even try that.
my next thought was nmap. a quick google search, and then I did this:
sudo nmap -O x.x.x.0/24 > /work/tmp/list
let it run for a while, it was pretty slow. what it gave me was a list of
every machine, what services they were running, and a best guess of the OS
type. at first I just started looking for linux 2.6.X, but then thought
better of it and starting trying all machines which were providing ssh.
finally found fission at 202!! here’s the output nmap gave me for it. I’m
not sure how in the world it came up with the host name even! I didn’t
even notice that until afterwards. I’m not sure what some of those
services are either. but oh well, I got logged in to fission and now won’t
have to lose a day’s work or drive in to the office tomorrow, or tell
someone how to switch the keyboard back to qwerty to check it for me.
Interesting ports on fission.office.tmcs (x.x.x.202):
Not shown: 1687 closed ports
PORT STATE SERVICE
22/tcp open ssh
25/tcp open smtp
53/tcp open domain
111/tcp open rpcbind
445/tcp filtered microsoft-ds
873/tcp open rsync
902/tcp open iss-realsecure-sensor
2049/tcp open nfs
3128/tcp open squid-http
6667/tcp filtered irc
No exact OS matches for host (If you know what OS is running on it, see