View Single Post
Posts: 110 | Thanked: 52 times | Joined on Sep 2007
#10
I'm glad I found this thread. It gave me the hint I needed to SSH in. For anyone else who has this problem in future, the command I needed to SSH in is:
ssh -p 22 root@192.168.1.102