Opened 18 years ago
Last modified 16 years ago
#9 closed defect
Connect fails with NT_STATUS_BAD_NETWORK_NAME due to garbage characters — at Initial Version
| Reported by: | guest | Owned by: | Paul Smedley |
|---|---|---|---|
| Priority: | major | Milestone: | Samba Server for eCS (OS/2) 1.0 |
| Component: | Samba Server | Version: | 3.0.25rc1 |
| Keywords: | connect failure garbage characters drive share | Cc: | herwig.bauernfeind@… |
Description
The problem is found in 3.0.25rc1, rc2 and rc3. It was not there in 3.0.25pre2 and earlier.
When a whole drive (i.e. K:/ or K:) is shared in smb.conf AND a loglevel of 3 or 4 is defined in smb.conf, connecting to the share will fail with a NT_STATUS_BAD_NETWORK_NAME.
I have provided some logs as attachments to this ticket. Browsing the logs (search for "K:/" in the log.samba.192.168.1.3 files), you will see that it is quite obvious, why this fails, as there are garbage characters after the share name:
If the smb.conf section looks like:
[k]
path = k:/
the logfile entry at loglevel 3 or 4 will be:
[2007/04/13 17:20:15, 0] smbd/service.c:make_connection_snum(1014)
'K:/d 548 ' does not exist or permission denied when connecting to [k]
Note the the garbage after K:/ !
A workaround for this problem is either not to use loglevel 3 or 4 or use a different notation in smb.conf:
[k]
path = k:/./
Both measures make the problem go away.
Additional notes:
- The problem does not occur with with loglevel 1, 5, 6 and 10, others not tested.
- WinXP is sometimes able to connect successfully at the second attempt, smbclient.exe however can never connect.
logfiles that show the failure including used smb.conf