Ok, So I have played around a bit with the program now to give it my side of view.
First of all the reason why I got the error message (
StartServiceCtrlDispatcher Failed) before, was because all the commands are case sensitive and must therefore be written with small letters. The same error message will show if you type in a command that doesn't exist.

Another thing to think of, is when you set up your NFS direction on the player. Also here is the letters to the alias for the mapped directory case sensitive and must be written just the way you named them in the file
exports.
When it comes to the installation commands
nfs add and
portmap add, you set the NFS Server to startup automatic the next time windows start. Which I see as an security issue. Especially when you not can setup to give permission only to the player, because it doesn't come with a unitname on the network. (
Something to add for the to-do-list in an update for the player maybe?
)
You can remove the automatic startup with the commands
nfs remove and
portmap remove. But then the program will not start, because it needs them to be added.

Therefore I came up with this batch script to run when you need access from the player:
portmap add
nfs add
nfs start
PAUSE
nfs stop
portmap stop
nfs remove
portmap removeSave the batch file where you put the NFS program.
The pause command makes the script halt until you press enter, after that it stops the NFS Server and remove the automatic startup of the program.

Thanks goes to Maudrid, for the share of this program.
And like he said: Enjoy.

Thats all for now, over and out.
regards
G M R