OK, well I'm not familiar with that particular blog or posting, but reiterate that the --multi option is not standard for gdbserver.
The way I test and get gdbserver running, because I do it only every few years and have to re-learn what works and what doesn't, is that I run it locally. You can run it not across a network, just using local ports. That helps me to the connection part working and then I translate that to multiple systems.
Typically gdbserver is run advertising a certain port number and using the compile application which you are compiling, like:
Code:
$ gdbserver <name> --attach <pid>
If memory serves, this gives you a port number to attach to. And then when you run gdb on the host side you use the IP address, the port, and the application name to attach to. Then it's normal gdb commands after that.
But since you're following a guide written in a specific way, I'd re-trace their flow steps and see if you've missed something, or review what they're saying in the details.