samba and winXP issue need help

Lleb_KCir · 04-02-2004, 05:30 PM

ok i have samba set up running on a RH9 laptop.

have it configured to go to my /home/ray dir with full access yes read and write.

just opened up port 24 in the firewall for TCP

the issue is this:

on winXP i can via my network places navitage to my workgroup and see the share on my RH box, but when i go to access it i get error:

not able to find path

what more do i need to do in order to gain access to my share on samba?

mega newbie here so please be patient with me. i do have webmin installed and running, i can find the samba controlls in gnome too.

if you need me to post my smb.conf file here so you can tell me what im doing wrong let me know, ill post that tonight when i get home.

win32sux · 04-02-2004, 06:49 PM

Quote:

Originally posted by Lleb_KCir
just opened up port 24 in the firewall for TCP

i'm not sure, but doesn't samba use tcp port 137 and udp ports 138 and 139, or something like that???

does it work if you flush your iptables (i'm guessing local firewall)???

http://www.linuxguruz.com/iptables/s...h-iptables.txt

posting your samba configuration will make it easier for someone to help you with samba, but you need to make sure the issue isn't your firewall rules...

Lleb_KCir · 04-02-2004, 07:02 PM

Quote:

Originally posted by win32sux
i'm not sure, but doesn't samba use tcp port 137 and udp ports 138 and 139, or something like that???

does it work if you flush your iptables (i'm guessing local firewall)???

http://www.linuxguruz.com/iptables/s...h-iptables.txt

posting your samba configuration will make it easier for someone to help you with samba, but you need to make sure the issue isn't your firewall rules...

ok only reason i thought it was 24 was someplace i was reading a FAQ or howto guide and it had for an IP to edit the config. file with was 192.168.1.1:24 as an example.

i can open 137, 138, 139 with no issues.

that is a nice link, but as a newB, were do i enter that data? just on the CLI as root or as a user? do i need to open up some file and edit sorry for the lame questions, but my CLI skills are very limited, but growing day by day with this great site and the help i receive.

thank you for the help. i look forward to figuring this out so i can further enjoy the wounders of Linux and its total power of freedom.

Lleb_KCir · 04-02-2004, 11:02 PM

Quote:

[global]
guest ok = yes
writeable = yes
path = /home/ray/

[global]
log file = /var/log/samba/%m.log
smb passwd file = /etc/samba/smbpasswd
load printers = yes
passwd chat = *New*password* %n\n *Retype*new*password* %n\n *passwd:*all*authentication*tokens*updated*successfully*
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
obey pam restrictions = yes
encrypt passwords = yes
passwd program = /usr/bin/passwd %u
dns proxy = no
netbios name = RHL
server string = samba server
printing = cups
path = /home/ray
unix password sync = Yes
workgroup = ssma
os level = 20
printcap name = /etc/printcap
valid users = ray
max log size = 0
username map = /etc/samba/smbusers
pam password change = yes

[homes]
comment = Home Directories
browseable = yes
writeable = yes
valid users = %S
create mode = 0664
directory mode = 0775

#added next 4 lines 4-1-04 RLB, this is to allow guest accounts.

guest account = nobody
log file = /var/log/samba-log.%m
lock directory = /var/lock/samba
share modes = yes

# If you want users samba doesn't recognize to be mapped to a guest user
; map to guest = bad user

# Un-comment the following and create the netlogon directory for Domain Logons
; [netlogon]
; comment = Network Logon Service
; path = /usr/local/samba/lib/netlogon
; guest ok = yes
; writable = no
; share modes = no

# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
;[Profiles]
; path = /usr/local/samba/profiles
; browseable = no
; guest ok = yes

# NOTE: If you have a BSD-style print system there is no need to
# specifically define each individual printer
[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
# Set public = yes to allow user 'guest account' to print
printable = yes

# This one is useful for people to share files
;[tmp]
; comment = Temporary file space
; path = /tmp
; read only = no
; public = yes

# A publicly accessible directory, but read only, except for people in
# the "staff" group
;[public]
; comment = Public Stuff
; path = /home/samba
; public = yes
; writable = yes
; printable = no
; write list = @staff

# Other examples.
#
# A private printer, usable only by fred. Spool data will be placed in fred's
# home directory. Note that fred must have write access to the spool directory,
# wherever it is.
;[fredsprn]
; comment = Fred's Printer
; valid users = fred
; path = /home/fred
; printer = freds_printer
; public = no
; writable = no
; printable = yes

# A private directory, usable only by fred. Note that fred requires write
# access to the directory.
;[fredsdir]
; comment = Fred's Service
; path = /usr/somewhere/private
; valid users = fred
; public = no
; writable = yes
; printable = no

# a service which has a different directory for each machine that connects
# this allows you to tailor configurations to incoming machines. You could
# also use the %U option to tailor it by user name.
# The %m gets replaced with the machine name that is connecting.
;[pchome]
; comment = PC Directories
; path = /usr/local/pc/%m
; public = no
; writable = yes

# A publicly accessible directory, read/write to all users. Note that all files
# created in the directory by users will be owned by the default user, so
# any user with access can delete any other user's files. Obviously this
# directory must be writable by the default user. Another user could of course
# be specified, in which case all files would be owned by that user instead.
;[public]
; path = /usr/somewhere/else/public
; public = yes
; only guest = yes
; writable = yes
; printable = no

# The following two entries demonstrate how to share a directory so that two
# users can place files there that will be owned by the specific users. In this
# setup, the directory should be writable by both users and should have the
# sticky bit set on it to prevent abuse. Obviously this could be extended to
# as many users as required.
;[myshare]
; comment = Mary's and Fred's stuff
; path = /usr/somewhere/shared
; valid users = mary fred
; public = no
; writable = yes
; printable = no
; create mask = 0765

[home]

ok there is my smb.conf file.

Lleb_KCir · 04-02-2004, 11:08 PM

ok added TCP 137, and UDP 138, 139 and still same error.

Quote:

The network path was not found.

this from the winXP system that can see the RH samba share when i navigate via My Neightwork Places.

what am i doing wrong?

win32sux · 04-03-2004, 11:58 AM

Quote:

Originally posted by Lleb_KCir
ok only reason i thought it was 24 was someplace i was reading a FAQ or howto guide and it had for an IP to edit the config. file with was 192.168.1.1:24 as an example.

i can open 137, 138, 139 with no issues.

what kinda firewall are you using???

Quote:

Originally posted by Lleb_KCir
that is a nice link, but as a newB, were do i enter that data? just on the CLI as root or as a user? do i need to open up some file and edit sorry for the lame questions, but my CLI skills are very limited, but growing day by day with this great site and the help i receive.

the most popular shell for linux is called bash (the bourne again shell)...

when we have a lot of commands that we need to give the shell, we can simply put them all inside a text file (called a shell script) and execute it...

http://www.freeos.com/guides/lsst/ch01sec09.html

http://gd.tuwien.ac.at/linuxcommand....l_scripts.html

http://www.lysator.liu.se/~forsberg/...l-scripts.html

remember to make your shell script executable before running it:

chmod a+x example-script.sh

./example-script.sh

so, basically, to run that iptables script from linuxguruz.com you'd just copy/paste the text into a file, make the file executable, and then execute it (as root)...

you don't need to be root to make the script itself, but you need to be root to run it cuz only root can mess with a system's iptables, for example...

the preffered text-editor for the shell is called "vi"... you could use any text editor, even a graphical one (such as kwrite, on kde), but it's important that you get to know "vi" if you wanna get comfortable with the shell...

http://www.cab.u-szeged.hu/local/lin...g/node159.html

http://www.linuxpowered.com/html/tutorials/vi.html

i'm taking a look at the samba configuration you posted... if i see something i'll let you know, but i don't have any real-world experience with samba... i'm sure somebody else who does will post, though...

meanwhile, here's a couple samba links that might help you:

http://www.troubleshooters.com/linux/samba.htm

http://en.tldp.org/HOWTO/SMB-HOWTO.html

you could easily make yourself a very nice iptables firewall script at this website:

http://easyfwgen.morizot.net/gen/

remember, i'm not 100% sure those are the ports samba uses, and you really need to be 100% sure your firewall is set-up right if you're serious about samba (or any other network service, for that matter)...