Use of Special Characters in Share Names on a Buffalo LinkStatio¿n NAS.

Posted on 2011-03-21
Medium Priority
Last Modified: 2012-05-11
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.
Question by:JeremyHigginson
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
LVL 43

Expert Comment

by:Davis McCarn
ID: 35188832
Most versions of Linux don't like spaces or punctuation marks in file/folder names and; ironically, sometimes Windows hates them, too.  Until XP-SP3, both Wordpad and Notepad would often get confused by filenames with spaces..........

Author Comment

ID: 35194359
...So I infer from your comment that the LinkStation uses Linux as its operating system, and this is the cause of the problem. Though it seems odd that the sharenames (effectively the root folders on the NAS?) have to comply with Linux naming conventions, but the remaining levels of the file structure don't - and these can happily use any characters that the client operating system can handle.

Should I therefore assume that there is no way round this problem short of buying a PC with Windows Server installed?
LVL 43

Accepted Solution

Davis McCarn earned 1000 total points
ID: 35197658
Or simply use an old Windows computer with a 2nd hard drive.  Even a PIII-800Mhz can dish up data faster than a 100Mbs network.

Author Comment

ID: 35202265
OK - I hadn't appreciated that I could perform the same feat on a Windows desktop PC. But I've dug out an old laptop, set up some shares with all the previously "forbidden" characters, created another hosts file which points at the new IP address of the laptop, and it works just fine with the <other db's>folder (space and apostrophe), but unfortunately not with the <databases$> folder, which for some reason is visible fine under a higher level share, but not as a "root" share. Never mind - i'm half way there and the "$" may be impossible to emulate without a proper edition of Windows server. Thanks for your help.
LVL 43

Expert Comment

by:Davis McCarn
ID: 35206890
Your welcome.  I had thought the use of $ was reserved for special strings anyway and shouldn't be allowed in an actual folder name.

Featured Post

Will your db performance match your db growth?

In Percona’s white paper “Performance at Scale: Keeping Your Database on Its Toes,” we take a high-level approach to what you need to think about when planning for database scalability.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The question appears often enough, how do I transfer my data from my old server to the new server while preserving file shares, share permissions, and NTFS permisions.  Here are my tips for handling such a transfer.
Is your phone running out of space to hold pictures?  This article will show you quick tips on how to solve this problem.
In this video, Percona Director of Solution Engineering Jon Tobin discusses the function and features of Percona Server for MongoDB. How Percona can help Percona can help you determine if Percona Server for MongoDB is the right solution for …
In this video, Percona Solutions Engineer Barrett Chambers discusses some of the basic syntax differences between MySQL and MongoDB. To learn more check out our webinar on MongoDB administration for MySQL DBA: https://www.percona.com/resources/we…
Suggested Courses

764 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question