LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Software (http://www.linuxquestions.org/questions/linux-software-2/)
-   -   Same old Problem, Win98 cannot access Samba share! (http://www.linuxquestions.org/questions/linux-software-2/same-old-problem-win98-cannot-access-samba-share-35121/)

mutantjazz 11-11-2002 01:46 AM

Same old Problem, Win98 cannot access Samba share!
 
I have been scouring this forum for days now.... maby not long enough I know but I have picked up many things and tried them all..... WinXp will connect to the Share but win98 gives the well known....
"\\XXXXX\server
Enter password___________
....Password not valid....
I have seen this problem crop up in many threads and was wondering if it has been solved?

It would be wonderful if Win98 actually let you define a Username and then password like W2k and XP before entering a share for the first time.... is there a way to do that in 98? I have the 98 box set up to Microsoft network logon share level access, samba is set up with the correct user names both in Linux logon and samba, with defined passwords , encrypted passwords = yes and I have the passwd file.... I have taken parts and pieces of many posts and tried to create a working smb.conf file.... but it only succeeds in gettign the winXP machine to gain access...

As it stands now I have a public folder shared guest only = yes just so I can use the Linux box to back up files... but I would liek to figure this out so I can up the security of access, just for practise...

Any and all help will be apreciated....
smb.conf is as follows
[global]
workgroup = Kraal
;netbios name = LINUXSERVER
server string = Server
public = yes
hosts allow = 192.168.1.100 192.168.1.101 127.
printcap name = etc/printcap
load printers = yes
printing = lprng
log file = /var/log/samba/%m.log
max log size = 0
security = user
encrypt passwords = yes
smb passwd file = /etc/samba/smbpasswd
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
dns proxy = n
[Server]
path = /BeastHalo1Dweeb
public = yes
only guest = yes
writable = yes
printable = no
[Shares]
public = yes
browseable = yes
Comment = Files
path = /server
;preexec close = no
;root preexec close = no
read only = no
writeable = yes
valid users = Halo1 Dweeb
[printers]
comment = All Printers
path = /var/spool/samba
browseable = yes
guest ok = no
writable = no
printable = yes

born4linux 11-11-2002 02:36 AM

try setting this:

encryp passwords = no

in your smb.conf file. restart smb and then retry accessing the samba share from Win98. If it goes through, well, you can just disable password encryption in XP (running regedit i suppose?). I believe Win98SE has password encryption support, r u using the older win98?

J_Szucs 11-11-2002 06:52 AM

Have you allowed wins support in smb.conf (and also on the win98 machine)?
I had no troubles with some 30 win98 machines, but there was one where only wins helped when I had a similar problem.

mutantjazz 11-11-2002 11:15 PM

Ok .. using win98se

I enabled wins support ... now both Machines cannot access either file share folders?!?! Took it out again and restarted SMB services... and still neither my win98 nor the Winxp machine can access anything on the Linux box..... Kinda annoying since I had at least some functionality yesterday? Oh well live and learn....

I need abit of help with WINS I believe... SO I enable it in SMB plus on the win98 box, in the 98 box do I use "use DCHP for wins", or define a wins server, then go back to the linux box and set up a wins server?

Off topic kinda...I believe my Linksys ROuter/4-port switch is screwing things up a bit.... I have no cable modem , bought the router/switch trying to think ahead... without a modem though I can't configure the damn thing..... Starting to suspect it maybe the an aditional cause for some problems I have been having.....
*Edited*
-- what is the 127.1.1.1 address mapped to localhost, and when I don't add 127. to hosts allow... my Linux box doesn't even show up on the network?? I have set all my win machines to static private ip's.... to keep easier track of them, plus set BEast ((Supposebly my linux box)) to static also, is locahost my linux box too? or is it a loopback from the router?

iamnotherbert 11-11-2002 11:23 PM

I seem to remember a problem simlar to this awhile back. Did you investigate the way a password is submitted to smb from 98. I think it is acctually workgroup/password instead of just password. Try adding the 98 users password to smbpasswd like that.

-d

mutantjazz 11-12-2002 12:13 AM

Never though of that... or even read about it... sux That I can't even get back to that point yet... ie entering passwd etc.... I am still stuck on that damn localhost bulls**t .... it is confusing to me... my PC is defined as a host with a static ip... yet his other "localhost" keep spopping up... how do I get rid of it... or override it.... I see localhost defined in hosts file, lmhosts etc but don't know what to make of it or change it to... plus why the hell it it set to 127. Loopback????? huh complete newbie just swimming in confusion.... THnx for the replies... the more the less painful my journey will be?!?!?
:-)

iamnotherbert 11-12-2002 12:43 AM

Are you trying to set the host name for the samba server? That is in smb.conf. You only need wins to resolve a name like sambaserver to an address like 192.168.1.2. Try connecting to the samba server with the ip address in net neighboorhood.. \\192.168.1.2\share.. Also make sure the firewall on xp is off. It screws up alot of smb stuff. hope it helps..

mutantjazz 11-12-2002 01:10 AM

ok... I will try all that now....
As for all that host name stuff.. no ... My smb.conf is listed at the top... it is setup correctly I believ... I am talking about my lmhosts and host files.... always listing localhost.... This is not an issue I am willing to deal with tonight though I have deleted it.....thnx for the input, really I do appreciate all I can get...

Xp firewall is off, all PC's in Network are set to static ip's, with same subnet address and domain. Both WinXP and WIn98 can see the Linux Machine, which samba is setup to share one folder indiscriminately, and another one specifically for the win machines..... It is almost the exact same setup as yesterday when my WInxp machien had access and as a few days ago when both machines had access.

I see my linux box, The error I get from the win machines is, "Network path not found"..... Am I sharing something on a different network, or are my win machines maby trying an ip that is not there, I can ping the linux box((only by IP though)) and all the others, too and from all.... so my static ips correspond to what i inputted.

I am not going to quit... after seeing how much quicker a transfer rate I got compared to a win2k server on the same box I am all for getting this samba stuff down... ;-)

**Disabled Linux Firewall, WinXP can access as desired!, Win98, no luck even after trying all of the above**
Thnx for the help... going to bed... Will check any posts later.

jeyarajnjd 11-12-2002 08:06 AM

The network Path was not Found
 
Hi,

I have installed Rehhat Linux and have configured Apache, MySQL and PHP and a site is running on the server. I am use FTP to that Linux Server and can access files. I can ping the server.

But I can not share the folders in Linux server to the windows network thru Samba server. Whenever I am typing the linux server name or the ip address from the explorer I am getting the error message as "The network path not found".

I don't know where is the problem. For ur reference I am adding the samba configuration setup too with this mail . Pls do some help for me.

Jeyaraj

SAMBA CONF File is

# 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 many any basic syntactic errors.
#
#======================= Global Settings =====================================
[global]

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

# server string is the equivalent of the NT Description field
server string = LINUXSERVER

# 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. 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/%m.log

# 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 or
# security = domain
; 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*successfully*

# 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
remote announce = 192.168.1.255

# 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>
domain controller = Domainserver

# 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

# 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
unix password sync = yes
comment = Shipstaff Linux Server
netbios name = LinServ
; security = user
password level = 0
null passwords = no
os level = 0
preferred master = no
domain master = no
wins support = no
dead time = 0
debug level = 0

# 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 = no
; 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 = no


# 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 = 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
guest ok = no
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
; 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 = /homes/fred
; printer = freds_printer
; public = 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

[public]
path = /home/httpd/html/shipstaff
public = yes
guest ok = yes
writable = yes
printable = no

[phplib]
path = /home/phplib-7.2c/php
public = yes
guest ok = yes
writable = yes
printable = no

[phpmanual]
path = /home/phplib-7.2c/doc
public = yes
guest ok = yes
writable = yes
printable = no

mutantjazz 11-12-2002 11:41 PM

Ok ... have some success to report....
Enabled wins and changed password to reflect what IAMNOTHERBERT said above.... it turns out my set password is too long for windows ... so I made it shorter and hey presto, still having trouble with the restricted access share.. but at least I can see it now... so progress is being made... thnx for the help... I will add any other issues as I encounter them... wish me luck

JimKyle 11-13-2002 12:08 AM

Just came across this thread and noticed that nobody has explained "localhost" for you... That's a convention that many programs follow; it's called the "loopback" interface. Your Linux box should have an interface of "lo" with the IP address 127.0.0.1, and the localhost definition for that address should be in the "hosts" file on all three machines. Some programs won't run if they cannot find localhost, and you should always be able to ping localhost with zero delay because the TCP/IP stack loops this address right back to the socket that requested it.

If you got "swat" installed as part of your Samba installation, you can use it to tweak your smb.conf file. From any browser on the Linux box, open the URL http://127.0.0.1:901 and you should see the swat login dialog. User name should be root and password your root password. Then you can simply fill out the forms the program displays...

From the Win98 machine, open a DOS box and try the nbtstat, netstat, and "net view" commands to see what's happening with Samba. The commands may also work under XP but I stopped upgrading M$ stuff with Win98SE...

mutantjazz 11-13-2002 10:55 AM

thnx for the explaination...makes sense now... also why if I don't define a host other than that on my linux box, the winboxes think there are two 'localhosts' and won't connect.... b/c there are technically three!

Well my win98 box still putting up a fight... only my 'guest only' account has access, I am going to scan my log files and see just what erors it has been generating when I try to connect.... maby it is a simple as file permissions? or maby not?

JimKyle 11-13-2002 11:51 AM

To get my Win98 boxes able to share with Samba, I had to establish passworded login on each of them. I had been using blank passwords. I'm now using Windows Login and with TweakUI set each box up to remember the user, and logged in with the same user name I use on Linux and the same password. That may be the only thing you need to do for Win98.

The "only guest" account can work because that tells Samba not to check passwords there.

Be very cautious of setting "guest ok=yes" anywhere, though; I did that the first time I installed Samba, and although I caught the problem within less than an hour thanks to Tiny Personal Firewall blocking an outbound packet, I still lost two Win98 systems to the Chernobyl virus (it rode in on a zombie program and propagated through Samba because of that mis-configuration). That one is so dangerous that I didn't try to disinfect, just moved the data itself over to another box, then did total reformat of the affected drives and reinstalled...


All times are GMT -5. The time now is 07:02 AM.