Bug 5392 - Server name is concatenated with unix hostname in windows network browser, creating an invalid network path
Server name is concatenated with unix hostname in windows network browser, cr...
Status: NEW
Product: Samba 3.0
Classification: Unclassified
Component: winbind
x64 Linux
: P3 normal
: none
Assigned To: Samba Bugzilla Account
Samba QA Contact
Depends on:
  Show dependency treegraph
Reported: 2008-04-13 04:50 UTC by target
Modified: 2008-04-14 13:03 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description target 2008-04-13 04:50:03 UTC
The samba server is the master in a small network and it curiously gets its server name (as defined in smb.conf) appended to the end of its unix hostname in windows network browsers. Needless to say, this results in invalid network path errors if any clients attempt to access the server.

hostname: gatsby
"server name": sambaserver

For some odd reason, it will show up like so in the network browser on Windows XP clients:
sambaserver (GATSBYsambaserver)
Attempting to access it results in windows attempting to connect to
...which is not a valid network path. It should be attempting to connect to \\sambaserver
Comment 1 target 2008-04-13 04:55:36 UTC
cat description | sed s/\"server name\"/\"server string\"/
Comment 2 target 2008-04-13 06:45:15 UTC
I may have nailed down the bug. The server in question's hostname is a bit too long for a netbios name, so it's automatically truncated by samba during startup. In doing so, something odd happens and samba performs this copy/concatenation of the names.

Adding the netbios name configuration directive to smb.conf with a name of appropriate length such that automatic truncation never occurs causes the server to show up normally in the network browser. 
Comment 3 Kai Blin 2008-04-14 07:50:07 UTC
Just to make sure I'm not barking up the wrong tree, which Samba version are you using?
Comment 4 target 2008-04-14 13:03:12 UTC
smbd --version
Version 3.0.28

It's also in the bug info above.