localhost.localdomain help

[yutt]

Okay, this should be a fairly simple process I am sure, but I haven't had any luck finding a solution.

I just want to change my computer name and domain name. Right now there are two of us trying to set up Samba sharing and both have the computer name "localhost", and appear to be conflicting with one another.

I am new to Linux as of yesterday, and am running RedHat 9. :D

Thanks,
yutt

[mandrakeroot]

This linuxquestions.org thread might help (http://www.linuxquestions.org/questions/history/62826)

PLEASE SEARCH BEFORE ASKING!!

Goggle Search results for your question (http://www.google.com/search?hl=en&lr=&ie=UTF-8&oe=UTF-8&q=change+%22computer+name%22+red+hat&btnG=Google+Search)

[homey]

Type the command: redhat-config-network to get into a GUI tool which makes it easy to change the hostname. Also, under the Hosts tab you can associate that host name with an IP address like maybe 192.168.0.1 or whatever. I leave the first line alone as your system does need the localhost for some things. My setup looks like this......
127.0.0.1 localhost.localdomain localhost
192.168.0.1 fred.mydomain.com fred

[serz]

Originally posted by mandrakeroot
This linuxquestions.org thread might help (http://www.linuxquestions.org/questions/history/62826)

PLEASE SEARCH BEFORE ASKING!!

Goggle Search results for your question (http://www.google.com/search?hl=en&lr=&ie=UTF-8&oe=UTF-8&q=change+%22computer+name%22+red+hat&btnG=Google+Search)
I'd better suggest him to search in THIS forum.

[yutt]

Thank you very much homey. I ran the utility you said and it was simple. It's so nice to get a direct answer instead of a RTFM reply. :)

I'm still not having much luck with my Samba shares, but at least this takes me a step closer to somewhere.

[mandrakeroot]

Originally posted by serz
I'd better suggest him to search in THIS forum.

LOL-- I got that from the google results

[mandrakeroot]

Originally posted by yutt
Thank you very much homey. I ran the utility you said and it was simple. It's so nice to get a direct answer instead of a RTFM reply. :)

I'm still not having much luck with my Samba shares, but at least this takes me a step closer to somewhere.

The FIRST result in that google query told you exactly what to do step by step. I didnt tell you to RTFM. If you had searched the Red Hat manual you would have found out how to do the same thing.

[yutt]

LOL-- I got that from the google results
Guess what? I had been searching Google for the past 45 minutes or so. As I already stated, I am very new to Linux, so I didn't have much of a clue of what to look for, or if what I found was what I need.

Silly me, I expected to get intelligent and thoughtful replies from a Linux help forum.

[mandrakeroot]

Thats why I provided the google results. As I said, the first result told you all you needed to know. Please dont act like I'm the bad guy. I was just trying to help... ok? A great man once said that you should never reinvent the wheel for a real inventor never does.

[homey]

Glad you got it going. When you get going on samba setup let us know. :)

[mandrakeroot]

For people without redhat: I am posting the first result from my google search because some people havent grasped the hyperlink concept:

FROM: mikec
DATE: 12/31/1997 22:40:50
SUBJECT: RE: Computer Name

On Wed, 31 Dec 1997, Peter wrote:

> In linux how do I change the computer name, ie Localhost.localdomain ?
> Im new to Linux

change it in the file: /etc/sysconfig/network
the file is pretty straightforward.

Also make sure you have your correct IP & hostname in /etc/hosts


Later...
Mike

[yutt]

Thats why I provided the google results. As I said, the first result told you all you needed to know. Please dont act like I'm the bad guy. I was just trying to help... ok?
Alrighty, sorry. I just got the wrong impression. :)

For future reference, giving direct, step-by-step instructions when possible can be much more helpful to a beginner than an arrow pointing in the general direction of the answer.

Glad you got it going. When you get going on samba setup let us know.
Well, since you offered... :D
I am slightly overwhelmed by the many different areas to configure the various parts of Samba. I have the client running perfect through Konqueror. I can browse other computers shares and get files without a problem.

But when I try to share a directory, my computer doesn't even show up. Basically in the end I want a guest share with read priveledges, and no password. I have been working on that most of today...
:(

Any suggestions would very helpful. And if I need to post my smb.conf I can. I've tried reading through the massive documentation for that, through dozen of various forums posts, and through the examples listed in the file itself. But, alas, no luck.

[mandrakeroot]

No problem about the wrong impression thingy.

In konqueror right click on the folder you want to share. I think it has to be IN your home directory. After you right click a menu comes up and you should click on sharing. After that (i think) it is pretty straightforward.(im in gnome right now) Write back to tell me if you have any more questions. Good Luck!!!!! My friend and I worked this out the other day. Thats why I know about the samba stuff. It seems to be much easier than NFS.

Sorry about being so hostile and vague towards you in the beginning. I know that I hated when people did that when I started asking questions.

[homey]

That is definitely in the smb.conf file. Make sure to uncomment the part about hosts allow....
hosts allow = 192.168.0. 192.168.1. 127.

and if you want to use guest accounts ( never on my network! ) .....
guest account = pcguest
security = share

That's a start anyway. It may help to see your file.
Also, there is another GUI tool which may make things more clear for you. It's called
samba-swat

[yutt]

Originally posted by mandrakeroot
In konqueror right click on the folder you want to share. I think it has to be IN your home directory. After you right click a menu comes up and you should click on sharing. After that (i think) it is pretty straightforward.(im in gnome right now)
Okay. I have a directory in my "Home" called "test". I right click on it, and there is not a sharing option on the menu. If I go to "Properties" on the bottom of the menu, there is a tab that says "Local Network Sharing". If I go to that I get an error, "Error running 'filesharelist'. Check if installed or in $PATH or usr/sbin." I believe this tab is related to NFS though, yes?

Anyhow. I don't know what $PATH means, and I don't know what it wants installed in usr/sbin.

I am using KDE, not Gnome, could that be the difference? I'd rather not use Gnome if I have the choice, as it's interface seems very unintuitive to me.

[mandrakeroot]

Originally posted by homey
That is definitely in the smb.conf file. Make sure to uncomment the part about hosts allow....
hosts allow = 192.168.0. 192.168.1. 127.

and if you want to use guest accounts ( never on my network! ) .....
guest account = pcguest
security = share

That's a start anyway. It may help to see your file.
Also, there is another GUI tool which may make things more clear for you. It's called
samba-swat

THat is interesting. I never touched my smb.conf file and everything worked perfeclty. KDE set it all up!
MY SAMBA FILE:

# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options (perhaps too
# many!) most of which are not shown in this example
#
# Any line which starts with a ; (semi-colon) or a # (hash)
# is a comment and is ignored. In this example we will use a #
# for commentry and a ; for parts of the config file that you
# may wish to enable
#
# NOTE: Whenever you modify this file you should run the command "testparm"
# to check that you have not made any basic syntactic errors.
#
#======================= Global Settings =====================================
[global]

# 1. Server Naming Options:
# workgroup = NT-Domain-Name or Workgroup-Name
workgroup = MDKGROUP

# netbios name is the name you will see in "Network Neighbourhood",
# but defaults to your hostname
; netbios name = <name_of_this_server>

# server string is the equivalent of the NT Description field
server string = Samba Server %v

# Message command is run by samba when a "popup" message is sent to it.
# The example below is for use with LinPopUp:
; message command = /usr/bin/linpopup "%f" "%m" %s; rm %s

# 2. Printing Options:
# CHANGES TO ENABLE PRINTING ON ALL CUPS PRINTERS IN THE NETWORK
# (as cups is now used in linux-mandrake 7.2 by default)
# if you want to automatically load your printer list rather
# than setting them up individually then you'll need this
printcap name = cups
load printers = yes

# It should not be necessary to spell out the print system type unless
# yours is non-standard. Currently supported print systems include:
# bsd, sysv, plp, lprng, aix, hpux, qnx, cups
printing = cups

# Samba 2.2 supports the Windows NT-style point-and-print feature. To
# use this, you need to be able to upload print drivers to the samba
# server. The printer admins (or root) may install drivers onto samba.
# Note that this feature uses the print$ share, so you will need to
# enable it below.
# This parameter works like domain admin group:
# printer admin = @<group> <user>
printer admin = @adm
# This should work well for winbind:
; printer admin = @"Domain Admins"

# 3. Logging Options:
# this tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/log.%m

# Put a capping on the size of the log files (in Kb).
max log size = 50

# Set the log (verbosity) level (0 <= log level <= 10)
; log level = 3

# 4. Security and Domain Membership Options:
# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page. Do not enable this if (tcp/ip) name resolution does
# not work for all the hosts in your network.
; hosts allow = 192.168.1. 192.168.2. 127.

# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
; guest account = pcguest
# Allow users to map to guest:
map to guest = bad user

[mandrakeroot]

# Security mode. Most people will want user level security. See
# security_level.txt for details.
security = user
# Use password server option only with security = server or security = domain
# When using security = domain, you should use password server = *
; password server = <NT-Server-Name>
; password server = *

# Password Level allows matching of _n_ characters of the password for
# all combinations of upper and lower case.
; password level = 8
; username level = 8

# You may wish to use password encryption. Please read
# ENCRYPTION.txt, Win95.txt and WinNT.txt in the Samba documentation.
# Do not enable this option unless you have read those documents
# Encrypted passwords are required for any use of samba in a Windows NT domain
# The smbpasswd file is only required by a server doing authentication, thus
# members of a domain do not need one.
encrypt passwords = yes
smb passwd file = /etc/samba/smbpasswd

[mandrakeroot]

# The following are needed to allow password changing from Windows to
# also update the Linux system password.
# NOTE: Use these with 'encrypt passwords' and 'smb passwd file' above.
# NOTE2: You do NOT need these to allow workstations to change only
# the encrypted SMB passwords. They allow the Unix password
# to be kept in sync with the SMB password.
; unix password sync = Yes
# You either need to setup a passwd program and passwd chat, or
# enable pam password change
; pam password change = yes
; passwd program = /usr/bin/passwd %u
; passwd chat = *New*UNIX*password* %n\n *ReType*new*UNIX*password* %n\n
;*passwd:*all*authentication*tokens*updated*succes sfully*

# Unix users can map to different SMB User names
; username map = /etc/samba/smbusers

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
; include = /etc/samba/smb.conf.%m

# Options for using winbind. Winbind allows you to do all account and
# authentication from a Windows or samba domain controller, creating
# accounts on the fly, and maintaining a mapping of Windows RIDs to unix uid's
# and gid's. winbind uid and winbind gid are the only required parameters.
#
# winbind uid is the range of uid's winbind can use when mapping RIDs to uid's
; winbind uid = 10000-20000
#
# winbind gid is the range of uid's winbind can use when mapping RIDs to gid's
; winbind gid = 10000-20000
#
# winbind separator is the character a user must use between their domain
# name and username, defaults to "\"
; winbind separator = +
#
# winbind use default domain allows you to have winbind return usernames
# in the form user instead of DOMAIN+user for the domain listed in the
# workgroup parameter.
; winbind use default domain = yes
#
# template homedir determines the home directory for winbind users, with
# %D expanding to their domain name and %U expanding to their username:
; template homedir = /home/%D/%U

# When using winbind, you may want to have samba create home directories
# on the fly for authenticated users. Ensure that /etc/pam.d/samba is
# using 'service=system-auth-winbind' in pam_stack modules, and then
# enable obedience of pam restrictions below:
; obey pam restrictions = yes

#
# template shell determines the shell users authenticated by winbind get
; template shell = /bin/bash

# 5. Browser Control and Networking Options:
# Most people will find that this option gives better performance.
# See speed.txt and the manual pages for details
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192

# Configure Samba to use multiple interfaces
# If you have multiple network interfaces then you must list them
# here. See the man page for details.
; interfaces = 192.168.12.2/24 192.168.13.2/24

# Configure remote browse list synchronisation here
# request announcement to, or browse list sync from:
# a specific host or from / to a whole subnet (see below)
; remote browse sync = 192.168.3.25 192.168.5.255
# Cause this host to announce itself to local subnets here
; remote announce = 192.168.1.255 192.168.2.44

# set local master to no if you don't want Samba to become a master
# browser on your network. Otherwise the normal election rules apply
; local master = no

# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
; os level = 33

# Domain Master specifies Samba to be the Domain Master Browser. This
# allows Samba to collate browse lists between subnets. Don't use this
# if you already have a Windows NT domain controller doing this job
; domain master = yes

# Preferred Master causes Samba to force a local browser election on startup
# and gives it a slightly higher chance of winning the election
; preferred master = yes

[mandrakeroot]

# 6. Domain Control Options:
# Enable this if you want Samba to be a domain logon server for
# Windows95 workstations or Primary Domain Controller for WinNT and Win2k
; domain logons = yes

# if you enable domain logons then you may want a per-machine or
# per user logon script
# run a specific logon batch file per workstation (machine)
; logon script = %m.bat
# run a specific logon batch file per username
; logon script = %U.bat

# Where to store roaming profiles for WinNT and Win2k
# %L substitutes for this servers netbios name, %U is username
# You must uncomment the [Profiles] share below
; logon path = \\%L\Profiles\%U

# Where to store roaming profiles for Win9x. Be careful with this as it also
# impacts where Win2k finds it's /HOME share
; logon home = \\%L\%U\.profile

# The add user script is used by a domain member to add local user accounts
# that have been authenticated by the domain controller, or by the domain
# controller to add local machine accounts when adding machines to the domain.
# The script must work from the command line when replacing the macros,
# or the operation will fail. Check that groups exist if forcing a group.
# Script for domain controller for adding machines:
; add user script = /usr/sbin/useradd -d /dev/null -g machines -c 'Machine Account' -s /bin/false -M %u
# Script for domain controller with LDAP backend for adding machines (please
# configure in /etc/samba/smbldap_conf.pm first):
; add user script = /usr/share/samba/scripts/smbldap-useradd.pl -w -d /dev/null -g machines -c 'Machine Account' -s /bin/false %u
# Script for domain member for adding local accounts for authenticated users:
; add user script = /usr/sbin/useradd -s /bin/false %u

# Domain groups:
# domain admin group is a list of unix users or groups who are made members
# of the Domain Admin group
; domain admin group = root @adm
#
# domain guest groups is a list of unix users or groups who are made members
# of the Domain Guests group
; domain guest group = nobody @guest

# LDAP configuration for Domain Controlling:
# The account (dn) that samba uses to access the LDAP server
# This account needs to have write access to the LDAP tree
# You will need to give samba the password for this dn, by
# running 'smbpasswd -w mypassword'
; ldap admin dn = cn=root,dc=mydomain,dc=com
; ldap ssl = start_tls
# start_tls should run on 389, but samba defaults incorrectly to 636
; ldap port = 389
; ldap suffix = dc=mydomain,dc=com
; ldap server = ldap.mydomain.com


# 7. Name Resolution Options:
# All NetBIOS names must be resolved to IP Addresses
# 'Name Resolve Order' allows the named resolution mechanism to be specified
# the default order is "host lmhosts wins bcast". "host" means use the unix
# system gethostbyname() function call that will use either /etc/hosts OR
# DNS or NIS depending on the settings of /etc/host.config, /etc/nsswitch.conf
# and the /etc/resolv.conf file. "host" therefore is system configuration
# dependant. This parameter is most often of use to prevent DNS lookups
# in order to resolve NetBIOS names to IP Addresses. Use with care!
# The example below excludes use of name resolution for machines that are NOT
# on the local network segment
# - OR - are not deliberately to be known via lmhosts or via WINS.
; name resolve order = wins lmhosts bcast

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
; wins support = yes

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z

# WINS Proxy - Tells Samba to answer name resolution queries on
# behalf of a non WINS capable client, for this to work there must be
# at least one WINS Server on the network. The default is NO.
; wins proxy = yes

# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The built-in default for versions 1.9.17 is yes,
# this has been changed in version 1.9.18 to no.
dns proxy = no

# 8. File Naming Options:
# Case Preservation can be handy - system default is _no_
# NOTE: These can be set on a per share basis
; preserve case = no
; short preserve case = no
# Default case is normally upper case for all DOS files
; default case = lower
# Be very careful with case sensitivity - it can break things!
; case sensitive = no

# Enabling internationalization:
# you can match a Windows code page with a UNIX character set.
# Windows: 437 (US), 737 (GREEK), 850 (Latin1 - Western European),
# 852 (Eastern Eu.), 861 (Icelandic), 932 (Cyrillic - Russian),
# 936 (Japanese - Shift-JIS), 936 (Simpl. Chinese), 949 (Korean Hangul),
# 950 (Trad. Chin.).
# UNIX: ISO8859-1 (Western European), ISO8859-2 (Eastern Eu.),
# ISO8859-5 (Russian Cyrillic), KOI8-R (Alt-Russ. Cyril.)
# This is an example for french users:
; client code page = 850
; character set = ISO8859-1


#============================ Share Definitions ==============================
[homes]
comment = Home Directories
browseable = no
writable = yes
# You can enable VFS recycle bin on a per share basis:
# Uncomment the next 2 lines (make sure you create a
# .recycle folder in the base of the share and ensure
# all users will have write access to it. See
# examples/VFS/recycle/REAME in samba-doc for details
; vfs object = /usr/lib/samba/vfs/recycle.so
; vfs options= /etc/samba/recycle.conf
# You may want to prevent abuse of your server disk space, and spread of virii
; veto files = /*.eml/*.nws/*.dll/*.mp3/*.MP3/*.mpg/*.MPG/*.vbs/*.VBS/

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

#Uncomment the following 2 lines if you would like your login scripts to
#be created dynamically by ntlogon (check that you have it in the correct
#location (the default of the ntlogon rpm available in contribs)
;root preexec = /usr/bin/ntlogon -u %U -g %G -o %a -d /var/lib/samba/netlogon/
;root postexec = rm -f /var/lib/samba/netlogon/%U.bat

# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
;[Profiles]
; path = /var/lib/samba/profiles
; browseable = no
; guest ok = yes
; writable = yes
# This script can be enabled to create profile directories on the fly
# You may want to turn off guest acces if you enable this, as it
# hasn't been thoroughly tested.
; root preexec = PROFILE=/var/lib/samba/profiles/%u; if [ ! -e $PROFILE ]; \
; then mkdir -pm700 $PROFILE; chown %u.%g $PROFILE;fi


# NOTE: If you have a CUPS print system there is no need to
# specifically define each individual printer.
# You must configure the samba printers with the appropriate Windows
# drivers on your Windows clients. On the Samba server no filtering is
# done. If you wish that the server provides the driver and the clients
# send PostScript ("Generic PostScript Printer" under Windows), you have
# to swap the 'print command' line below with the commented one.
[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
# to allow user 'guest account' to print.
guest ok = yes
writable = no
printable = yes
create mode = 0700
# =====================================
# print command: see above for details.
# =====================================
print command = lpr-cups -P %p -o raw %s -r # using client side printer drivers.
; print command = lpr-cups -P %p %s -r # using cups own drivers (use generic PostScript on clients).
# The following two commands are the samba defaults for printing=cups
# change them only if you need different options:
; lpq command = lpq -P %p
; lprm command = cancel %p-%j

# This share is used for Windows NT-style point-and-print support.
# To be able to install drivers, you need to be either root, or listed
# in the printer admin parameter above. Note that you also need write access
# to the directory and share definition to be able to upload the drivers.
# For more information on this, please see the Printing Support Section of
# /usr/share/doc/samba-<version>/docs/Samba-HOWTO-Collection.pdf
[print$]
path = /var/lib/samba/printers
browseable = yes
read only = yes
write list = @adm root
guest ok = yes

# A useful application of samba is to make a PDF-generation service
# To streamline this, install windows postscript drivers (preferably colour)
# on the samba server, so that clients can automatically install them.

[pdf-generator]
path = /var/tmp
guest ok = No
printable = Yes
comment = PDF Generator (only valid users)
#print command = /usr/share/samba/scripts/print-pdf file path win_path recipient IP doc_name &
print command = /usr/share/samba/scripts/print-pdf %s ~%u //%L/%u %m %I "%J" &

# 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
; public = yes
; writable = no
; write list = @staff
# Audited directory through experimental VFS audit.so module:
# Uncomment next line.
; vfs object = /usr/lib/samba/vfs/audit.so

[mandrakeroot]

# 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 = /homes/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/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

[ALEX_VIDEO]
path = /home/alex/video
comment = /home/alex/video
public = yes
guest ok = yes
writable = no

[ALEX_MP3S]
path = /home/alex/mp3s
comment = /home/alex/mp3s
public = yes
guest ok = yes
writable = no
wide links = no

[yutt]

Oy... this gets frustrating after a while. Probably something that should be obvious I am missing...

Well, here is my smb.conf (http://www.yutt.net/files/smb.conf).

I looked over yours mandrake, even tried to use it (modified of course) but I am not having any better luck.

Just wondering, will the service network restart suffice to update what is in use after I modify my smb.conf? Or do I need to logout, or restart, or what?

[homey]

There are a couple of problems in your smb.conf but first... to restart samba use the command: service smb restart
Now onto the config.....
I would use a simple netbios name for your network like...
workgroup = workgroup

try this in lower case....
security = share

local master = no
os level = 33

comment this out since you DO want to allow guest
# map to guest = bad user

And you have not actually shared anything except the homes directory which is available to logged on users.
Try uncommenting this one....
# This one is useful for people to share files
[tmp]
comment = Temporary file space
path = /tmp
read only = yes
public = yes

After you make the changes restart samba with the command: service smb restart

You can check for errors with the command: testparm

Check the shares on the Linux computer with the command:
smbclient –L <linux hostname> -N
Note: linux hostname is the name of your linux computer.

[yutt]

homey, wow, thanks that was an amazingly informative post. Now I think I actually have some idea of the tools and procedures for troubleshooting this junk.

Well, the computer is now visible from a WinXP box, but it can't be browsed. One thing that looked worth noting was this.

[root@l1nux root]# smbclient -L L1nux -N
added interface ip=158.80.64.62 bcast=158.80.64.255 nmask=255.255.255.0
Domain=[WORKGROUP] OS=[Unix] Server=[Samba 2.2.7a-security-rollup-fix]
tree connect failed: NT_STATUS_WRONG_PASSWORD
The bold is what looked like a problem, but I do not know what exactly that problem is.

I looked into it, and it looked like it had something to do with not having a user. So I tried using smbpasswd to create the user pcguest... but that didn't work.

[yutt]

Okay. I've made it beyond that error. Had to "useradd pcguest" , then, "smbpasswd -a pcguest".

But I still cannot browse my computer from a Windows PC.

Linux is frustrating. :mad:

[mandrakeroot]

yutt: you should post your smb.conf now. That would be helpful. I dont understand why you are making users for acces to the files.

Homey: Thanks for your posts. You obviously know a lot about this and I am learning much from your posts.
yutt-- this might not be helpful but this is how my foldres are shared. I dont have any problems with users.
[ALEX_VIDEO]
path = /home/alex/video
comment = /home/alex/video
public = yes
guest ok = yes
writable = no

[ALEX_MP3S]
path = /home/alex/mp3s
comment = /home/alex/mp3s
public = yes
guest ok = yes
writable = no
wide links = no

[mandrakeroot]

Originally posted by yutt
Oy... this gets frustrating after a while. Probably something that should be obvious I am missing...

Well, here is my smb.conf (http://www.yutt.net/files/smb.conf).

I looked over yours mandrake, even tried to use it (modified of course) but I am not having any better luck.

Just wondering, will the service network restart suffice to update what is in use after I modify my smb.conf? Or do I need to logout, or restart, or what?

Im pretty sure that it updates automatically... I dont know if you need to do anything but wait a few seconds for it to update. I might be wrong of course.

[homey]

added interface ip=158.80.64.62

Check the Windows computer to see if it's IP address is similar to this one. Something like 158.80.64.?? If it is, then you need to add that IP range to the smb.conf ........
hosts allow = 158.80.64. 192.168.0. 192.168.1. 127.


Don't forget to restart samba after making changes.

Linux can be challenging but that's half the fun :)

[mandrakeroot]

Originally posted by homey
Check the Windows computer to see if it's IP address is similar to this one. Something like 158.80.64.?? If it is, then you need to add that IP range to the smb.conf ........
hosts allow = 158.80.64. 192.168.0. 192.168.1. 127.


Don't forget to restart samba after making changes.

Linux can be challenging but that's half the fun :)

How do you make it so *all* hosts are allowed?

[homey]

How do you make it so *all* hosts are allowed?
You comment out the hosts allow section.....
# hosts allow = 192.168.0. 192.168.1. 127.

Not a very secure way of doing things though :)

[mandrakeroot]

Originally posted by homey
You comment out the hosts allow section.....
# hosts allow = 192.168.0. 192.168.1. 127.

Not a very secure way of doing things though :)

Yeah definately not. I guess I would only do that for a computer without internet access but those are hard to find now a days. Thanks for the info.

[yutt]

Originally posted by homey
Check the Windows computer to see if it's IP address is similar to this one. Something like 158.80.64.?? If it is, then you need to add that IP range to the smb.conf ........
hosts allow = 158.80.64. 192.168.0. 192.168.1. 127.
/me smacks self

That was so ridiculously obvious... Oy. It works, perfectly. *sigh*

Thank you very much homey you are very knowledgeable and helpful. I really appreciate it. :)
Linux can be challenging but that's half the fun :)
True, but once I've reached the point where my troubleshooting skills are reduced to chanting, "Please just work, please just work.... Expletive!!," it's not nearly as fun. :D