September 19, 20169 yr I know this is probably a silly complaint, but I can't seem to figure out how to get my server to display upper and lower case for it's name how it is configured in unRAID. I've tried searching and can't seem to find the answer. Any ideas? TIA!
December 3, 20169 yr Author Anyone else experience this? If I take the array offline and then go to Settings > Identification and change the name from Tower to tower, it will appear all lower case, but if I name it back to Tower, it reverts to ALL CAPS.
December 3, 20169 yr Author Where exactly is it being displayed "wrongly"? Maybe a screenshot would help. Here is a screenshot from Finder: https://www.dropbox.com/s/iwixixqmqnhv6cw/Screenshot%202016-12-03%2011.54.59.png?dl=0 Before upgrading to 6.2 it displayed correctly as Tower.
December 3, 20169 yr I have three unRAID servers, all running 6.2.4 and they all display in CAPS on my MAC, doesn't bother me though, never looked for a solution.
December 3, 20169 yr Author I have three unRAID servers, all running 6.2.4 and they all display in CAPS on my MAC, doesn't bother me though, never looked for a solution. I understand that it isn't necessarily a big deal, but prior to 6.2 it displayed how I had it named in the unRAID configuration and now it doesn't. It's an annoyance to me.
December 3, 20169 yr Well, here's what mine look like. Lapulapu is running unRAID 6.3.0rc5, Mandaue and Northolt are running 6.2.4. I have AFP shares enabled on all of them. Go figure!
December 3, 20169 yr Author Well, here's what mine look like. Lapulapu is running unRAID 6.3.0rc5, Mandaue and Northolt are running 6.2.4. I have AFP shares enabled on all of them. Go figure! If I enable AFP, it displays correctly, but the SMB share still is in all caps.
December 3, 20169 yr Community Expert Well, here's what mine look like. Lapulapu is running unRAID 6.3.0rc5, Mandaue and Northolt are running 6.2.4. I have AFP shares enabled on all of them. Go figure! If I enable AFP, it displays correctly, but the SMB share still is in all caps. Samba is actually 'borrowed' networking scheme and is actually controlled by Microsoft and all small letters are stripped to CAPS (internally) for computer names and file names. (They can be displayed with small letters but that is a bit of smoke and mirrors. (Try naming one file Sam and another file sam on a windows computer and you will get a complaint. Occasionally, some will name one share on their unRAID server Media and then inadvertently create a second share named media. Windows computers will only display one of the two shares and it often appears that hundreds of files have just vanished!) Both UNIX and Linux honor capitalization (Sam and sam are two different files on both) and I have ever quite figured out how Samba resolves this issue. So be aware of it... When folks are having network issues, I usually caution them to name all Computers on the Samba/SMB network with capital letters to prevent this thing from being an issue.
December 4, 20169 yr I have the same thing but running 6.1.9 on 2 servers (see below)... One displays correctly but the other one displays the SMB in all caps. never really took time to look into it.
December 5, 20169 yr FWIW, I had to reboot the server I call Lapulapu and now the case of its SMB name has changed. I don't think there's any consistency to it. Maybe I ought to reboot Northolt too. As a Mac user that is surely irritating but take comfort from the fact that it's a "Windows thing" and that the AFP names are consistently correct. :^)
January 19, 20179 yr I'm seeing the same behaviour. But here's what's weird: On 4 of my 5 networked Macs, my SMB server name is in mixed cased. On 1 of the 5, it's ALL CAPS! Bizarre.
January 19, 20179 yr Community Expert Mine look like this today. But does it actually matter? Nope. Not unless you have two servers and decide to name one SAM and the other sam (or any other combination of capital and small letters)! Which is why, I always recommend using ALL CAPS when naming computers that will be on a SMB (or Samba) network.
Archived
This topic is now archived and is closed to further replies.