Made the switch -need a little help

[wader]

Just recently started dual booting XP and Red Hat 7.3
I have 3 machines running on a home lan all using XP
They are connected using Linksys 4 port router.
I am able to browse files on the XP machines using the Red HAt box , however I am not able to see files on the linux box using the XP Machines.
Samba is running and I am able to see the linux box.
I cannot get past the password error and see your network administor error.( not that it's an error)
I have tried editing the smb.conf file but I am not too smart.
Does this key mean comment " ; " (without the quotes)
I have read quite a bit about the smb.conf file and it ???seems that it can be simplified. I only need file and printer sharing.

btw has anyone on this forum run Medal of Honor on a linux box?

Thnx

[babbing]

i think you may need to set a password for the XP users. try smbpasswd. man that up let us know if that helps :P. On a second note, nice post, clear concise and included all pertenant information.


I haven't heard too much about it about here, but who knows, check out the games forum, and see :P


Goodluck,


Babbing

[wader]

Sorry I don't understand what you mean!
I found a file called smbpasswd in /usr/bin
An exe that I don't know how to use.
I find this all very frustrating tho a challenge. I've logged hours and hours already trying to overcome this one thing.
I am confused with the whole lan setup.
Seems easier in windows(xp or 98)

Right now I am unable to use KDE interface to log onto windows machine. Says unable to find local host.
With Nautilus I run SMB: at the location bar and it gives me the workgroup on the windoze machine.

Understand I have zero linux knowledge,
tho I know more today than I did yesterday

thnx again

An update:
By typing in the computer name in Konquerer file/web browser at the "open location" menu
I am able to get onto the select XP machine.
I would of course prefer a "network neighbourhood browsing style.

So now I have only to get XP to let me see files on the linux box.


So bear in mind I have zero knowledge setting up config files in Linux

Update2:
Getting closer, I can add a network place in xp.It seems to wanna take when I type in the server name but gives this message: "windows requires a share to publish in. please try another location"

Do you know where I should go from here?

BTW smbpasswd doesn't exist in etc/samba/

[Spot]

Sorry I don't understand what you mean!
I found a file called smbpasswd in /usr/bin
An exe that I don't know how to use.

No such thing as an "exe" for linux - that's a winders thing

I find this all very frustrating tho a challenge. I've logged hours and hours already trying to overcome this one thing.
I am confused with the whole lan setup.
Seems easier in windows(xp or 98)

Are you sure about that statement? I'm sure it might seem that way, but were you honestly able to do all that as a "winders newbie"?

Right now I am unable to use KDE interface to log onto windows machine. Says unable to find local host.
With Nautilus I run SMB: at the location bar and it gives me the workgroup on the windoze machine.

Understand I have zero linux knowledge,
tho I know more today than I did yesterday

thnx again

An update:
By typing in the computer name in Konquerer file/web browser at the "open location" menu
I am able to get onto the select XP machine.
I would of course prefer a "network neighbourhood browsing style.

There are few similar things(linneighborhood, lisa, et al), but like 'network neighborhood' itself, they're kinda lame.

So now I have only to get XP to let me see files on the linux box.


So bear in mind I have zero knowledge setting up config files in Linux

Update2:
Getting closer, I can add a network place in xp.It seems to wanna take when I type in the server name but gives this message: "windows requires a share to publish in. please try another location"

Do you know where I should go from here?

Seeing your samba config file might be of some help.
The file is located at: /etc/samba/smb.conf and can be read with any text editor(though it can only be edited by root). If you could copy/paste the contents here, we might have more of a clue as to what's going on.

[wader]

Here it is: Good luck.
# 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]

# workgroup = NT-Domain-Name or Workgroup-Name
workgroup = games

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

# 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
hosts allow = 192.168.1.1 192.168.2. 127.

# if you want to automatically load your printer list rather
# than setting them up individually then you'll need this
printcap name = /etc/printcap
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
; printing = bsd

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

# 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

# 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
; password server = <NT-Server-Name>

# 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
; encrypt passwords = yes
; smb passwd file = /etc/samba/smbpasswd

# The following are needed to allow password changing from Windows to
# update the Linux sytsem password also.
# 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
; passwd program = /usr/bin/passwd %u
; passwd chat = *New*UNIX*password* %n\n *ReType*new*UNIX*password* %n\n *passwd:*all*authentication*tokens*updated*success fully*

# 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

# 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

# Browser Control Options:
# 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

# Use only if you have an NT server on your network that has been
# configured at install time to be a primary domain controller.
; domain controller = <NT-Domain-Controller-SMBName>

# Enable this if you want Samba to be a domain logon server for
# Windows95 workstations.
; 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 roving profiles (only for Win95 and WinNT)
# %L substitutes for this servers netbios name, %U is username
# You must uncomment the [Profiles] share below
; logon path = \\%L\Profiles\%U

# 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

[wader]

This is the second part as it was too long.


# 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 oneWINS 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

# 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

#============================ Share Definitions ==============================
[homes]
comment = Home Directories
browseable = yes
writable = yes

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


# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
[Profiles]
path = /home/profiles
browseable = yes
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
guest ok = yes
writable = no
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
read only = yes
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 = /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

[friskydrifter]

Make sure your workgroup on the windows is games
[quote; smb passwd file = /etc/samba/smbpasswd]

get rid of the ; in that line

make sure you have a user on the windows machine e.g User1with a password of password

then on the linux box type

smbpasswd -a User

then enter the password for that user (e.g password)
enter again to confirm (e.g password)

see how that helps.

Also the ; means that that line will not be read.

hosts allow = 192.168.1.1 192.168.2. 127.

you can also comment out that line (with a ; at the start) - that is just for restricting samba to particular ip addresses.

Havent tried Medal of Honour


good luck Frisky

[friskydrifter]

Ah yes i forgot to mention do a :

locate BROWSING.txt and read that file :P

[wader]

Frisky,

Thnx for your help thus far.
Editing the smb.conf file did not get results.
I stil dont see a etc/samba/smbpasswd file!
Should I?
I read the BROWSING.txt that was confusing.
Do I need to change WINS in XP?
What is nmbd?

Also I am not sure that I did the add user password thing right! Was I supposed to be prompted for a password and then the confirm?
It gave me options and uses for the command.

bear with me Frisky.

Just so you know:
I would like at this point to set up without passwords and anything else.
The XP machines have no users.
They are all administrator access.

Getting the lan browsing to work would be great. I can always add to the smb.conf file later. I do not care about security at this point as I am dual booting and have nothing to hide or worry about.Router provides hardware firewall and I can add software fiewall later.
Isn't a simple smb.conf possible.
What about that LISA thing?
should it be showing the network when you run it? Cause it don't!!

[friskydrifter]

Hahaha u sound hell confused. Where to start. OK im no expert and its been a lil while since i looked at samba but ill try to answer a few things here.

I read the BROWSING.txt that was confusing.

Indeed lol.

Do I need to change WINS in XP?

No, I dont think so.

Also I am not sure that I did the add user password thing right! Was I supposed to be prompted for a password and then the confirm?
It gave me options and uses for the command.

try it again - i think the first time i tried it it didnt workbecause the passwd file hadnt been created, and also i think when you do this right it adds a /etc/samba/smbpassword file - ill have to check up on this later.

I would like at this point to set up without passwords and anything else.
The XP machines have no users.
They are all administrator access.

you need a password to access the files on the linux box as far as i know - try adding a user called Administrator with the smbpasswd but leaving the password blank if you have no password on the XP box. Ill try to give an example.

smbpasswd -a Administrator (Enter)
(Enter)
(Enter)
should say some mesage that the password has been added.

Well keep me informed ill try to help out and i might go check a few things out for u next time.

Also i had some probs with samba and two subnets that we covered earlier , maybe have a read here and see if anything helps.
http://www.getlinuxonline.com/yabbse...y;threadid=849

Plus i've never used lisa.
Also just a thourght - how about trying samba between just two machines to become a little more familiar with it instead of through a router. I dont think it should be any different(i could be wrong) but you could eliminate any network troubles.

Well hope ure gettin there - Frisky