URGENT: SAMBA - I can't see linux computer in win98 1

[Guest_imported]

I have 2 computers, one have linux and other windows 98.
I configure samba, and I know the configuration is correct.
I can do ping to each machine, but I can't see the linux
computer in windows98. Why? It is strange... Can you help
me? Thanks

 

[fenris]

I am having the same problem, except samba stops working when I put my new 100Mb switch into place...

The hardware...
winMe with a dlink dfe-530 tx
mandrake 7.2 with an identical dfe-530tx
old hub: dlink de-810tac (10 mbs)
new switch: dlink dss-8

I have tested the cables at 100Mb and they work fine. I brought the hub into work and it works fine on the company network. I am pretty sure that the nics are working fine as I haven't been able to plug them into a working 100Mb network.

I suspect that the problem may reside with a samba setting. As i can ping from and to both machines. I am stumped, does any one have any ideas about this one?

Troy Williams B.Eng.
fenris@hotmail.com

 

[bill666]

No encrypted passwords set on Samba server. smb.conf follows:

# 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
#
#======================= Global Settings =====================================
[global]

# workgroup = NT-Domain-Name or Workgroup-Name
netbios name = Bill_linux
workgroup = qmcamc
; workgroup = funlovers
# 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.0. 192.168.1. 127.
; hosts allow = 192.168.0. 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 = lprng

# 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 = 0
; log level = 3

# 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.0.255 192.168.0.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

# 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 &quot;host lmhosts wins bcast&quot;. &quot;host&quot; 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. &quot;host&quot; 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

# 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
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 &quot;staff&quot; 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 = /export/fred
valid users = bill ian
public = no
writable = yes
printable = no
create mask = 0765


Would really appreciate some direction here.

Cheers,
Bill

 

[TheRAt]

change the following lines from:

# 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

to:

# 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

Then restart SAMBA by:

/etc/rc.d/init.d/smb restart

AV
tnedor@yahoo.com

 

[bill666]

Thanks,

The issue has to do with both Win98 and NT4.0 SP 3.0 and beyond: They both use password encryption. There is a registry hack to send plaintext password and it works, but not so good for security. I will try your suggestions and let you know.

Cheers,
Bill

 

[Guest_imported]

My configuration is this (note: I use fake IP's)
I expect that this help you configure samba, and see
Linux in your &quot;Network Neighborhood&quot;, in Win98

------------------------------------------------------------

[global]
workgroup = YOURWORKGROUP
serverstring = SERVERLINUX
socket options = TCP_NODELAY IPTOS_LOWDELAY
os level = 33
security = share
guest account = nobody
encrypt passwords = yes
wins support = yes
browseable = yes
local master = no
domain master = no
preferred master = no
force create mode = 777
log file = /var/log/samba/%m.log
max log size = 50
interfaces = (your Linux IP)/24

[Public Share]
comment = Public Share
path = /home/linuxshare
public = yes
guest ok = yes

------------------------------------------------------------
Obviously, you need to make sure that the &quot;/home/linuxshare&quot; dir exists and for testing purposes make it accessable to everyone (chmod 777 /home/linuxshare)

Then restart SAMBA by:

/etc/rc.d/init.d/smb restart

 

[bill666]

Bingo! Password encryption is what win98/winnt needs to connect to Samba. I am kind of amazed that Samba does not have this as a default setting given that this is the preferred way to authenticate. and plaintext is not secure!

Thanks for your help.

Kind Regards,
Bill

 

[TheRAt]

Really depends on what you mean by secure... In my opinion, both methods have certain issues.

Plain text allows passwords to travel as clear text over the network when logging in, which is certainly a problem.

&quot;The SMB encryption scheme never sends the cleartext password over the network, but it does store the 16 byte hashed value on disk.&quot;

This is bad because it although it is impossible to derive the users password from this, it is possible to use this with a modified client to gain access to a server!!

(Just some infor from ENCRYPTON.txt in the SAMBA docs for my installation...)

AV
tnedor@yahoo.com

 

[Guest_imported]

This is a really samba configuration

 

[Guest_imported]

Really Helpfull

 

[mikeo2l]

Slightly different problem (apart from can't spell)

I can see the linux box in my network but can't access it. The error reported is: &quot;A duplicate name exists on the network&quot;... I only have two PC's connected!
Mike

 

[mikeo2l]

Just a note re can see but can't access:
I am using Mandrake 8.0 and conecting to a win 2000 pc. Have changed the samba config... all over the place...
I need to know if it's possible to use the linux box for:

1 - internet Access (using firewall and modem/connection sharing with the win 2000 pc)

2 - Access php files on the server (linux box) using the browser on 2000. IIS on the windows pc limits the connections to ten and times out after 900 seconds.

And the above post? any help would be appreciated. Mike

 

[mikeo2l]

Update:

Can now see Linux Box... but when asked for password and username... none of the ones I give allow access. Have decided to read all (every word) about Samba. If that dosent work I'll consider myself an Idiot and give up or re-read it until I get it right. Many thanks to all who helped. :d

 

[clickguy]

Hi.

I'm also having a similar problem with getting Samba to work. I think I'm *almost* there.

I have a Win98 and a RH 7.1 connected via a Linksys router. I'm able to see the Linux box as a network icon on my Win98. My problem is that when I click on the Linux icon I get:

\\Linuxbox1 is not accessible
The computer or sharename could not be found.

My smb.conf is basically the same as bill666 posted above.

I also have

encrypt passwords = yes
smb passwd file = /etc/samba/smbpasswd

I did an smbadduser joe:joe and typed in a password.

Did the /etc/rc.d/init.d/smb restart as well.

Any ideas on why I can see the Linux icon but still get the \\Linuxbox1 is not accessible error message?

Thanks!

 

[stanhubble]

Do you have any shares defined that are browsable?
Try to set one up that is wide open and see if it can be browsed. Then try some user specific shares.
Also check that nmbd is running.

Can you run swat from the 98 box?

 

[clickguy]

I set browseable = yes and writable = yes for a /share directory.

Also ps -ef shows both smbd and nmbd to be running.

I haven't tried running swat from the 98 box. I've been modifying the smb.conf file directly.

 

[clickguy]

Ahhh...Figured it out, thanks in part to the hint from stanhubble.

I tried to enable swat and access it from my 98 box. At first it wasn't working so on the Linux side I ran tcpdump to see the traffic. I noticed that the swat port was getting rejected so that made me think about the firewalls.

I ran lokkit and turned off all the firewalls and now I can see my Linux box!

Now I just have to work my firewalls back up again.

Thanks all!

 

[Guest_imported]

i have 56 kbs motorola internal modem.pl help me how to make modem work in linux7.0,I had tried all the probabilities. but i could'nt suceed.

with rgds,
shashidhar