Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I've recently been experiencing an issue connecting to my Samba shares on a Ubuntu 10.4 server box on my network from a Windows 7 client. If I use Ubuntu 10.10 on the same machine, or a Windows XP Virtual Machine running under both Windows and Linux host the share works absolutely fine.
What happens is if I browse to the hostname or the IP address I see a login prompt (there is access control) but my username and password no longer work. Before I didn't need to login as they are the same as my windows credentials.
I'm not sure what information/logs etc would be most relevant so I've posted some information, if any more is required then let me know where to find it and I'm sure I'll be able to get it.
Here is the last few days of the log when I believe it was working, there are no entries since.
Code:
[2010/12/15 12:30:05, 1] smbd/service.c:1063(make_connection_snum)
ramuh (192.168.2.13) connect to service tom initially as user tom (uid=1000, gid=1000) (pid 2458)
[2010/12/15 12:33:05, 0] printing/print_cups.c:103(cups_connect)
Unable to connect to CUPS server localhost:631 - Connection refused
[2010/12/15 12:33:05, 0] printing/print_cups.c:103(cups_connect)
Unable to connect to CUPS server localhost:631 - Connection refused
[2010/12/15 12:38:43, 1] smbd/service.c:1240(close_cnum)
ramuh (192.168.2.13) closed connection to service tom
[2010/12/15 19:25:24, 1] smbd/service.c:1063(make_connection_snum)
ramuh (192.168.2.13) connect to service tom initially as user tom (uid=1000, gid=1000) (pid 2710)
[2010/12/15 19:28:24, 0] printing/print_cups.c:103(cups_connect)
Unable to connect to CUPS server localhost:631 - Connection refused
[2010/12/15 19:28:24, 0] printing/print_cups.c:103(cups_connect)
Unable to connect to CUPS server localhost:631 - Connection refused
[2010/12/15 19:37:30, 1] smbd/service.c:1240(close_cnum)
ramuh (192.168.2.13) closed connection to service tom
[2010/12/15 20:00:27, 1] smbd/service.c:1063(make_connection_snum)
ramuh (192.168.2.13) connect to service tom initially as user tom (uid=1000, gid=1000) (pid 1939)
[2010/12/15 20:03:27, 0] printing/print_cups.c:103(cups_connect)
Unable to connect to CUPS server localhost:631 - Connection refused
[2010/12/15 20:03:27, 0] printing/print_cups.c:103(cups_connect)
Unable to connect to CUPS server localhost:631 - Connection refused
[2010/12/15 20:16:27, 0] printing/print_cups.c:103(cups_connect)
Unable to connect to CUPS server localhost:631 - Connection refused
[2010/12/15 20:16:27, 0] printing/print_cups.c:103(cups_connect)
Unable to connect to CUPS server localhost:631 - Connection refused
[2010/12/15 20:29:28, 0] printing/print_cups.c:103(cups_connect)
Unable to connect to CUPS server localhost:631 - Connection refused
[2010/12/15 20:29:28, 0] printing/print_cups.c:103(cups_connect)
Unable to connect to CUPS server localhost:631 - Connection refused
[2010/12/15 20:42:28, 0] printing/print_cups.c:103(cups_connect)
Unable to connect to CUPS server localhost:631 - Connection refused
[2010/12/15 20:42:28, 0] printing/print_cups.c:103(cups_connect)
Unable to connect to CUPS server localhost:631 - Connection refused
[2010/12/15 20:55:29, 0] printing/print_cups.c:103(cups_connect)
Unable to connect to CUPS server localhost:631 - Connection refused
[2010/12/15 20:55:29, 0] printing/print_cups.c:103(cups_connect)
Unable to connect to CUPS server localhost:631 - Connection refused
[2010/12/15 21:03:48, 1] smbd/service.c:1240(close_cnum)
ramuh (192.168.2.13) closed connection to service tom
[2010/12/15 21:03:48, 0] lib/util_sock.c:539(read_fd_with_timeout)
[2010/12/15 21:03:48, 0] lib/util_sock.c:1491(get_peer_addr_internal)
getpeername failed. Error was Transport endpoint is not connected
read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer.
[2010/12/15 22:37:31, 1] smbd/service.c:1063(make_connection_snum)
ramuh (192.168.2.13) connect to service tom initially as user tom (uid=1000, gid=1000) (pid 2975)
[2010/12/15 22:38:37, 0] smbd/nttrans.c:2123(call_nt_transact_ioctl)
call_nt_transact_ioctl(0x1401c4): Currently not implemented.
[2010/12/15 22:40:08, 1] smbd/service.c:1063(make_connection_snum)
ramuh (192.168.2.13) connect to service MythTV initially as user mythtv (uid=108, gid=117) (pid 2975)
[2010/12/15 22:40:31, 0] printing/print_cups.c:103(cups_connect)
Unable to connect to CUPS server localhost:631 - Connection refused
[2010/12/15 22:40:31, 0] printing/print_cups.c:103(cups_connect)
Unable to connect to CUPS server localhost:631 - Connection refused
[2010/12/15 22:48:31, 1] smbd/service.c:1240(close_cnum)
ramuh (192.168.2.13) closed connection to service MythTV
[2010/12/15 22:53:31, 0] printing/print_cups.c:103(cups_connect)
Unable to connect to CUPS server localhost:631 - Connection refused
[2010/12/15 22:53:31, 0] printing/print_cups.c:103(cups_connect)
Unable to connect to CUPS server localhost:631 - Connection refused
[2010/12/15 23:06:31, 0] printing/print_cups.c:103(cups_connect)
Unable to connect to CUPS server localhost:631 - Connection refused
[2010/12/15 23:06:31, 0] printing/print_cups.c:103(cups_connect)
Unable to connect to CUPS server localhost:631 - Connection refused
[2010/12/15 23:19:32, 0] printing/print_cups.c:103(cups_connect)
Unable to connect to CUPS server localhost:631 - Connection refused
[2010/12/15 23:19:32, 0] printing/print_cups.c:103(cups_connect)
Unable to connect to CUPS server localhost:631 - Connection refused
[2010/12/15 23:32:32, 0] printing/print_cups.c:103(cups_connect)
Unable to connect to CUPS server localhost:631 - Connection refused
[2010/12/15 23:32:32, 0] printing/print_cups.c:103(cups_connect)
Unable to connect to CUPS server localhost:631 - Connection refused
[2010/12/15 23:45:33, 0] printing/print_cups.c:103(cups_connect)
Unable to connect to CUPS server localhost:631 - Connection refused
[2010/12/15 23:45:33, 0] printing/print_cups.c:103(cups_connect)
Unable to connect to CUPS server localhost:631 - Connection refused
[2010/12/15 23:58:33, 0] printing/print_cups.c:103(cups_connect)
Unable to connect to CUPS server localhost:631 - Connection refused
[2010/12/15 23:58:33, 0] printing/print_cups.c:103(cups_connect)
Unable to connect to CUPS server localhost:631 - Connection refused
[2010/12/16 00:11:34, 0] printing/print_cups.c:103(cups_connect)
Unable to connect to CUPS server localhost:631 - Connection refused
[2010/12/16 00:11:34, 0] printing/print_cups.c:103(cups_connect)
Unable to connect to CUPS server localhost:631 - Connection refused
[2010/12/16 00:14:33, 1] smbd/service.c:1240(close_cnum)
ramuh (192.168.2.13) closed connection to service tom
[2010/12/16 16:24:39, 0] printing/print_cups.c:103(cups_connect)
Unable to connect to CUPS server localhost:631 - Connection refused
[2010/12/16 16:24:39, 0] printing/print_cups.c:103(cups_connect)
Unable to connect to CUPS server localhost:631 - Connection refused
Here is my smb.conf
Code:
#======================= Global Settings =======================
[global]
log file = /var/log/samba/log.%m
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
obey pam restrictions = yes
map to guest = bad user
encrypt passwords = yes
passwd program = /usr/bin/passwd %u
passdb backend = tdbsam
wins support = true
dns proxy = no
server string = %h Server
unix password sync = yes
workgroup = WORKGROUP
os level = 20
security = user
syslog = 0
panic action = /usr/share/samba/panic-action %d
usershare allow guests = yes
max log size = 1000
pam password change = yes
[printers]
comment = All Printers
browseable = no
path = /var/spool/samba
printable = yes
guest ok = no
read only = yes
create mask = 0700
[print$]
comment = Printer Drivers
path = /var/lib/samba/printers
browseable = yes
read only = yes
guest ok = no
[MythTV]
writeable = yes
path = /home/mythtv
force directory mode = 770
force group = mythtv
force create mode = 770
force user = mythtv
comment = MythTV Content Share
valid users = tom
create mode = 770
directory mode = 770
[homes]
force create mode = 750
comment = Home Directory
writeable = yes
valid users = @users
create mode = 750
force directory mode = 750
directory mode = 750
[Web]
writeable = yes
path = /home/www
force directory mode = 770
force group = www-data
force create mode = 770
force user = tom
hide dot files = no
comment = Web Hosting Directory Share
valid users = tom
create mode = 770
directory mode = 770
[Public]
writeable = yes
path = /home/public
force directory mode = 770
force group = nogroup
force create mode = 770
force user = nobody
comment = Public Share Directory
public = yes
create mode = 770
directory mode = 770
Finally I have tried several of the security policies changes under Windows 7 (unfortunately I can't remember which) and this hasn't helped. The issue first happened just before Christmas so I guess either Windows or the server did an update at that time which has caused this issue.
Hopefully someone has experienced the same issue because I am unsure where to go to find the best support if this is a Windows issue.
If it's windows7 that's not connecting, windows7 may be able to join group.
Also check /etc/host or guest allow(not sure) on server, it may have updated while your machine was not on network.
I'm not sure what you mean by 'windows7 may be able to join group'?
I have a public share using samba which does have guest enabled, although I am unable to access this share either it is still prompting for a username.
The text with /etc/host is:
Code:
tom@bahamut:~$ cat /etc/hosts
127.0.0.1 localhost
127.0.1.1 bahamut.cable.virginmedia.net bahamut
# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
Does that help at all?
I can't see how my config file would be the problem as this has been working perfectly for months, I'm having a look through the options but so far to no avail.
Windows7 has join group feature under network & sharing center.
You can either create another group or join group.
I don't know if it will join a linux group, but worth a shot.
Unfortunately that didn't see to help either, not sure you can join a Linux group either. Interestingly I fired up the Windows Network Diagnostics and it claims the problem is: 'The remote device or resource won't accept the connection'.
Short version: Try using the Synaptic Package Manager to "re-install" the samba package. This option will not overwrite your configuration files (although you should back them up in case).
Long version: I have no clue why this worked. I experienced a similar problem. I had 64-bit Windows 7 systems happily accessing Ubuntu 10.04 file shares (as both network shares and mapped drives). Then, at some point that I sadly failed to document (i.e. at some point during a series of Windows and Ubuntu/Linux updates) the file shares stopped working, for no apparent reason. And, more curiously, the failure happened in stages: first the server stopped showing up in the "Network", but could still be browsed if I typed in the server name, and the mapped drives continued to work; second, everything went down (net view resulted in error code 53, network diagnostics resulted in "The remote device or resource won't accept the connection"). Throughout, my settings on both the Win 7 and Ubuntu boxes were unchanged, as were their network settings and availability.
In desperation, I decided to uninstall Samba and re-build the configuration from scratch. As an interim step, I tried the "re-install" option for Samba in the package manager. Magically, I have file access again, though I still can't see the server in the Win 7 "Network" list.
Go figure.
I just gave that a go and no such luck. I tried the reinstall method, no change even with a restart of both machines. I then tried reinstall after removing first and still nothing.
I'm pretty sure whatever has changed is my Windows 7 machine now as the shares work on my house-mate's machine which is also using Windows 7 x64 and the shares are still available under XP and Linux.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.