can not connect to windows share - smb://192.168.3.97/pictures/

Bug #399569 reported by Steve on 2009-07-15
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
Low
Unassigned

Bug Description

Binary package hint: nautilus

Ubuntu 9.04 64bit

Wanted to connect to a share picture folder on the network. Tried to use Nautilus to connect but received error.

From Nautilus (2.26.2)
1. File -> Connect to Server
2. Service Type: Windows Share, Server: 192.168.3.97, Share: pictures, User Name: upict, Domain Name: HOMENET, click connect
3. Password dialog - enter password and press enter
4. Dialog - Could not display "smb://HOMENET;upict@192.168.3.97/pictures/". Error: Failed to mount Windows Share Please select another viewer and try again.

Note: Can connect fine to the share on this machine via terminal using smbclient. Also, I have another machine with Ubuntu 8.04 and can connect to the network share using Nautilus (2.22.5.1).

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/nautilus
NonfreeKernelModules: fglrx
Package: nautilus 1:2.26.2-0ubuntu2
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
Uname: Linux 2.6.28-13-generic x86_64

Steve (steve-littig) wrote :
Sebastien Bacher (seb128) wrote :

thank you for your bug report, does gvfs-mount smb:... works correctly?

Changed in nautilus (Ubuntu):
importance: Undecided → Low
status: New → Incomplete

Hello,

gvfs-mount does not work, it returns the following:

"Error mounting location: Failed to mount Windows share"

Thank you,

Steve

Sebastien Bacher wrote:
> thank you for your bug report, does gvfs-mount smb:... works correctly?
>
> ** Changed in: nautilus (Ubuntu)
> Importance: Undecided => Low
>
> ** Changed in: nautilus (Ubuntu)
> Status: New => Incomplete
>
>

Sebastien Bacher (seb128) wrote :

could you run GVFS_SMB_DEBUG=60 /usr/lib/gvfs/gvfsd -r, try to gvfs-mount and copy the log there?

affects: nautilus (Ubuntu) → gvfs (Ubuntu)
Steve (steve-littig) wrote :
Download full text (5.9 KiB)

I have done as you suggest and the log information is as follows

lp_load_ex: refreshing parameters
Initialising global parameters
params.c:pm_process() - Processing configuration file
"/home/steve/.smb/smb.conf"
Processing section "[global]"
doing parameter lanman auth = yes
doing parameter name resolve order = bcast host
doing parameter dos charset = CP850
doing parameter workgroup = WORKGROUP
pm_process() returned Yes
lp_servicenumber: couldn't find homes
set_server_role: role = ROLE_STANDALONE
Attempting to register new charset UCS-2LE
Registered charset UCS-2LE
Attempting to register new charset UTF-16LE
Registered charset UTF-16LE
Attempting to register new charset UCS-2BE
Registered charset UCS-2BE
Attempting to register new charset UTF-16BE
Registered charset UTF-16BE
Attempting to register new charset UTF8
Registered charset UTF8
Attempting to register new charset UTF-8
Registered charset UTF-8
Attempting to register new charset ASCII
Registered charset ASCII
Attempting to register new charset 646
Registered charset 646
Attempting to register new charset ISO-8859-1
Registered charset ISO-8859-1
Attempting to register new charset UCS2-HEX
Registered charset UCS2-HEX
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
added interface eth0 ip=fe80::224:8cff:fe7a:2ecf%eth0
bcast=fe80::ffff:ffff:ffff:ffff%eth0 netmask=ffff:ffff:ffff:ffff::
added interface eth0 ip=192.168.2.94 bcast=192.168.2.255
netmask=255.255.255.0
Using netbios name ATHENA.
Using workgroup WORKGROUP.
smbc_stat(smb://192.168.2.96/pictures)
SMBC_server: server_n=[192.168.2.96] server=[192.168.2.96]
 -> server_n=[192.168.2.96] server=[192.168.2.96]
Connecting to 192.168.2.96 at port 445
socket option SO_KEEPALIVE = 0
socket option SO_REUSEADDR = 0
socket option SO_BROADCAST = 0
socket option TCP_NODELAY = 1
socket option TCP_KEEPCNT = 9
socket option TCP_KEEPIDLE = 7200
socket option TCP_KEEPINTVL = 75
socket option IPTOS_LOWDELAY = 0
socket option IPTOS_THROUGHPUT = 0
socket option SO_SNDBUF = 16384
socket option SO_RCVBUF = 87380
socket option SO_SNDLOWAT = 1
socket option SO_RCVLOWAT = 1
socket option SO_SNDTIMEO = 0
socket option SO_RCVTIMEO = 0
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
 session request ok
write_socket(13,194)
write_socket(13,194) wrote 194
got smb length of 91
size=91
smb_com=0x72
smb_rcls=0
smb_re...

Read more...

Sebastien Bacher (seb128) wrote :

The issue is "Server requested LANMAN password (share-level security) but 'client lanman auth' is disabled"

Sebastien Bacher (seb128) wrote :

the connection is refused for security reason see bug #209520

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

Other bug subscribers