Date: Tue, 16 Apr 2013 23:50:24 -0700 (PDT) From: Beeblebrox <zaphod@berentweb.com> To: freebsd-questions@freebsd.org Subject: FreeBSD as Samba Server and Windows as Client Message-ID: <1366181424913-5804418.post@n5.nabble.com> In-Reply-To: <CAOgwaMudEAcCPE-NiJyVk6sLfkH%2Bc06XP11nfTOQ7Ys2n80=%2BQ@mail.gmail.com> References: <CAOgwaMvTQm-_hE0Dbq0GYXa4rD8WaT8WBY63WBwjSzCkoz5Rog@mail.gmail.com> <516DC569.2030409@gmail.com> <CAOgwaMudEAcCPE-NiJyVk6sLfkH%2Bc06XP11nfTOQ7Ys2n80=%2BQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
There are just so many things that could go wrong on a samba setup that it is beyond funny in my opinion. You have authentication method (kerberos, pam, txt), ports, winbind and dns just to list a few. I suggest you start samba in debug mode and enable full logging. The documentation from samba its self is probably going to be much more comprehensive: http://www.samba.org/samba/docs/man/manpages-3/smbd.8.html I would also try to connect with various clients like a linux, XP, vista or win7. These connection attempts should generate comprehensive logs when samba is running in debug mode. You can then start to get some idea why the connection is being refused by reading through the generated logs. Also, several how-to's already exist on the FreeBSD forums - as an example: http://forums.freebsd.org/showthread.php?t=36137 ----- 10-Current-amd64-using ccache-portstree merged with marcuscom.gnome3 & xorg.devel -- View this message in context: http://freebsd.1045724.n5.nabble.com/FreeBSD-as-Samba-Server-and-Windows-as-Client-tp5804306p5804418.html Sent from the freebsd-questions mailing list archive at Nabble.com.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1366181424913-5804418.post>