Hello emily, and welcome to our community!
The instrument you have on your hands is a Raspberry Shake 4D (with one vertical weak motion geophone sensor, and three three-dimensional strong motion accelerometers) that was released between 2017 and 2018 (you can check our changelog history here: Change log).
As Philip highlighted, the address (which I think your colleague provided) is an old one, and the correct one is rs.local/ (including the forward slash).
However, as you have done, you can bypass this by directly typing the Shake IP address in your browser bar, and reach the same page.
As nothing seems to be happening with the IP address either, something may be preventing the Shake from fully booting and, consequently, your access to its configuration page.
Could I please ask you to do these two checks?
- Open your terminal window again, and try to ping the Shake IP with the following command
ping -n 5 shakeIPaddress. Does this command yield a 0% packet loss, or a 100% one? - a) If 0% packet loss: can you then execute
ssh myshake@shakeIPaddress(when asked the password, writeshakeme, the default one) and then, if the login is successful, executesudo reboot? - b) If 100% packet loss: can you shut down the Shake by pulling the plug, and then power it on again?
Now, whether the shake has been rebooted (per 2a) or turned on again (after 2b), can you check if the LEDs on it progress as indicated here? Technical Specifications
If not, can you tell me what differences you can see? This information will possibly tell us what is not working with the instrument.
Thank you!