|Can be solved in different manners:|
1. catch and act on the errorlevel inside the "inside.bat" itself. Maybe it's not possible, maybe it is ... You can handle errorcodes inside scripts, without any issue, you don't need to pass them through a called script.
2. Write a file somewhere, indicating the result. Now, since this involves remote computers, it's more difficult, but know that the filesystem is often used as an alternative "communication layer", since it is common inside one OS (but here, different computers I acknowledge. ... still, shared filesystem) ?
3. Try using variables, don't use "setlocal". Possibly RSH will typically destroy all variables, but you can try.