I have the same problem with wep (and Karmic.)
(BTW, when I checked this thread this morning, I was surprised to find myself rooting for a poster on a help thread! Go dmizer! Crush the bug! Find a workaround!)
Printable View
I have the same problem with wep (and Karmic.)
(BTW, when I checked this thread this morning, I was surprised to find myself rooting for a poster on a help thread! Go dmizer! Crush the bug! Find a workaround!)
Hello,
Another karmic upgrade problem... I'm sorry if the answer is somewhere in the 117 pages, I couldn't read everything :)
I upgraded from jaunty to karmic a few days ago and cannot mount samba shares anymore even manually. I used to (and still can on another computer not yet upgraded) be able to manually mount typing:
sudo mount //netbiosname/sharename mount_point -o username=myname,password=mypsswd
This doesn't work anymore on karmic. I checked smbfs, samba, modified nsswitch.conf, installed winbind, tried different versions of the manual mount (adding -t cifs, adding options like iocharset=utf8,file_mode=0777,dir_mode=0777 or noserverino and nounix), nothing works. I get a mount error(110), timed out or something.
Using nautilus, I do get prompted for my password, but then after a little bit, I get an error "impossible to mount the windows share" (translated from French so something like that :)).
Sorry if the solution is obvious or already said somewhere, I just can't find it!
Thanks a lot in advance.
What works in my still-jaunty computer is
That doesn't work anymore in my new-karmic computer. I also triedCode:sudo mount //sirocco/wwwroot/ /media/test/ -o username=myname,password=mypassword
for instance. Same, works with jaunty, not with karmic.Code:sudo mount -t cifs //sirocco/wwwroot/ /media/test/ -o username=myname,password=mypassword,iocharset=utf8,file_mode=0777,dir_mode=0777
I only did an upgrade, and it used to work with jaunty on the same computer...
The error (that I get after 5 min maybe, as if it was trying to connect but couldn't) is
(kind of, connexion ended because the waiting time expired)Code:mount error(110): Connexion terminée par expiration du délai d'attente
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
Thanks for your help!
Hi dmizer,
I do have the firewall enabled (Gufw 9.10.4), but that was already the case before the upgrade. I tried to turn it off, in which case iptables givesCode:Chain INPUT (policy DROP)
target prot opt source destination
ufw-before-logging-input all -- anywhere anywhere
ufw-before-input all -- anywhere anywhere
ufw-after-input all -- anywhere anywhere
ufw-after-logging-input all -- anywhere anywhere
ufw-reject-input all -- anywhere anywhere
ufw-track-input all -- anywhere anywhere
Chain FORWARD (policy DROP)
target prot opt source destination
ufw-before-logging-forward all -- anywhere anywhere
ufw-before-forward all -- anywhere anywhere
ufw-after-forward all -- anywhere anywhere
ufw-after-logging-forward all -- anywhere anywhere
ufw-reject-forward all -- anywhere anywhere
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
ufw-before-logging-output all -- anywhere anywhere
ufw-before-output all -- anywhere anywhere
ufw-after-output all -- anywhere anywhere
ufw-after-logging-output all -- anywhere anywhere
ufw-reject-output all -- anywhere anywhere
ufw-track-output all -- anywhere anywhere
Chain ufw-after-forward (1 references)
target prot opt source destination
Chain ufw-after-input (1 references)
target prot opt source destination
RETURN udp -- anywhere anywhere udp dpt:netbios-ns
RETURN udp -- anywhere anywhere udp dpt:netbios-dgm
RETURN tcp -- anywhere anywhere tcp dpt:netbios-ssn
RETURN tcp -- anywhere anywhere tcp dpt:microsoft-ds
RETURN udp -- anywhere anywhere udp dpt:bootps
RETURN udp -- anywhere anywhere udp dpt:bootpc
RETURN all -- anywhere anywhere ADDRTYPE match dst-type BROADCAST
Chain ufw-after-logging-forward (1 references)
target prot opt source destination
LOG all -- anywhere anywhere limit: avg 3/min burst 10 LOG level warning prefix `[UFW BLOCK] '
Chain ufw-after-logging-input (1 references)
target prot opt source destination
LOG all -- anywhere anywhere limit: avg 3/min burst 10 LOG level warning prefix `[UFW BLOCK] '
Chain ufw-after-logging-output (1 references)
target prot opt source destination
Chain ufw-after-output (1 references)
target prot opt source destination
Chain ufw-before-forward (1 references)
target prot opt source destination
ufw-user-forward all -- anywhere anywhere
Chain ufw-before-input (1 references)
target prot opt source destination
ACCEPT all -- anywhere anywhere
ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED
ufw-logging-deny all -- anywhere anywhere state INVALID
DROP all -- anywhere anywhere state INVALID
ACCEPT icmp -- anywhere anywhere icmp destination-unreachable
ACCEPT icmp -- anywhere anywhere icmp source-quench
ACCEPT icmp -- anywhere anywhere icmp time-exceeded
ACCEPT icmp -- anywhere anywhere icmp parameter-problem
ACCEPT icmp -- anywhere anywhere icmp echo-request
ACCEPT udp -- anywhere anywhere udp spt:bootps dpt:bootpc
ufw-not-local all -- anywhere anywhere
ACCEPT all -- BASE-ADDRESS.MCAST.NET/4 anywhere
ACCEPT all -- anywhere BASE-ADDRESS.MCAST.NET/4
ufw-user-input all -- anywhere anywhere
Chain ufw-before-logging-forward (1 references)
target prot opt source destination
Chain ufw-before-logging-input (1 references)
target prot opt source destination
Chain ufw-before-logging-output (1 references)
target prot opt source destination
Chain ufw-before-output (1 references)
target prot opt source destination
ACCEPT all -- anywhere anywhere
ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED
ufw-user-output all -- anywhere anywhere
Chain ufw-logging-allow (0 references)
target prot opt source destination
LOG all -- anywhere anywhere limit: avg 3/min burst 10 LOG level warning prefix `[UFW ALLOW] '
Chain ufw-logging-deny (2 references)
target prot opt source destination
LOG all -- anywhere anywhere limit: avg 3/min burst 10 LOG level warning prefix `[UFW BLOCK] '
Chain ufw-not-local (1 references)
target prot opt source destination
RETURN all -- anywhere anywhere ADDRTYPE match dst-type LOCAL
RETURN all -- anywhere anywhere ADDRTYPE match dst-type MULTICAST
RETURN all -- anywhere anywhere ADDRTYPE match dst-type BROADCAST
ufw-logging-deny all -- anywhere anywhere limit: avg 3/min burst 10
DROP all -- anywhere anywhere
Chain ufw-reject-forward (1 references)
target prot opt source destination
Chain ufw-reject-input (1 references)
target prot opt source destination
Chain ufw-reject-output (1 references)
target prot opt source destination
Chain ufw-track-input (1 references)
target prot opt source destination
Chain ufw-track-output (1 references)
target prot opt source destination
ACCEPT tcp -- anywhere anywhere state NEW
ACCEPT udp -- anywhere anywhere state NEW
Chain ufw-user-forward (1 references)
target prot opt source destination
RETURN all -- anywhere anywhere
Chain ufw-user-input (1 references)
target prot opt source destination
ACCEPT tcp -- anywhere anywhere tcp dpt:ftp
ACCEPT tcp -- anywhere anywhere tcp dpt:ssh
ACCEPT udp -- anywhere anywhere udp dpt:ssh
ACCEPT tcp -- anywhere anywhere tcp dpt:4662
ACCEPT udp -- anywhere anywhere udp dpt:4672
ACCEPT tcp -- anywhere anywhere tcp dpt:5900
ACCEPT udp -- anywhere anywhere udp dpt:5900
RETURN all -- anywhere anywhere
Chain ufw-user-logging-forward (0 references)
target prot opt source destination
Chain ufw-user-logging-input (0 references)
target prot opt source destination
Chain ufw-user-logging-output (0 references)
target prot opt source destination
Chain ufw-user-output (1 references)
target prot opt source destination
RETURN all -- anywhere anywhere
but it still doesn't work...Code:Chain INPUT (policy ACCEPT)
target prot opt source destination
ufw-before-logging-input all -- anywhere anywhere
ufw-before-input all -- anywhere anywhere
ufw-after-input all -- anywhere anywhere
ufw-after-logging-input all -- anywhere anywhere
ufw-reject-input all -- anywhere anywhere
ufw-track-input all -- anywhere anywhere
Chain FORWARD (policy ACCEPT)
target prot opt source destination
ufw-before-logging-forward all -- anywhere anywhere
ufw-before-forward all -- anywhere anywhere
ufw-after-forward all -- anywhere anywhere
ufw-after-logging-forward all -- anywhere anywhere
ufw-reject-forward all -- anywhere anywhere
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
ufw-before-logging-output all -- anywhere anywhere
ufw-before-output all -- anywhere anywhere
ufw-after-output all -- anywhere anywhere
ufw-after-logging-output all -- anywhere anywhere
ufw-reject-output all -- anywhere anywhere
ufw-track-output all -- anywhere anywhere
Chain ufw-after-forward (1 references)
target prot opt source destination
Chain ufw-after-input (1 references)
target prot opt source destination
Chain ufw-after-logging-forward (1 references)
target prot opt source destination
Chain ufw-after-logging-input (1 references)
target prot opt source destination
Chain ufw-after-logging-output (1 references)
target prot opt source destination
Chain ufw-after-output (1 references)
target prot opt source destination
Chain ufw-before-forward (1 references)
target prot opt source destination
Chain ufw-before-input (1 references)
target prot opt source destination
Chain ufw-before-logging-forward (1 references)
target prot opt source destination
Chain ufw-before-logging-input (1 references)
target prot opt source destination
Chain ufw-before-logging-output (1 references)
target prot opt source destination
Chain ufw-before-output (1 references)
target prot opt source destination
Chain ufw-reject-forward (1 references)
target prot opt source destination
Chain ufw-reject-input (1 references)
target prot opt source destination
Chain ufw-reject-output (1 references)
target prot opt source destination
Chain ufw-track-input (1 references)
target prot opt source destination
Chain ufw-track-output (1 references)
target prot opt source destination
A disabled firewall will look like this: http://pastebin.com/f564e1a42, so even though you thought the firewall was disabled ... it was not.
I suspect that your problem is directly related to your firewall rules. You may be successful by following the directions in the 6th link in my sig under "Problem 4"
Sorry... it doesn't seem like a firewall problem. After disabling it (uncheck the "activated" case under Gufw), I also restarted the computer this time, and then iptables actually gives
Still doesn't work though...Code:Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
This being said, that would probably be best if I added the samba rules to ufw instead of disabling it anyway. I had a question about it: when you say "Make sure to change 192.168.29.0/24 so that it matches your own network IP range.", if ifconfig gives 134.89.8.143 for wlan0 but 134.89.11.129 for eth0 (and I'm at work so that my network will be different at home...), should I use 134.89.8.0 and 134.89.11.0 and run the commands for these 2 IP ranges?
In case it helps: if I run the command without the password, for instance
sudo mount //sirocco/wwwroot/ /media/test/ -o username=myname
I'm actually prompted for my password... but then it hangs, and time out.
(BTW I didn't mention that I tried to check the proposed updates since someone else mentioned it, but there was nothing related to samba when I looked)
Thanks a lot for your help. I'm starting to wonder if there's a bug somewhere. Maybe I'll try a clean install at some point. Just wish I could avoid it...
I am having the same problem as kalyp. All my 9.10 machines can no longer mount Buffalo TeraServer. my 9.04 machines have no problem. no firewalls. My fstab entries looks something like this:
//server/share /home/user/net-public cifs credentials=/home/user/.smbcred,noperm,nocase,user,iocharset=utf8,file_mo de=0777,dir_mode=0777 0 0
When I try to mount manually, I get the following error
/etc/mount error(11): Resource temporarily unavailable
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
I have not found anything useful when searching for information on that error.
Certainly seems like the problem I'm trying to fix is because of WiFi as shutdown with eth0 in use instead of WiFi is pretty instant, even with the CIFS shares mounted.