Would you really expect it to transfer PCM 44k1/16bit over network?
Oh, boy ... how on earth does your daughter watch cartoons over DLNA, if 1.35 Mbit/s is too much? Choppy pixelated crap?
DLNA server is a program, which is to be run in the server (which is assumed to be Windows). HTTP server is a program, setting it up is as trivial as DLNA server. DLNA is http with extra, unneeded, headers & complications. Similar programs are anonymous ftp, etc. Sharing a folder in Windows is one click operation. My Android found my samba share without any problems. Try "smbclient -L //server". Or start a http server, ask your daughter to find Music on it. Or Videos. Note: I am not against UPnP, only against DLNA.
DLNA is easier to set up only because some braindead idiot decided it to be a standard (instead of http/ftp/nfs/samba/net-radio/...), and manufacturers agreed. I bet the reason is "content protection".
My Samsung DVD player cannot handle streaming data at all! It cannot play[1] net radio stations. It works only with Samsungs own server, with 320kbit/s or slower mp3, not with any other (freeware) server without hours of C programming & setup modifications. Ask yout wife about WAF! Everybody complains the DLNA implementations being shit - it cannot be a coincidence, the spec must be too loose, convoluted and poor.
{1] With any meaningfull definition of "can".