Universal Media Server | Forum

First of all, I need to thank to all contributors to this project, because I've tried many media servers and UMS simply outperforms everythink, I mean E-VE-RY-THINK.

But I have issue with "start as service" option. You see, I have a Windows 7 x64 machine as home server. This server is also used as workstation, where users have accounts and after they finish some work, they log out and leave the computer in logon screen.

I'm running all server related tasks as services in background, which survives all logon and logout. If I register UMS as a service, it works fine while logged in, but after I logout, the UMS is visible from remote machine, but streams nothing, not even the folder structure.

The media content is stored on drive pool, which is accesible for everyone in USERS group.
I have also setted up all firewall rules according to viewtopic.php?t=1525

Still the media server does not seem to work while logged out. I use latest UMS 5.3.0.

Any thoughs?

The log seem to be without problems:
http://pastebin.com/Shp4dMLw
but I will run some aditional tests to gather more information for you.

WOW. I can't believe how amizing this project is. Simply by posting my problem here, the problem was solved. Magically. I started another test and realized, that it already works. Maybe the final reboot of machine did reinitialized something, or I reinitielized myself better today morning, but I'm now able to watch my media from the TV no matter if users are logged in or out.

It reminds me my orthoped doctor. Every time I have a problem, which seem to be serious, I call him and book for a visit, and usually at the very same day of the visit, my problems dissapeared, so I go meet him, tell him I'm alright, he made some routine examination and tels me, that I'm healthy. He must think I'm malingerer.

I've also disabled "run at startup", so only the service is runnig. Is it a rule to use just one option (service/program) or is it allowed to start a service and then also the program at logon? I think, maybe the terminating of the program at logout possibly terminated the service.

Ok, i think I have some clue.

I have UMS started as service. if I then start application, the application complaints, that port 5001 is already in use. Previously, I started UMS at windows logon and I have also configured autologon to one of my account. Because previously in a application log it did not complaints about port usage, I presume the program started earlier then the service and took port 5001 for himself, which prevents service to operate. Then after logout, the program was terminated and the service remained blocked. So by running the service and disabling the "run at startup" I've prevented this conflict.