svn commit: samba r12695 - in branches/SAMBA_4_0/source/scripting/libjs: .

[Jelmer Vernooij]

On Wed, Jan 04, 2006 at 05:26:15PM +0100, G?mes G?za wrote about 'Re: svn commit: samba r12695 - in?branches/SAMBA_4_0/source/scripting/libjs: .':
> Jelmer Vernooij ?rta:
> >>Jelmer Vernooij wrote:
> >>>>Does windows allow such a name in 'system -> computer name'?
> >>>Samba 3 allows it so it is necessary in some cases to have, in order
> >>>to have a clean upgrade path.
> >>  Is this something that can be detected and optionally corrected
> >>in an upgrading script?
> >Yes, it could be detected and corrected. However, we could only fix this
> >on the server that is being upgraded - If it is a DC, its domain members
> > will break because we can't fix the NetBIOS name remotely. If it is a
> >domain member, it won't be able to access its domain later on.
> Just my 2c:
> The cleanest way would be to check for that kind of names before doing
> any modification, and if any found drop an error message to the admin
> explaining the phenomen and giving the steps she/he needs to perform
> before a successfull migration and then exit.
I don't think we should forbid dots in NetBIOS names at all - forcing
users to change their NetBIOS domain name will require them to rejoin
all their workstations and possibly change other things as well. I
don't think allowing NetBIOS names will be that much work (if it would 
require any specific work at all) to support in Samba4.

Jelmer

-- 
Jelmer Vernooij <jelmer at samba.org> - http://jelmer.vernstok.nl/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.samba.org/archive/samba-technical/attachments/20060104/15893c3c/attachment.bin