[Samba] Samba 2.2.0. & Vista Business Edition
nkadel at gmail.com
Sun Apr 18 08:21:20 MDT 2010
And you should seriously consider updating that Solaris 8 box. Even
though Solaris 8 is nominally supported until 2012, is Solaris 8
almost 10 years old. Oracle, which bought Sun, seems to be pushing the
upgrade, even the free upgrade to OpenSolaris, at
On Fri, Apr 16, 2010 at 8:55 PM, Damien Dye <damien.j.dye at googlemail.com> wrote:
> Version 2.2 pre dates vista you should be looking to update to a minimum of 3.4 to ensure compatiblity.
> If you turn off ntlm v2 on vista and sign and seal does it work then ?
> -----Original Message-----
> From: David McWilliams <davidkmcw at gmail.com>
> Sent: 16 April 2010 08:16 PM
> To: samba at lists.samba.org
> Subject: [Samba] Samba 2.2.0. & Vista Business Edition
> I'm trying to get a new Vista Business client to connect a newly created
> Samba server. Windows XP clients connect without issue.
> I have tried changing 'Network Security: Lan Manager Authentication Level'
> to 'Send LM & NTLM use NTLMv2 session security if negotiated', as suggested
> on other sites, but to no avail. We have a domain, but both the Samba server
> & the Vista client are part of a workgroup & not on the domain. The client &
> server can ping each other by hostname & ip address.
> The Samba server is a Solaris 8 SPARC box.
> Here is my smb.conf file;
> netbios name = SAMBA
> server string = Samba Server 2.2.0
> security = SHARE
> log level = 2
> log file = /var/tmp/samba.out.%m
> max log size = 50
> dns proxy = No
> path = /team
> read only = No
> guest ok = Yes
> strict sync = Yes
> oplocks = No
> Browsing to either the IP of hostname of the Samba server, gives the same
> error - 'Windows cannot access \\SAMBA <file://samba/>, Check the spelling
> of the name...'. Running smbclient gives;
> bash-2.03# ./smbclient -L 192.168.1.221
> INFO: Debug class all level = 2 (pid 5737 from pid 5737)
> added interface ip=192.168.1.253 bcast=192.168.1.255 nmask=255.255.255.0
> session request to 192.168.1.221 failed (Called name not present)
> session request to 192 failed (Called name not present)
> session request to *SMBSERVER failed (Called name not present)
> I appreciate any insight anyone can provide.
More information about the samba