Sorry, I guess I was so excited, that I did not reread and make sure I explained everything.
By "monitoring" I meant that if you clicked on plug-ins, and clicked on web remote from within MJ/MC, prior to having the remote server functionality, you would get a screen that showed you the port number that was chosen, (and allowed you to change it) plus there was a stop and start server button, and a list of what commands were being performed. For example, when you started up MJ/MC, and you clicked on this you would see that the server was started. Any commands that were entered either through a browser, or Glissando, would register their as well. I guess that is what I mean by monitor. I don't use Media Server, although I have seen it, and I think it has the same functionality. Hopfully this helps explain what I mean.
Regarding your response to my second question, I am totally confused, as I was under the impression that the web remote plug-in was not necessary anymore, as the functionality was included in with MC. In fact I uninstalled the Web Remote Plug-in, as I thought it might conflict with the new code that was included within MC. Once I did that, I connected through a browser, found it to work, so I tried Glissando, and although it worked, I did not have the Audio files as I stated before. To add a question to the original question, am I under the wrong impression about the remote server functionality, and that I am still responsible for the Web Remote plug-in version, or is that now included in the base functionality of MC?
Thanks for your help with this Jim!
Drew