More weirdnesses: Now I set my Samba server to share level (no domain
logons, since that wouldn't work). Machines 192.168.1.2 and 192.168.1.3 (a
noname and a HP Pavilion Win95 box) can see the server (192.168.1.1), but
it does not even show up in the network neighborhood of 192.168.1.20 (a
Compaq Armada 6500 with Win95). Furthermore, if I try to connect to the
Compaq via smbclient, it gives me a
Added interface ip=192.168.1.1
bcast=192.168.1.255 nmask=255.255.255.0 error connecting to
192.168.1.20:139 (Connection refused)
Connection to Traveller failed
The two Win95 machines can connect to the Compaq OK and the Linux machine
can ping the Compaq (and vice versa). Looks like a NetBIOS issue, I guess.
Is it a conspiracy by Microsoft to keep us from using Linux in
heterogenous networks or did I just miss something?
I attached my smb.conf - I hope that's OK (it's not all that big).
Hope you can help me,
Juergen
# Samba config file created using SWAT
# from Kater.NanoSoft (192.168.1.2)
# Date: 1999/02/21 14:38:39
# Global parameters
workgroup = NANOSOFT
#domain logons = Yes
os level = 33
preferred master = Yes
domain master = Yes
local master = Yes
guest account = guest
#update passwords = Yes
#encrypt passwords = Yes
wins support = Yes
security = share
[root]
path = /
read only = No
guest ok = No
[printers]
comment = All Printers
path = /tmp
guest ok = Yes
print ok = Yes
browseable = No
[files]
comment = files
path = /files
writeable=yes
guest ok = Yes
force directory mode = 0755
[netlogon]
path=/usr/local/samba/netlogon
guest ok = no
writeable = no
