Samba error when trying to connect to shares
Hey guys I am getting the error
lib/util_sock.c:read_socket_with_timeout whenever I try to connect to my samba shares. Any ideas on the problem. I am using SMB4K to connect to my samba shares. Code:
#======================= Global Settings ======================= output of mount command on samba server Code:
/dev/hda1 on / type ext3 (rw,errors=remount-ro) Code:
total 20 Code:
sudo smbpasswd -a remyforbes777 Code:
testparm /etc/samba/smb.conf |
Link to PCAP file for samba session http://www.cinci2600.com/?fuseaction=download.go&id=21http://www.cinci2600.com/?fuseaction=download.go&id=20[/URL]
|
Recommendations:
1. Trim down your smb.conf dump to just the relevant material, and enclose it in the CODE tags. 2. Post the results of running the command testparm, and enclose it in the CODE tags. 3. Remove the excessive ASCII dump from your sniffer. Instead upload and link the pcap file. 4. Specify the filter options that were used in your sniffing. 5. Show the output of mount on the samba server, and enclose it in the CODE tags. 6. Post the permissions of the shares on the filesystem on the samba server, and enclose them in the CODE tags. 7. Show the command you used to add the user remyforbes777 to your samba access list, and enclose it in the CODE tags. 8. Post any INPUT filter rules on your samba server, and any OUTPUT filter rules on your client, and enclose them in the CODE tags. |
No testparm output from you, but here is what I got:
Code:
int0x80:~$ testparm /tmp/smb.conf If you only issued the command smbpasswd then your user was not added, that could be part of the problem. If you included any flags/parameters, please specify them along with the command. Include any relevant output. Also, probably inconsequential to your problem, you should not have your share owned by root with permissions 777. If everyone can read, write, and execute, then make the contents owned by a non-privileged user. That is just speaking from a system administration and security perspective on ownership and permissions. Checked the pcap file, few issues: 1. Where are your filters? You didn't specify any in your thread and there is traffic from or to two other public IP addresses in your dump. 2. You don't have a complete session in your dump. You start with the client and server terminating a session (your FIN/ACKs), and then show a new session starting; but we never see what happens in the new session. Make sure you start sniffing before you begin your samba session, then stop sniffing after the samba session is over. Please also use filters. You didn't respond with any firewall rules? Were there any? My guess right now is a problem with the setup of samba itself, and not a network issue. Then again, I don't have all the pieces yet :) |
I am aware of the permissions issue. It was a temporary thing. What is funny is the /mnt/mediashare2 does not show as being mounted but it is. I can navigate to it and also when samba was working right I could connect to it.
There is not any filters because I didn't use any. I will do another one and include filters. No firewall rules at all. sudo smbpasswd -a remyforbes777 is the specific exact command I used. New pcap file had been downloaded. |
Based on your pcap file (PS: your link doesn't work), I don't think it is a network issue at all. While you are not conducting a full samba session, the machines can still see and talk to each other just fine. This leads me to believe the error lies with the samba setup. Have you at least fixed your smb.conf such that testparm checks out alright? Also what resources/sites did you use/read in setting everything up? Honestly samba is very simple to set up, and it could just be that the sites you used were inaccurate or out-dated.
|
The link is now fixed. I forgot to change the link when i uploaded the new pcap file. The thing is, I have not changed anything with my smb.conf file and it has been working correctly for almost a year, then out of the blue it stopped working.
|
What other changes have happened on the samba server? Did any binaries change (eg: dist-upgrade)? Do you have an md5 of your smb.conf before these problems occurred? Is it the same as the md5 of the current smb.conf?
Have you tried just mounting the shares with smbmount or mount -t smbfs? These are items from previous posts that I requested but still haven't seen: Quote:
|
Quote:
|
Oh I see, you edited your original post yesterday... Thanks for pointing that out :rolleyes:
Here are some of the results from my setup: 2. Post the results of running the command testparm, and enclose it in the CODE tags. Code:
[global] Code:
/dev/md2 on /files type ext3 (rw) Code:
$ tree -d -L 2 /share/ |
Okay, I totally forgot about the tree command. I will re edit my initial post and include that information.
|
All times are GMT -5. The time now is 12:48 PM. |