Project

General

Profile

Bug #16006

Unable to set CIFS Workgroup with space

Added by Eric To over 4 years ago. Updated about 3 years ago.

Status:
Closed: User Config Issue
Priority:
Expected
Assignee:
Erin Clark
Category:
OS
Target version:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

I've had been using a Workgroup that have a space in it (example: HELLO WORLD) since day one with Freenas, and I've been using that in my network for years.

Today I just noticed it won't connect/show up in my windows network anymore after the latest update few days ago... Went to check the CIFS settings, and tried to click Save... however it won't let me save anything due to the workgroup name...

"workgroup: Invalid NetBIOS name"

History

#1 Updated by Eric To over 4 years ago

  • File debug-freenas-20160618082550.txz added

#2 Avatar?id=14398&size=24x24 Updated by Kris Moore about 4 years ago

  • Category changed from OS to 57
  • Assignee changed from Kris Moore to Erin Clark
  • Priority changed from No priority to Expected

#3 Updated by Erin Clark about 4 years ago

  • Status changed from Unscreened to Screened

#4 Updated by Erin Clark about 4 years ago

  • Seen in changed from Unspecified to 9.10-STABLE-201606072003

What version were you on prior to your recent upgrade?

#5 Updated by Erin Clark about 4 years ago

  • Status changed from Screened to 15

#6 Updated by Eric To about 4 years ago

Erin Clark wrote:

What version were you on prior to your recent upgrade?

Last year it was 9.2 or 9.3 I think, I had that same WORKGROUP name since (so it was accepting the name with space for sure), then at some point I upgraded 9.10 and have been getting the regular STABLE updates since.
I believe it was probably broken at some point (but since I never change my settings, so it never complaints) and I just happened to notice it when I couldn't see my NAS from Windows 10 after the latest STABLE update from last week.

#7 Updated by Eric To about 4 years ago

BTW, I've changed my WORKGROUP to a name without space, and is working again. So there is a simple workaround, but is still a minor bug nonetheless. :)

Thanks you guys for working on Freenas. <3

#8 Updated by Erin Clark about 4 years ago

Could you show me the output of the command "beadm list", I'd like to see a history so I can get a better idea of when it stopped working altogether

#9 Avatar?id=14398&size=24x24 Updated by Kris Moore about 4 years ago

  • Status changed from 15 to Closed: User Config Issue

BRB: We don't support spaces in the workgroup name, since windows doesn't

#10 Updated by Eric To about 4 years ago

Kris Moore wrote:

BRB: We don't support spaces in the workgroup name, since windows doesn't

Windows does support it.

#11 Updated by Eric To about 4 years ago

Erin Clark wrote:

Could you show me the output of the command "beadm list", I'd like to see a history so I can get a better idea of when it stopped working altogether

BE                                       Active Mountpoint  Space Created                Nickname                                   
default                                  -      -            3.1M 2015-06-06 11:26       default                                    
Initial-Install                          -      -            1.6M 2015-06-06 11:46       Initial-Install                            
FreeNAS-1ac5f24e172b4785efcab5401aa5507f -      -          286.6M 2016-04-20 00:29       FreeNAS-1ac5f24e172b4785efcab5401aa5507f   
9.10-STABLE-201604261518                 -      -          103.1M 2016-04-27 10:06       9.10-STABLE-201604261518                   
9.10-STABLE-201605021851                 -      -           99.9M 2016-05-03 00:39       9.10-STABLE-201605021851                   
9.10-STABLE-201605240427                 -      -          109.0M 2016-05-25 00:52       9.10-STABLE-201605240427                   
9.10-STABLE-201606072003                 NR     /            1.8G 2016-06-11 13:02       9.10-STABLE-201606072003  

#12 Updated by Jordan Hubbard about 4 years ago

Just to correct some misconceptions here:

1. Anything pre-Win2K does NOT support spaces in Workgroup names. Windows 95/98 will not allow this.
2. Even in Win2K forward, any usage of spaces in Workgroup names on the Windows CLI needs to be enclosed in quotes.
3. Quite a few 3rd party SMB packages were designed with the earlier premise that spaces aren't allowed and will fail on them.

For these and other reasons, Most Windows administrators who have been around for any length of time advocate that spaces NOT be used in Workgroup names and will usually slap the fingers of anyone doing so. Just not recommended, not good practice. Here are some of the "best practices" suggestions for workgroup names:

1. Ensure each workgroup and domain name is no longer than 15 characters.

2. Ensure no workgroup or domain name contains spaces. Windows ME and earlier versions of Windows do not support workgroups or domains with spaces in their name.

3. Whenever possible, ensure all computers on the LAN use the same workgroup/domain name. Using common workgroups/domains makes it easier to browse the network and avoids some security complications when sharing files. Note that the default workgroup name in Windows XP is "MSHOME" but in older versions of Windows is "WORKGROUP".

4. Ensure the name of the workgroup/domain is different from the name of any computer on that network.

#13 Updated by Eric To about 4 years ago

Jordan Hubbard wrote:

Just to correct some misconceptions here:

1. Anything pre-Win2K does NOT support spaces in Workgroup names. Windows 95/98 will not allow this.
2. Even in Win2K forward, any usage of spaces in Workgroup names on the Windows CLI needs to be enclosed in quotes.
3. Quite a few 3rd party SMB packages were designed with the earlier premise that spaces aren't allowed and will fail on them.

For these and other reasons, Most Windows administrators who have been around for any length of time advocate that spaces NOT be used in Workgroup names and will usually slap the fingers of anyone doing so. Just not recommended, not good practice. Here are some of the "best practices" suggestions for workgroup names:

1. Ensure each workgroup and domain name is no longer than 15 characters.

2. Ensure no workgroup or domain name contains spaces. Windows ME and earlier versions of Windows do not support workgroups or domains with spaces in their name.

3. Whenever possible, ensure all computers on the LAN use the same workgroup/domain name. Using common workgroups/domains makes it easier to browse the network and avoids some security complications when sharing files. Note that the default workgroup name in Windows XP is "MSHOME" but in older versions of Windows is "WORKGROUP".

4. Ensure the name of the workgroup/domain is different from the name of any computer on that network.

Well, I don't understand what is your point in bringing up Windows 95/98/2K... I am just reporting a minor bug, it is up to you guys to decide to fix it or not... Feel free to close the ticket. You can bring up Windows 3.1 doesn't support anything and don't need to fix any issues reported... But Windows 7 and Windows 8, 8.1, 10 allows space in the name.

#14 Updated by Eric To about 4 years ago

Jordan Hubbard wrote:

Just to correct some misconceptions here:

1. Anything pre-Win2K does NOT support spaces in Workgroup names. Windows 95/98 will not allow this.
2. Even in Win2K forward, any usage of spaces in Workgroup names on the Windows CLI needs to be enclosed in quotes.
3. Quite a few 3rd party SMB packages were designed with the earlier premise that spaces aren't allowed and will fail on them.

For these and other reasons, Most Windows administrators who have been around for any length of time advocate that spaces NOT be used in Workgroup names and will usually slap the fingers of anyone doing so. Just not recommended, not good practice. Here are some of the "best practices" suggestions for workgroup names:

1. Ensure each workgroup and domain name is no longer than 15 characters.

2. Ensure no workgroup or domain name contains spaces. Windows ME and earlier versions of Windows do not support workgroups or domains with spaces in their name.

3. Whenever possible, ensure all computers on the LAN use the same workgroup/domain name. Using common workgroups/domains makes it easier to browse the network and avoids some security complications when sharing files. Note that the default workgroup name in Windows XP is "MSHOME" but in older versions of Windows is "WORKGROUP".

4. Ensure the name of the workgroup/domain is different from the name of any computer on that network.

Well, I don't understand what is your point in bringing up Windows 95/98/2K... I am just reporting a minor bug, it is up to you guys to decide to fix it or not... Feel free to close the ticket. You can bring up Windows 3.1 doesn't support anything and don't need to fix any issues reported... But Windows 7 and Windows 8, 8.1, 10 allows space in the name.

Also I know how Workgroup works, as I stated, it had always been working since the day 1 I started using Freenas and it had always been working since Windows XP.

#15 Updated by Dru Lavigne about 3 years ago

  • File deleted (debug-freenas-20160618082550.txz)

#16 Updated by Dru Lavigne about 3 years ago

  • Target version set to N/A
  • Private changed from Yes to No

Also available in: Atom PDF