Situation: I am on a standalone development computer running Windows 7 . Not connected to Windows Server. I would like to test the ability of a Window application to use UNC paths . It will be transferred later to the Linux server (and not at my location), therefore, the desire to use the cross-platform path (UNC) mechanism (// server_name / sharename) rather than the drive connected to the window (X: \ folder_name).
The application is Autodesk Maya 2014. The main project file contains many links to other files. These file links can be relative paths ("subfolder / filename.ext"), absolute paths ("H: /projects/this_project/subfolder/filename.ext"), or UNC paths ("// server_name / projects /. . "or" server_name / assets / .. "). The application allows slashes and maps them to the correct character on different operating systems. If possible, I use relative paths.
But I have a situation where the plugin does not work correctly with relative paths, so I resorted to using some absolute paths. It was suggested to change them from the current displayed disk form in the UNC path. REASON: Data will be transferred to the Linux rendering farm. The Linux version of the application will be used. (So my question is not about accessing Linux files from a Windows window, but about setting up all the data, so when everything is moved to the rendering farm, it will still work.)
Due to the combination of plugins and functions that we use in Maya, I am not 100% sure that I can convert all paths to relative. (Questions for Maya forums.) So, as a reserve, I need to test UNC paths. I ask what it takes to install this on my Windows 7 PC without actually connecting to the server computer. (Do not install Linux and Windows Server in my location.)
Usually I do not do network programming or server programming, so I am not familiar with the various possible solutions.
Googling offers some basic methods that may or may not be relevant. Before I spend more time on this, I want to know if I am going in the right / easy direction.
What I managed to do so far: At the command line (Run as administrator):
net view \\localhost
or
net view \\mycomputernamehere
Enumerates shared folders on my PC. For example. H: \ temp Properties / Sharing, shared as the "HTemp" that is specified.
So, I think all I need to do is:
but. Share any folder with the desired name, for example. "projects". It will then display as "\\ localhost \ projects".
C. Convince Windows to use my local computer when I request "\\ servername". Then I can use "// server_name / projects" in the application that will prompt Windows for "\\ servername \ projects", which will then be converted by Windows to "\\ mycomputernamehere \ projects".
... this (B) is the part in which I need help. (3) this seems to be the solution. But for me it is rather mysterious (registry editing). Will he do what I need? Is there a simple solution that does not require editing the registry?
And yes, somewhere along the way it dawned on me that the easiest solution is to rename my computer to "servername". I will probably do it this week.
But anyway, I would like to know the way the aliases of the name of my computer are, to fake the UNC path without actually renaming my computer. And not relying on a second computer acting as a server.