The solidoodle usb driver creates a COM port on the computer that the host software (e.g. repetier host, as comes with the solidoodle package) uses to communicate with it - it's basically a usb-serial adapter underneath.
Normally a network print server can only share things it knows how to talk to - and yours, according to the brochure, will only talk to generic printers and mass storage devices. Depending on which it detects, it then runs a network print server or samba share drive itself so you can access them over the network. As a rule these print servers don't know how to deal with serial adapters, a brief look around the net came up with a few people trying this unsuccessfully for various applications (older printers that use serial ports, mainly).
The reason it's showing up in 'shares' is that your print server doesn't know what the solidoodle is, and perhaps has defaulted to thinking it's a storage device. You can't connect to it, as when the print server tries to speak mass-storage-device-language via usb to the solidoodle, the solidoodle will ignore it.
In short, this is not going to work. Please connect it directly to the computer by USB.
(If you want to access it via wifi, the current best method is to put a dedicated host computer on the printer (e.g. a $40 raspberry pi single-board computer), running it's own 3d-printing host software that provides a network/web interface (e.g. octoprint), with a wifi connection (the pi needs a usb dongle for this). It's a more involved project, but not insurmountable. There are many guides on the internet about doing this.)
SD3. Mk2b + glass, heated enclosure, GT2 belts, direct drive y shaft, linear bearings, bowden-feed E3D v5 w/ 0.9° stepper
Smoothieboard via Octoprint on RPi
