Displaying 4 results from an estimated 4 matches for "canonicalize_servicename".
2016 Aug 29
2
Certain systems can no longer access samba post upgrade to 4.3.9
...ll then be able to use the short
name to pull up the share after you have made the successful connection to
the fully qualified name.
The one log entry that seems to identify systems with this issue is this,
repeated over and over:
[2016/08/29 08:35:56.694436, 0]
../source3/param/loadparm.c:1460(canonicalize_servicename)
canonicalize_servicename: NULL source name!
[2016/08/29 08:35:57.694984, 0]
../source3/param/loadparm.c:1460(canonicalize_servicename)
canonicalize_servicename: NULL source name!
[2016/08/29 08:35:58.694495, 0]
../source3/param/loadparm.c:1460(canonicalize_servicename)
canonicalize_servi...
2016 Aug 30
2
Certain systems can no longer access samba post upgrade to 4.3.9
...made the successful connection
> to
> > the fully qualified name.
> >
> > The one log entry that seems to identify systems with this issue is this,
> > repeated over and over:
> >
> > [2016/08/29 08:35:56.694436, 0]
> > ../source3/param/loadparm.c:1460(canonicalize_servicename)
> > canonicalize_servicename: NULL source name!
> >
> > [2016/08/29 08:35:57.694984, 0]
> > ../source3/param/loadparm.c:1460(canonicalize_servicename)
> > canonicalize_servicename: NULL source name!
> >
> > [2016/08/29 08:35:58.694495, 0]
> > ....
2016 Aug 31
0
Certain systems can no longer access samba post upgrade to 4.3.9
...to
>> > the fully qualified name.
>> >
>> > The one log entry that seems to identify systems with this issue is
>> this,
>> > repeated over and over:
>> >
>> > [2016/08/29 08:35:56.694436, 0]
>> > ../source3/param/loadparm.c:1460(canonicalize_servicename)
>> > canonicalize_servicename: NULL source name!
>> >
>> > [2016/08/29 08:35:57.694984, 0]
>> > ../source3/param/loadparm.c:1460(canonicalize_servicename)
>> > canonicalize_servicename: NULL source name!
>> >
>> > [2016/08/29 08:3...
2016 Aug 29
0
Certain systems can no longer access samba post upgrade to 4.3.9
...me to pull up the share after you have made the successful connection to
> the fully qualified name.
>
> The one log entry that seems to identify systems with this issue is this,
> repeated over and over:
>
> [2016/08/29 08:35:56.694436, 0]
> ../source3/param/loadparm.c:1460(canonicalize_servicename)
> canonicalize_servicename: NULL source name!
>
> [2016/08/29 08:35:57.694984, 0]
> ../source3/param/loadparm.c:1460(canonicalize_servicename)
> canonicalize_servicename: NULL source name!
>
> [2016/08/29 08:35:58.694495, 0]
> ../source3/param/loadparm.c:1460(canoni...