Ubuntu
samba package

windows unable to access samba

Bug #90950 reported by SolidSource
6
Affects Status Importance Assigned to Milestone
samba (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Currently having a problem where samba setup and able to browser folders on windows machines. However, windows machines are unable to browse samba shares. Samba does not give any errors in testparm nor the logs, the only error I get is on the windows machine saying "network path not found." On the guest machine the password dialog does appear and is accepted, yet remain unable to access any folders/printers.

When configuring through kcontrol, when setting security level, shared will have the security line appear in the smb.conf, but when its set to user there is no security line.

My setup:
Here is my current smb.conf: http://paste.biz/paste-881.html
The users and passwords are set.
Using router
firewall configured correctly (even tried accessing with firewall disabled)
OS = Kubuntu Feisty Herd 5

Known Launchpad Users having similar issues:
Flosoft

ProblemType: Bug
Architecture: amd64
Date: Fri Mar 9 13:31:04 2007
DistroRelease: Ubuntu 7.04
Uname: Linux HellzTitan1 2.6.20-9-generic #2 SMP Sun Feb 25 22:59:06 UTC 2007 x86_64 GNU/Linux

Revision history for this message
mrvanes (mrvanes) wrote :
Download full text (4.1 KiB)

I think I have the same problem, and connecting with smbclient with debug on results in this answer (feisty has only share level security):

This is a (failed) connection FROM an Edgy machine TO Feisty share:

martin@minivanes:~$ smbclient -d 3 //feisty/samba
lp_load: refreshing parameters
Initialising global parameters
params.c:pm_process() - Processing configuration file "/etc/samba/smb.conf"
Processing section "[global]"
added interface ip=192.168.1.73 bcast=192.168.1.255 nmask=255.255.255.0
Client started (version 3.0.22).
resolve_lmhosts: Attempting lmhosts lookup for name feisty<0x20>
resolve_wins: Attempting wins lookup for name feisty<0x20>
resolve_wins: WINS server resolution selected and no WINS servers listed.
resolve_hosts: Attempting host lookup for name feisty<0x20>
name_resolve_bcast: Attempting broadcast lookup for name feisty<0x20>
Got a positive name query response from 192.168.1.22 ( 192.168.1.22 )
Connecting to 192.168.1.22 at port 445
Password:
Domain=[MSHOME] OS=[Unix] Server=[Samba 3.0.24]
resolve_lmhosts: Attempting lmhosts lookup for name feisty<0x20>
resolve_wins: Attempting wins lookup for name feisty<0x20>
resolve_wins: WINS server resolution selected and no WINS servers listed.
resolve_hosts: Attempting host lookup for name feisty<0x20>
name_resolve_bcast: Attempting broadcast lookup for name feisty<0x20>
Got a positive name query response from 192.168.1.22 ( 192.168.1.22 )
Connecting to 192.168.1.22 at port 445
dos_clean_name []
convert_string_allocate: Conversion error: Incomplete multibyte sequence(���_)
convert_string_allocate: Conversion error: Illegal multibyte sequence(���_)
convert_string_allocate: Conversion error: Illegal multibyte sequence(��_)
convert_string_allocate: Conversion error: Illegal multibyte sequence(�_)
convert_string_allocate: Conversion error: Incomplete multibyte sequence(▒_)
convert_string_allocate: Conversion error: Incomplete multibyte sequence)
convert_string_allocate: Conversion error: Incomplete multibyte sequence(���_)
convert_string_allocate: Conversion error: Illegal multibyte sequence(���_)
convert_string_allocate: Conversion error: Illegal multibyte sequence(��_)
convert_string_allocate: Conversion error: Illegal multibyte sequence(�_)
convert_string_allocate: Conversion error: Incomplete multibyte sequence(▒_)
convert_string_allocate: Conversion error: Incomplete multibyte sequence)
convert_string_internal: Conversion error: Incomplete multibyte sequence(���_)
convert_string_internal: Conversion error: Illegal multibyte sequence(���_)
convert_string_internal: Conversion error: Illegal multibyte sequence(��_)
convert_string_internal: Conversion error: Illegal multibyte sequence(�_)
convert_string_internal: Conversion error: Incomplete multibyte sequence(▒_)
convert_string_internal: Conversion error: Incomplete multibyte sequence)
resolve_lmhosts: Attempting lmhosts lookup for name ���_<0x20>
resolve_wins: Attempting wins lookup for name ���_<0x20>
resolve_wins: WINS server resolution selected and no WINS servers listed.
resolve_hosts: Attempting host lookup for name ���_<0x20>
name_resolve_bcast: Attempting broadcast lookup for name ���_<0x20>
convert_string_allocate: Convers...

Read more...

Revision history for this message
SolidSource (cmz13) wrote : Re: [Bug 90950] Re: windows unable to access samba
Download full text (4.5 KiB)

Feisty only has share level security because its still in testing? or
will it only ever have share level? Clarification please, cause feisty
only having share level doesn't make sense, nor is it secure
enough...for my tastes at least.

mrvanes wrote:
> I think I have the same problem, and connecting with smbclient with
> debug on results in this answer (feisty has only share level security):
>
> This is a (failed) connection FROM an Edgy machine TO Feisty share:
>
> martin@minivanes:~$ smbclient -d 3 //feisty/samba
> lp_load: refreshing parameters
> Initialising global parameters
> params.c:pm_process() - Processing configuration file "/etc/samba/smb.conf"
> Processing section "[global]"
> added interface ip=192.168.1.73 bcast=192.168.1.255 nmask=255.255.255.0
> Client started (version 3.0.22).
> resolve_lmhosts: Attempting lmhosts lookup for name feisty<0x20>
> resolve_wins: Attempting wins lookup for name feisty<0x20>
> resolve_wins: WINS server resolution selected and no WINS servers listed.
> resolve_hosts: Attempting host lookup for name feisty<0x20>
> name_resolve_bcast: Attempting broadcast lookup for name feisty<0x20>
> Got a positive name query response from 192.168.1.22 ( 192.168.1.22 )
> Connecting to 192.168.1.22 at port 445
> Password:
> Domain=[MSHOME] OS=[Unix] Server=[Samba 3.0.24]
> resolve_lmhosts: Attempting lmhosts lookup for name feisty<0x20>
> resolve_wins: Attempting wins lookup for name feisty<0x20>
> resolve_wins: WINS server resolution selected and no WINS servers listed.
> resolve_hosts: Attempting host lookup for name feisty<0x20>
> name_resolve_bcast: Attempting broadcast lookup for name feisty<0x20>
> Got a positive name query response from 192.168.1.22 ( 192.168.1.22 )
> Connecting to 192.168.1.22 at port 445
> dos_clean_name []
> convert_string_allocate: Conversion error: Incomplete multibyte sequence(���_)
> convert_string_allocate: Conversion error: Illegal multibyte sequence(���_)
> convert_string_allocate: Conversion error: Illegal multibyte sequence(��_)
> convert_string_allocate: Conversion error: Illegal multibyte sequence(�_)
> convert_string_allocate: Conversion error: Incomplete multibyte sequence(▒_)
> convert_string_allocate: Conversion error: Incomplete multibyte sequence)
> convert_string_allocate: Conversion error: Incomplete multibyte sequence(���_)
> convert_string_allocate: Conversion error: Illegal multibyte sequence(���_)
> convert_string_allocate: Conversion error: Illegal multibyte sequence(��_)
> convert_string_allocate: Conversion error: Illegal multibyte sequence(�_)
> convert_string_allocate: Conversion error: Incomplete multibyte sequence(▒_)
> convert_string_allocate: Conversion error: Incomplete multibyte sequence)
> convert_string_internal: Conversion error: Incomplete multibyte sequence(���_)
> convert_string_internal: Conversion error: Illegal multibyte sequence(���_)
> convert_string_internal: Conversion error: Illegal multibyte sequence(��_)
> convert_string_internal: Conversion error: Illegal multibyte sequence(�_)
> convert_string_internal: Conversion error: Incomplete multibyte sequence(▒_)
> convert_string_internal: Conversion error: Incomplete multibyte sequence)
> reso...

Read more...

Revision history for this message
mrvanes (mrvanes) wrote :

No that's not true. I meant my 'feisty' machine (as in hostname) only has share level security to clarify that no "difficult" encryption or whatever mechanism might be hampering the chit-chat.

Revision history for this message
mrvanes (mrvanes) wrote :
Download full text (5.5 KiB)

"Funny" thing is that the same happens when I try to connect to the feisty machine FROM the same feisty machine. Feisty install is HERD 5 with all updates applied.

root@feisty:~# smbclient -d 3 //feisty/samba
lp_load: refreshing parameters
Initialising global parameters
params.c:pm_process() - Processing configuration file "/etc/samba/smb.conf"
Processing section "[global]"
added interface ip=192.168.1.22 bcast=192.168.1.255 nmask=255.255.255.0
Client started (version 3.0.24).
Connecting to 127.0.1.1 at port 445
Password:
Doing spnego session setup (blob length=58)
got OID=1 3 6 1 4 1 311 2 2 10
got principal=NONE
Got challenge flags:
Got NTLMSSP neg_flags=0x608a0215
NTLMSSP: Set final flags:
Got NTLMSSP neg_flags=0x60080215
NTLMSSP Sign/Seal - Initialising with flags:
Got NTLMSSP neg_flags=0x60080215
SPNEGO login failed: Logon failure
Anonymous login successful
Domain=[MSHOME] OS=[Unix] Server=[Samba 3.0.24]
convert_string_allocate: Conversion error: Illegal multibyte sequence(ￜￜￜ)
convert_string_allocate: Conversion error: Incomplete multibyte sequence(ￜￜ)
convert_string_allocate: Conversion error: Incomplete multibyte sequence(ￜￜ)
convert_string_allocate: Conversion error: Incomplete multibyte sequence(ￜￜ)
convert_string_allocate: Conversion error: Illegal multibyte sequence(ￜￜ)
convert_string_allocate: Conversion error: Illegal multibyte sequence(ￜￜ)
convert_string_allocate: Conversion error: Incomplete multibyte sequence(ￜ)
convert_string_allocate: Conversion error: Illegal multibyte sequence(ￜ)
convert_string_allocate: Conversion error: Illegal multibyte sequence(ￜ)
convert_string_allocate: Conversion error: Incomplete multibyte sequence()
convert_string_allocate: Conversion error: Incomplete multibyte sequence()
convert_string_internal: Conversion error: Illegal multibyte sequence(ￜￜￜ)
convert_string_internal: Conversion error: Incomplete multibyte sequence(ￜￜ)
convert_string_internal: Conversion error: Incomplete multibyte sequence(ￜￜ)
convert_string_internal: Conversion error: Incomplete multibyte sequence(ￜￜ)
convert_string_internal: Conversion error: Illegal multibyte sequence(ￜￜ)
convert_string_internal: Conversion error: Illegal multibyte sequence(ￜￜ)
convert_string_internal: Conversion error: Incomplete multibyte sequence(ￜ)
convert_string_internal: Conversion error: Illegal multibyte sequence(ￜ)
convert_string_internal: Conversion error: Illegal multibyte sequence(ￜ)
convert_string_internal: Conversion error: Incomplete multibyte sequence()
convert_string_internal: Conversion error: Incomplete multibyte sequence()
convert_string_allocate: Conversion error: Illegal multibyte sequence(ￜￜￜ)
convert_string_allocate: Conversion error: Incomplete multibyte sequence(ￜￜ)
convert_string_allocate: Conversion error: Incomplete multibyte sequence(ￜￜ)
convert_string_allocate: Conversion error: Incomplete multibyte sequence(ￜￜ)
convert_string_allocate: Conversion error: Illegal multibyte sequence(ￜￜ)
convert_string_allocate: Conversion error: Illegal multibyte sequence(ￜￜ)
convert_string_allocate: Conversion error: Incomplete multibyte sequence(ￜ)
co...

Read more...

Revision history for this message
TomasHnyk (sup) wrote :

please, could yoy post your smb.conf once more? it is not longer available on paste.biz, paste it here on launchpad.
However, I fear that many bugs related to samba are in fact config issues.

Revision history for this message
SolidSource (cmz13) wrote :

tomashnyk,

I no longer have the problem, fixed by completely re-writing the smb.conf manually. I believe the problem falls with the GUI configurures - so as I am using kubuntu - the samba configurator of kcontrol doesn't seem to work correctly anymore which it did work in edgy... to a point.

So, if anyone is having this problem and is trying to use a GUI to get it to work, try just manually writing it from the original default smb.conf.

note: there are several other GUI (configurators or just programs) problems with feisty...they should have waited to release it.

Revision history for this message
TomasHnyk (sup) wrote :

Then it is not a bug in samba but in kcontrol. I close this bug. If you feel like it, fill a bug againsta kcontrol, but that would require more investing what is not working. For the behaviour of kcontrol as of now seems to me koherent, because? (from smb.conf)
 SECURITY = USER This is the default security setting in Samba 3.0.
which means that it actually work (because if there is no security line, security = user is used).

Changed in samba:
status: Unconfirmed → Rejected
Revision history for this message
mrvanes (mrvanes) wrote :

I suspect this is the same problem as in bug #95460 and if so, then this IS a bug in both Samba and Kcontrol's samba configurator:
Kcontrol shouldn't add a (misconfigured) msdfs proxy= line and samba should gracefully ignore this line.

Revision history for this message
Mathias Gug (mathiaz) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 95460 and is being marked as such. Please look at the other bug report to see if there is any information missing that you can add or to see if there is a work around. Feel free to continue to report any other bugs you may find.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.