File Sharing Windoze Network Computers

deepgrewal · 03-17-2005, 06:24 PM

My migration to SuSe is almost complete, except for a few problems and glitches which I have posted here. Anyhow, I have been successful in acquiring an IP address from my router and am able to surf the net wirelessly. However, I am not able to view other computers on my network (all of which are Windoze based). From the Windoze machines, I am also not able to view my SuSe Linux 9.2 machine. What exactly do I need to do to make this happen? I'm certain that I have set up my Workgroup name and Host name correctly. But then again, I am new to Linux so I can't be too certain. Please advise . . .

elsmack · 03-17-2005, 10:21 PM

I'm having the same issues. I could use a little help as well

brundles · 03-18-2005, 07:47 AM

Do you have the Samba service up and running? ('rcsmb status' from should tell you?).

Something else that caught me out is that 9.2 has tightened up the firewall settings compared to previous versions - although YAST does seem to include options in the right places to make these changes as you go.

deepgrewal · 03-18-2005, 09:23 PM

Yes I tried typing in rcsmb status and it is confirmed: Samba is running, yet no communication with Windoze machines.

brundles · 03-19-2005, 06:20 AM

Can you post your smb.conf file?

eadwine · 03-19-2005, 07:10 AM

Before doing all sorts of difficult things.. lower all the firewalls on all the systems for a bit and then inside Samba search (Network - Search in the menu) for the IP numbers you have. You might have the same yippee feeling I just had a few days ago

I had been ripping my hair out for 2.5 months until I made a mistake with my firewall and saw what happened when things were down. All that remained was configuring the firewalls to let the computers in question in.

deepgrewal · 03-19-2005, 04:45 PM

Eadwine, none of my other networked computers have any firewalls up. So I took off the firewall on this computer and still no luck. Perhaps firewalls in Mepis and SuSe are different? I will try this again. Thanx for the reply. Here is my "smb.conf" file:

# 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: 2005-01-28
[global]
workgroup = GREWAL
printing = cups
printcap name = cups
printcap cache time = 750
cups options = raw
printer admin = @ntadmin, root, administrator
username map = /etc/samba/smbusers
map to guest = Bad User
include = /etc/samba/dhcp.conf
logon path = \\%L\profiles\.msprofile
logon home = \\%L\%U\.9xprofile
logon drive = P:
security = user
encrypt passwords = yes
ldap idmap suffix = ou=Idmap
ldap machine suffix = ou=Computers
wins support = no
ldap suffix = dc=example,dc=com

[homes]
comment = Home Directories
valid users = %S
browseable = no
read only = no
inherit acls = yes

[profiles]
comment = Network Profiles Service
path = %H
read only = no
store dos attributes = yes
create mask = 0600
directory mask = 0700

[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
browseable = no

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

eadwine · 03-19-2005, 04:59 PM

My smb.conf is a tad smaller:

Code:

;*******************section global*****************
[global]

# Do something sensible when Samba crashes: mail the admin a backtrace
   panic action = /usr/share/samba/panic-action %d
printing = cups
printcap name = /etc/printcap
load printers = yes
security = user
workgroup = WORKGROUP
netbios name = EADWINE
server string = %h server (Samba %v)
hosts allow = xxx.xxx.x. xxx.xxx.x. xxx.xxx.x. 127.
smb passwd file = /etc/samba/smbpasswd
socket options = IPTOS_LOWDELAY TCP_NODELAY SO_SNDBUF=4096 SO_RCVBUF=4096
encrypt passwords = true
   passdb backend = tdbsam guest
dns proxy = no
max log size = 1000
;*******************section eadwine*****************
[eadwine]
comment = /home/eadwine
path = /home/eadwine
public = yes
guest ok = yes
writeable = yes
;*******************section homes*****************
[homes]
comment = Home Directories
browseable = no
writable = yes
;*******************section printers*****************
[printers]
comment = All Printers
path = /tmp
browseable = no
printable = yes
writable = no
guest ok = yes
create mode = 0700
print command = lpr -P %p -o raw %s -r

Not a clue if this will help you out though..

novice26 · 03-20-2005, 02:27 AM

i too am having the same problem. the only way i could work around it is to actually use the ip of the windows computer to be able to browse. when i click on smb it just gives me a error. not sure if its the same problem but sounds like it. mine works by using the ip addresses at the moment.

fantasysky · 09-25-2005, 12:09 PM

Try turning off the firewall on your network card. Hope this help.

1kyle · 09-26-2005, 02:53 AM

For Samba on SUSE

Open , Read and ALL SHALL BE REVEALED.

Enjoy.

http://www.tweakhound.com/linux/samba/page_1.htm

Cheers

-K

deepgrewal · 10-12-2005, 10:37 AM

Thanx for all of your suggestions guys. I obviously haven't logged on to LQ for a while. So I appreciate your feedback on this otherwise relatively old thread. I will give it a shot and post results.