You are aware MP2 is not a release? Everything connected to it states that fact.
A UNC path has 2 methods of mounting.... An actual Shared drive or folder from the host OR \\SystemName\Drive$ there-by using System Access.
A Mapped Drive is only local to that machine. It is a Remote Volume Assigned to a Local System. Forwarding a Mapped Drive is not expectable even to Windows. Do you truly expect a Map Drive to be available as 2nd party to a piece of software?
MP2 supports Local drive access or Network (Shares) using the Gui. For a Network Share to be available to MP2, it must be Shared by the server. This method guarantees 1-You actually wanted it shared, 2-It appears the same way for All Clients.
This is the Norm for Windows....
No one can help you without them
I for one have been doing extensive testing for the MP2 developers and know 2 things
1 - For not a release, this is an exciting piece of software
2 - Making statements without information on System / System Configuration / Log Files does nothing for anyone
Nope... A Drive Letter indicates it is a Local device but any kind of a UNC.Now, when I add a network resource, it ALSO does not allow me to use my existing drive letter. It uses some weirdo GUID+UNC-path syntax
A UNC path has 2 methods of mounting.... An actual Shared drive or folder from the host OR \\SystemName\Drive$ there-by using System Access.
A Mapped Drive is only local to that machine. It is a Remote Volume Assigned to a Local System. Forwarding a Mapped Drive is not expectable even to Windows. Do you truly expect a Map Drive to be available as 2nd party to a piece of software?
MP2 supports Local drive access or Network (Shares) using the Gui. For a Network Share to be available to MP2, it must be Shared by the server. This method guarantees 1-You actually wanted it shared, 2-It appears the same way for All Clients.
This is the Norm for Windows....
How about following procedure and posting the Server and Client logs.....UPnP discovery seems to be broken or incompatible with other stuff on the network. My logs are overflowing with 'Invalid HTTP header' lines from the SSDPClient/Server
No one can help you without them
I for one have been doing extensive testing for the MP2 developers and know 2 things
1 - For not a release, this is an exciting piece of software
2 - Making statements without information on System / System Configuration / Log Files does nothing for anyone