I have a Buffalo LinkStation which I mainly use for emulating client (i.e. customer) server locations prior to configuring software to point at those locations (e.g. \\servername\sharename\folder level 1\folder level 2\...).
I do this by logging into the root of the NAS and selecting the "Security > Setup shared folder" option; I then "Add a new folder" and enter the name of the top level folder on the designated server (i.e. "sharename" in the example above).
Next I add a new entry to the "hosts" file which is stored in the "C:\Windows\system32\drivers\etc" folder on my test PC; this quotes the IP address of the NAS and the name that is being allocated to that server ("servername" in the example above).
If I then use Explorer, I can type in \\servername\sharename and it will display all folders and files that have already been set up on the LinkStation; these can also be seen by typing in \\Buffalo\sharename (since "Buffalo" is the machine name I have ascribed to the device).
My problem is that some of the clients have a sharename that includes spaces or other non-alphabetic characters (e.g. "\\servername\other db's", or "\\servername\databases$", and the NAS device does not seem to be able to set up a sharename which includes these (although it is perfectly happy to deal with such characters at lower levels of the folder structure). This means that I cannot preconfigure the application to point in the right place.
Is this problem universal across all similar devices or is there anything I can do to overcome this? Obviously if you have a proper (Windows) server - which is what I am trying to emulate - then the spaces and other non-alpha characters work just fine. But I can't afford to go down that route.