From: Jeff Layton <jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>
To: Shirish Pargaonkar
<shirishpargaonkar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Mike <miked-yxPvCyoe84a+XT7JhA+gdA@public.gmane.org>,
linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: CIFS Not Responding Error On Working System
Date: Fri, 29 Apr 2011 09:32:56 -0400 [thread overview]
Message-ID: <20110429093256.3c33cd01@corrin.poochiereds.net> (raw)
In-Reply-To: <BANLkTinoC1d=NBLyzXa61cB+tR-+4F50zg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Fri, 29 Apr 2011 07:13:05 -0500
Shirish Pargaonkar <shirishpargaonkar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> On Thu, Apr 28, 2011 at 2:27 PM, Mike <miked-yxPvCyoe84a+XT7JhA+gdA@public.gmane.org> wrote:
> > Hopefully I am submitting this to the correct email list. I have been doing
> > Google searches and haven't found anyone that has the same string in their
> > log file, so I'm looking for help on this issue.
> >
> > Recently I lost my hard drive and had to reinstall Debian. I am now getting
> > these errors in /var/log/syslog and I can't figure out why:
> > Apr 28 11:57:05 rockenfield kernel: [1479867.192022] CIFS VFS: Server peart
> > has not responded in 300 seconds. Reconnecting...
> >
> > The weird thing is that there are no problems. I can view the shares on the
> > remote Windows machine (peart is WinXP 64 SP2) with no problems whatsoever.
> > Also my Windows machine can see my samba shares as well, so both directions
> > work fine and I'm not sure why these messages are occurring.
> >
> >
> > Here is my /etc/fstab (samba/cifs mounts only, trimmed to applicable
> > content):
> > //peart/mp3 /mnt/peart/mp3 cifs
> > defaults,credentials=/etc/samba/smbpass.peart,_netdev 0 0
> > //peart/software /mnt/peart/software cifs
> > defaults,credentials=/etc/samba/smbpass.peart,_netdev 0 0
> > //peart/backup /mnt/peart/backup cifs
> > defaults,credentials=/etc/samba/smbpass.peart,_netdev 0 0
> > //peart/dvd /mnt/peart/dvd cifs
> > defaults,credentials=/etc/samba/smbpass.peart,_netdev 0 0
> >
> >
> > Here is my /etc/samba/smb.conf:
> > [global]
> > workgroup = HOME_NETWORK
> > netbios name = ROCKENFIELD
> > server string = %h server - Debian GNU/Linux
> > dns proxy = no
> > name resolve order = lmhosts host wins bcast
> > interfaces = 192.168.123.0/24 eth1
> > bind interfaces only = yes
> > hosts allow = 192.168.123.
> > log file = /var/log/samba/log.%m
> > max log size = 1000
> > syslog = 0
> > panic action = /usr/share/samba/panic-action %d
> > security = user
> > encrypt passwords = true
> > passdb backend = tdbsam
> > obey pam restrictions = yes
> > unix password sync = yes
> > passwd program = /usr/bin/passwd %u
> > passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:*
> > %n\n *password\supdated\ssuccessfully* .
> > pam password change = yes
> > socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
> > [homes]
> > comment = Home Directories
> > browseable = no
> > read only = no
> > create mask = 0700
> > directory mask = 0700
> > valid users = %S
> > [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
> >
> >
> > I am running Debian wheezy/testing (7.0). The kernel version is
> > 2.6.38-2-amd64. Samba version is 3.5.8~dfsg-1 (obtained from "dpkg -l |
> > grep samba"). This is just a home network, so I don't have a Domain
> > Controller or anything fancy. It's just a Debian box and a WinXP box and
> > I'm sharing files/directories on each side.
> >
> > Any help is greatly appreciated. Thanks!
> > -MikeD
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-cifs" in
> > the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> >
>
> May be some issues like firewall etc.?
> Can you capture wireshark traces on either side and see if you see
> any network in response to a mount reuqest from a cifs client?
To be clear...
What sort of host is "peart" here? WinXP?
--
Jeff Layton <jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>
next prev parent reply other threads:[~2011-04-29 13:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-28 19:27 CIFS Not Responding Error On Working System Mike
[not found] ` <4DB9BFBA.3020403-yxPvCyoe84a+XT7JhA+gdA@public.gmane.org>
2011-04-29 12:13 ` Shirish Pargaonkar
[not found] ` <BANLkTinoC1d=NBLyzXa61cB+tR-+4F50zg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-04-29 13:32 ` Jeff Layton [this message]
[not found] ` <20110429093256.3c33cd01-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2011-04-29 15:06 ` Mike Dillinger
[not found] ` <4DBAD409.9000300-yxPvCyoe84a+XT7JhA+gdA@public.gmane.org>
2011-04-29 21:04 ` Jeff Layton
[not found] ` <20110429170436.22cb8c4c-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2011-05-13 23:39 ` Mike
2011-05-02 11:01 ` Jeff Layton
2011-06-06 7:57 ` kofolamaster
[not found] ` <loom.20110606T095706-912-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2011-06-06 10:32 ` Jeff Layton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110429093256.3c33cd01@corrin.poochiereds.net \
--to=jlayton-eunubhrolfbytjvyw6ydsg@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=miked-yxPvCyoe84a+XT7JhA+gdA@public.gmane.org \
--cc=shirishpargaonkar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox