and then tried to install openssh-server. Well I guess it kinda worked. I think it installed ssh-server because when I type in apt-get install ssh-server it says:

openssh-server is already the newest version.
openssh-server set to manually installed.

but when I try ssh:

sudo ssh 192.168.0.4
root@192.168.0.4's password: <-laptop
Welcome to Linux Mint 12 Lisa (GNU/Linux 3.0.0-12-generic i686)

Welcome to Linux Mint
* Documentation: http://www.linuxmint.com

Last login: Wed Mar 28 16:20:36 2012
Michaels-Laptop ~ # ssh 192.168.0.2 <----------------------------- computer in question
ssh: connect to host 192.168.0.2 port 22: No route to host

Michael, in Linux troubleshooting, "the error is the answer". So that means there is NO ROUTE TO HOST.
Is the machine on the same network?

# traceroute 192.168.0.4
# ping 192.168.0.4

Yes, they are in the same network. /24.
Michaels-Laptop ~ # traceroute 192.168.0.3
traceroute to 192.168.0.3 (192.168.0.3), 30 hops max, 60 byte packets
1 * * *
...
30 * * *
Michaels-Laptop ~ # ping 192.168.0.3
PING 192.168.0.3 (192.168.0.3) 56(84) bytes of data.
64 bytes from 192.168.0.3: icmp_req=1 ttl=64 time=1.70 ms
^C
--- 192.168.0.3 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 1.422/1.551/1.722/0.135 ms
Michaels-Laptop ~ # ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
    link/ether 44:1e:a1:c8:89:4b brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    link/ether 94:39:e5:11:b8:84 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.4/24 brd 192.168.0.255 scope global wlan0
    inet6 fe80::9639:e5ff:fe11:b884/64 scope link
       valid_lft forever preferred_lft forever
Michaels-Laptop ~ #
bmike1@Michaels-PC:~$ traceroute 192.168.0.4
traceroute to 192.168.0.4 (192.168.0.4), 30 hops max, 60 byte packets
1 Michaels-Laptop (192.168.0.4) 1.693 ms 1.623 ms 2.344 ms
bmike1@Michaels-PC:~$ ping 192.168.0.4
PING 192.168.0.4 (192.168.0.4) 56(84) bytes of data.
^C
--- 192.168.0.4 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 1.421/1.662/2.175/0.267 ms
bmike1@Michaels-PC:~$ ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:09:6b:78:ab:f0 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.3/24 brd 192.168.0.255 scope global eth0
    inet6 fe80::209:6bff:fe78:abf0/64 scope link
       valid_lft forever preferred_lft forever
bmike1@Michaels-PC:~$

Michaels-Laptop ~ #
The synaptic report is at 'a'.

bmike1@Michaels-PC:~$ /etc/init.d/sshd start
bash: /etc/init.d/sshd: No such file or directory
bmike1@Michaels-PC:~$ ssh localhost
ssh: connect to host localhost port 22: Connection refused
bmike1@Michaels-PC:~$

# cd /etc/init.d/
# ls -al ssh*

It's called /etc/init.d/ssh in Ubuntu https://help.ubuntu.com/10.04/serverguide/C/openssh-server.html

bmike1@Michaels-PC:~$ cd /etc/init.d/
bmike1@Michaels-PC:/etc/init.d$ ls -al ssh*
-rwxr-xr-x 1 root root 4194 2011-07-29 09:02 ssh
bmike1@Michaels-PC:/etc/init.d$ cd ssh
bash: cd: ssh: Not a directory
bmike1@Michaels-PC:/etc/init.d$ sudo ssh start
[sudo] password for bmike1: sat for five minutes
^Cbmike1@Michaels-PC:/etc/init.d$

why did the sound stop working?
>>Another problem that just started is the sound on the print server stopped working. I clicked on the speaker icon >>to turn it up and I see it is maxed. So then I clicked 'sound settings' and the output volume is maxed so I >>investigate the tabs. The first tab (hardware) has nothing in the 'choose a device to configure' window. So >>somehow the driver was removed (I guess).