I've tried and it doesn't work I'm afraid. Connectiing to serverpc from laptop is ok, htpc to serverpc is ok. Laptop to htpc serving local library ok, but connecting from laptop to htpc when htpc is connected to serverpc results in error.
Just thought I'd say, this is exactly my issue with having the Tremote tied to the Library Server. The issue basically comes down to this: The Library Server feature doesn't have much to do with remote control, and the two uses can conflict. Consider my setup:
1. I have a PC hidden away in back room (we'll call this the Server PC). It has a very large RAID-5 volume on it, where effectively all my media lives. This volume is mounted on every machine on the network as Drive M. The library is also located on Drive M. I would like to run MC on this machine as a service, and have it serve the library to all other machines in the house via the Library Server function. (Currently I cannot due to video performance issues with using Library Server, but that is another issue completely unrelated to this issue.) While I do actually use MC on this machine occasionally (when I happen to be doing work in that room and want to listen to music or watch something), it is mostly just a server sitting there running 24/7. It could just as easily be a completely headless box with no sound card stuck in a closet somewhere if I had a closet with adequate cooling to do so.
2. I have a HTPC in the living room. It accesses effectively all of it's media on the network drive (M as mentioned earlier). I would like to connect to the "Server PC" and access the shared library from that machine, never using MC in "local library" mode on the HTPC.
3. I have an office PC downstairs in my "man-lair". This is where I do the majority of my "tagging" work, though I do also do some of it from my laptop and directly from the HTPC. I would also like to connect this machine to the library served by the "Server PC". Connecting to the library server would give me all the benefits of allowing multiple MC-clients to connect and modify the library simultaneously, which is why I want to use that feature. My wife can be watching TV on the HTPC while I tag media files downstairs, and my play counts and whatnot won't get all messed up.
4. I have a laptop that also accesses Drive M, while I'm at home on my fast wireless network. While I'm away, I also have a 2TB drive I can carry with me that has an always-updated clone of the Drive M RAID (which also serves as a convenient redundant backup of the RAID drives should I suffer multiple drive failure or some other catastrophic problem). I use this laptop to watch shows up in the bedroom a lot, and other things like that. I'd like to sometimes use this to connect to the Library Server on the Server PC, and sometimes use it with a local library on the laptop's drive, and sometimes use it with the duplicate of Drive M on the big, honking, external drive, and lastly sometimes use it in Tremote mode. I also have an EeePC 1000H that I'd sometimes like to use for Tremote type purposes.
All this is fine, except for when I add in Tremote to the mix. If I want to use Tremote, it would effectively NEVER be used to control and play back media on the "Server PC" (because that machine is off in a back-room and hidden from most people). If I want to control something, it would almost always be the HTPC. Maybe occasionally the downstairs "man-lair" PC (there's beer and dartboards and party-friendly stuff down there). Sometimes, I might even want to remote control the laptop using the 1000H (if I have the laptop outside hooked up to some speakers for an outdoor party). But the VAST majority of the time it'd be the HTPC.
The problem is, that I can only "remote control" the Server PC, which is useless. That's about the ONLY machine that I'll never want to remote control. In fact, most of the time the speakers hooked up to it (just little cheap desktop jobs) are turned off!
The Tremote feature has nothing to do with the Library Server function (from a
USE perspective). I can certainly see why, programatically, it makes sense that they go together (they both need to load the remote system's library) but in actual use, they would often conflict.
More and more, I think people who do have HTPCs will be storing their media on remote systems. My main reason for doing so is noise and size. In order to store all my media in a reliable fashion, I need a BUNCH of drives. This requires a big box with a bunch of cooling. I don't want all of that sitting in my living room. A perfect HTPC should be tiny, silent, and have nothing on its single hard drive but the software it needs to run. Any media can be served up off the network. However, if I want to remote control something with my fancy touch-screen netbook, it is probably going to be the HTPC, not the server-room machine in the closet!