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 Samba server is a Solaris 8 SPARC box.
Here is my smb.conf file;
[global]
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
[team]
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 -L 192.168.1.221 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.
Sl?inte,
David
"Build a man a fire he'll be warm for a day, set a man on fire and
he'll be
warm for the rest of his life" - Terry Pratchett
Checkout my photos - http://www.panoramio.com/user/1113507
