Where do clients get the service name for a Samba share ?

stryker_oz · 12-19-2008, 11:15 PM

Hi,

I've recently rebuilt from Fedora 6 to 10. While it was a fresh install, I restored the smb.conf from the most recent system backup to define the samba shares as they were on the old system and it all appears to work fine, however...

While windows desktops can browse the share, and view files in it, writing to the share causes an error to be logged with a malformed service (backupsv rather than backupsvr). Where aside from smb.conf are these to cause this? Snippet of smbd.log below:

Code:

  __ffff_192.168.34.99 (::ffff:192.168.34.99) connect to service backupsvr initially as user samba (uid=502, gid=502) (pid 8718)
[2008/12/20 13:32:25,  0] smbd/service.c:make_connection(1362)
  bitey (::ffff:192.168.34.99) couldn't find service backupsv
[2008/12/20 13:33:15,  0] smbd/service.c:make_connection(1362)
  __ffff_192.168.34.99 (::ffff:192.168.34.99) couldn't find service backupsv
[2008/12/20 13:33:15,  0] smbd/service.c:make_connection(1362)
  __ffff_192.168.34.99 (::ffff:192.168.34.99) couldn't find service backupsv

Thanks
Geoff

gilead · 12-19-2008, 11:26 PM

I haven't seen that problem so this is a guess and may depend on which version of windows you're running. Is there an 8 character limitation on share names for windows? It would have to silently drop errors when browsing/viewing though so it doesn't sound too promising.

gilead · 12-19-2008, 11:27 PM

Double post

stryker_oz · 12-20-2008, 12:07 AM

Quote:

Originally Posted by gilead

I haven't seen that problem so this is a guess and may depend on which version of windows you're running. Is there an 8 character limitation on share names for windows? It would have to silently drop errors when browsing/viewing though...

Thanks for the fresh set of eyes on this Steve.

The share name is the same as it was prior the move to FC10 the limitation (if any) is not at the client end unless for some reason it's mangling it as a result of the windozeupdate this week. The client in the example is running Windows XP Pro.

TIA
Geoff