*** This bug is a duplicate of bug 408948 ***
https://bugs.launchpad.net/bugs/408948
** This bug has been marked a duplicate of bug 408948
winxp discovery fails when machine name truncated at 15 chars
--
Truncating NetBIOS name don't work
https://bugs.launchpad.net/bugs/376359
You
So there seem to be an incompatibility between the way Windows (and
smbtree) browse the Windows network and a Samba server where the DNS
name and NetBIOS name differ.
Just to make sure, does adding netbios name = VSERVER-TERM to
/etc/samba/smb.conf (while keeping your hostname to
Here it is. Attach: screenshot, there is no VSERVER-TERMINA in list.
Even more,
fr...@vserver-terminal:~$ smbtree -SN
session request to 192.168.1.45 failed (Called name not present)
session request to 192.168.1.45 failed (Called name not present)
GREENGROUP
session request to 192.168.1.45 failed
Here it is. Attach: screenshot, there is no VSERVER-TERMINA in list.
Even more,
fr...@vserver-terminal:~$ smbtree -SN
session request to 192.168.1.45 failed (Called name not present)
session request to 192.168.1.45 failed (Called name not present)
GREENGROUP
session request to 192.168.1.45 failed
Here You are.
First, I changed hostname to vserver-terminal, restart samba and puts output to
file VSERVER-TERMINA.txt, then changed back to v-terminal, again restart samba
and puts output to file V-TERMINAL.txt.
Attaching files.
** Attachment added: VSERVER-TERMINA.txt
** Attachment added: V-TERMINAL.txt
http://launchpadlibrarian.net/26886719/V-TERMINAL.txt
--
Truncating NetBIOS name don't work
https://bugs.launchpad.net/bugs/376359
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
I mean, VSERVER-TERMINA did not seen in Windows or Linux network
neighborhood windows. Tomorrow I'll boot computers with long terminal
name and get some look into problem (windows don't react immediately to
computer name change).
--
Truncating NetBIOS name don't work
Here You are.
First, I changed hostname to vserver-terminal, restart samba and puts output to
file VSERVER-TERMINA.txt, then changed back to v-terminal, again restart samba
and puts output to file V-TERMINAL.txt.
Attaching files.
** Attachment added: VSERVER-TERMINA.txt
** Attachment added: V-TERMINAL.txt
http://launchpadlibrarian.net/26886719/V-TERMINAL.txt
--
Truncating NetBIOS name don't work
https://bugs.launchpad.net/bugs/376359
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: remote-V-TERMINAL.txt
http://launchpadlibrarian.net/26887036/remote-V-TERMINAL.txt
--
Truncating NetBIOS name don't work
https://bugs.launchpad.net/bugs/376359
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Attaching same files from remote client
** Attachment added: remote-VSERVER-TERMINAL.txt
http://launchpadlibrarian.net/26887031/remote-VSERVER-TERMINAL.txt
--
Truncating NetBIOS name don't work
https://bugs.launchpad.net/bugs/376359
You received this bug notification because you are a member
The trace remote-VSERVER-TERMINAL.txt looks successful to me... What do
you mean by but, VSERVER-TERMINA did not seen in network ?
In all cases the problem would be in your host resolution. Your hostname
is VSERVER-TERMINAL and the NetBIOS name (limited to 16 char) is
VSERVER-TERMINA. If you
I mean, VSERVER-TERMINA did not seen in Windows or Linux network
neighborhood windows. Tomorrow I'll boot computers with long terminal
name and get some look into problem (windows don't react immediately to
computer name change).
--
Truncating NetBIOS name don't work
I think it's a hostname resolution issue on the client side, due to mismatch
between DNS hostname and NetBIOS name. Could you run:
smbclient -d 4 -N -L //servername
on the client in both cases and post the corresponding output ?
** Changed in: samba (Ubuntu)
Status: New = Incomplete
--
I think it's a hostname resolution issue on the client side, due to mismatch
between DNS hostname and NetBIOS name. Could you run:
smbclient -d 4 -N -L //servername
on the client in both cases and post the corresponding output ?
** Changed in: samba (Ubuntu)
Status: New = Incomplete
--
15 matches
Mail list logo
