SUSE 10.2 Really Strange Windows Sharing Problem (smb.conf included)

Agentx86 · 02-15-2007, 08:29 PM

Hello, I am running openSUSE 10.2 on an AMD64 platform. My network consists of this SUSE computer, a Dang Small Linux box running a game server, an iBook G3, 2 WinXP machines, and 1 Win2000 machine. All firewalls are off with the exception of the windows firewall (which does allow sharing from the other comps) and Zone Alarm on the 2000 machine, which is set to trust a certain range of IP addresses.

My SUSE box is set up to be the master browser and domain controller on network "MSHOME." All computers are set to this workgroup. With Windows I can access my SUSE box with no trouble, and with my SUSE box I can access Windows Shares provided that I use the IP address of the Windows machine instead of the hostname.

All the computers on the network appear in Konqueror, but when attempting to connect to them by name, without naming by IP, it times out. Trying to connect on the command line always results in SUSE trying to connect to 208.67.219.40

However, typing "findsmb" does show several of the network computers and their appropriate IP addresses.
I have done quite a bit of research, and some reading on this forum, but I cannot for the life of me figure out what's going on.

Here's my config file, and thanks.

Code:

# smb.conf is the main Samba configuration file. You find a full commented
# version at /usr/share/doc/packages/samba/examples/smb.conf.SUSE if the
# samba-doc package is installed.
# Date: 2006-11-27
[global]
workgroup = MSHOME
printcap name = cups
cups options = raw
map to guest = Bad User
include = /etc/samba/dhcp.conf
logon path = \\%L\profiles\.msprofile
logon home = \\%L\%U\.9xprofile
logon drive = P:
usershare allow guests = Yes
usershare owner only = False
usershare max shares = 100
add machine script = /usr/sbin/useradd  -c Machine -d /var/lib/nobody -s /bin/false %m$
domain logons = yes
domain master = yes
preferred master = yes
os level = 65
wins support = Yes
dns proxy = no
restrict anonymous = no
guest ok = yes
max protocol = NT
acl compatibility = 
ldap ssl = No
server signing = Auto
log file = /home/agent86/sambalog.txt
lm interval = 30

[homes]
comment = Home Directories
valid users = %S, %D%w%S
read only = No
inherit acls = Yes

[possum]
comment = Network Profiles Service
path = /home/agent86/Desktop/Possum/
read only = no
create mask = 0600
directory mask = 0700
case sensitive = no
strict locking = no
msdfs proxy = no

[users]
comment = All users
path = /home
read only = No
inherit acls = Yes
veto files = /aquota.user/groups/shares/

[groups]
comment = All groups
path = /home/groups
read only = No
inherit acls = Yes

[printers]
comment = All Printers
path = /var/tmp
printable = Yes
create mask = 0600
use client driver = yes

[print$]
comment = Printer Drivers
path = /var/lib/samba/drivers
write list = @ntadmin root
force group = ntadmin
create mask = 0664
directory mask = 0775

[netlogon]
comment = Network Logon Service
path = /var/lib/samba/netlogon
write list = root

swerdna · 02-20-2007, 02:52 AM

Quote:

Originally Posted by Agentx86

Hello, I am running openSUSE 10.2 on an AMD64 platform. My network consists of this SUSE computer, a Dang Small Linux box running a game server, an iBook G3, 2 WinXP machines, and 1 Win2000 machine. All firewalls are off with the exception of the windows firewall (which does allow sharing from the other comps) and Zone Alarm on the 2000 machine, which is set to trust a certain range of IP addresses.

My SUSE box is set up to be the master browser and domain controller on network "MSHOME." All computers are set to this workgroup. With Windows I can access my SUSE box with no trouble, and with my SUSE box I can access Windows Shares provided that I use the IP address of the Windows machine instead of the hostname.

All the computers on the network appear in Konqueror, but when attempting to connect to them by name, without naming by IP, it times out. Trying to connect on the command line always results in SUSE trying to connect to 208.67.219.40

However, typing "findsmb" does show several of the network computers and their appropriate IP addresses.
I have done quite a bit of research, and some reading on this forum, but I cannot for the life of me figure out what's going on.

Here's my config file, and thanks.

Code:

no point re-quoting this

If you want to improve browsing

Code:

[global]
workgroup = MSHOME
printcap name = cups
cups options = raw
map to guest = Bad User
include = /etc/samba/dhcp.conf
logon path = \\%L\profiles\.msprofile
logon home = \\%L\%U\.9xprofile
logon drive = P:
usershare allow guests = Yes
usershare owner only = False
usershare max shares = 100
add machine script = /usr/sbin/useradd  -c Machine -d /var/lib/nobody -s /bin/false %m$
#domain logons = yes
#domain master = yes
preferred master = yes
security = user
passdb backend = tdbsam
os level = 65
#wins support = Yes
#dns proxy = no
#restrict anonymous = no
#guest ok = yes
#max protocol = NT
#acl compatibility = 
#ldap ssl = No
#server signing = Auto
#log file = /home/agent86/sambalog.txt
#lm interval = 30

Turn off wins server, make the Susebox a local master browser and get rid of the Linux server stuff - yiu're only a workgroup. Give that a go.
If you want easy access to a share it should then have this complexion:

Code:

[possum]
path = /home/agent86/Desktop/Possum/
read only = No
force group = users
force user = agent86
#guest ok = Yes #turn this on for guest access, including the entire internet

See how you go
Swerdna

Agentx86 · 02-24-2007, 10:45 PM

Thanks for your suggestions, but even after implementing all of the above, I still cannot browse the network, even when a "findsmb" command shows that my suse box is the master browser. Whenever I try to browse by hostname, it tries to connect to some other IP address, it's always the same each time, no matter what the hostname. I can still type in the IP address of the windows machine manually and connect, but that can be a pain. I do only have 6 other computers I connect to, but I will not always be able to come up with an IP address off the top of my head!
I am really enjoying openSUSE 10.2, but I haven't had this problem with any other version of SUSE. I think the entire browsing/mounting system got screwed up in their decision to move away from smbfs to cifs. I now have the kernel module installed that is supposed to restore smbfs support, but browsing is still not working.
I need help!

swerdna · 02-24-2007, 11:18 PM

Quote:

Originally Posted by Agentx86

Thanks for your suggestions, but even after implementing all of the above, I still cannot browse the network, even when a "findsmb" command shows that my suse box is the master browser. Whenever I try to browse by hostname, it tries to connect to some other IP address, it's always the same each time, no matter what the hostname. I can still type in the IP address of the windows machine manually and connect, but that can be a pain. I do only have 6 other computers I connect to, but I will not always be able to come up with an IP address off the top of my head!
I am really enjoying openSUSE 10.2, but I haven't had this problem with any other version of SUSE. I think the entire browsing/mounting system got screwed up in their decision to move away from smbfs to cifs. I now have the kernel module installed that is supposed to restore smbfs support, but browsing is still not working.
I need help!

Well I don't know what to say except to go through a checklist

Duplicate IP's
IP's all on the same subnet (Linux --> kdesu ifconfig; windows --> ipconfig/all)
Consistent workgroup name
declare NetBIOS name of LinuxBox in smb.conf = same as hostname in Yast?
Enable NBT ping in nsswitch
Consistency between hostnames in hosts file, NetBIOS names in lmhosts file, and and NetBIOS names in windows "my computer" and smb.conf.

When my LAN falls apart I check carefully which machines can be seen from which machines and single out the bad one (it sounds like your SuseBox) and re-network it, using methodical references. ED some Samba tute's here. It'll be some silly little thing that's not obvious.
G luck
Swerdna

Agentx86 · 02-25-2007, 09:33 AM

Thanks for the help!
I edited my nsswitch.conf to include wins resolution.
Just to throw another thing into the ring, I can connect to the sole Win2000 machine by hostname, but not any of the XP machines. Maybe I have something screwy going on with my XP machines...
Still looking for that silly, obvious little thing!