RE: [Samba] Samba 2.2.7 on Red Hat 8.0 and Windows 2000

2003-01-13 Thread A. Rosina Bignall

Yes, it sounds like the same problem I had as well.  Try opening up your
firewall completely.  Once you get samba working, set up the firewall
again.  I set mine up so that my ethernet connection (device eth0) is
trusted.  Redhat has made it easy for basic configuration of the
firewall using the Security Level editor (from the System Settings
submenu if you use the standard setup Redhat ships or
redhat-config-securitylevel).  Using that tool, set the Security Level
to "No firewall" verify that samba is working as expected, then figure
out what you want your firewall to be set at.  Mine is set at "High",
then I customize so that eth0 is a trusted device.  Alternatively, you
could allow incoming to the port samba uses, but I haven't tried that --
given that I just have two machines that only I use, trusting eth0 is
good enough for me ;).

Rosina

On Sat, 2003-01-11 at 23:18, naugaranch wrote:
> Jose,
> 
> Sounds like the same problem I had.  And related to the firewall on the RH8
> box (particularly if its built as a server).  Try stopping IPChains and
> IPTables in the services.  If you can access the RH8 shares after doing
> this - you need help getting the firewall set up (something I have not done
> here and also need to learn).
> 
> Tom Winfield
>   -Original Message-
>   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Jose Medrano
>   Sent: Friday, January 10, 2003 10:27 PM
>   To: [EMAIL PROTECTED]
>   Subject: [Samba] Samba 2.2.7 on Red Hat 8.0 and Windows 2000
> 
> 
>   I'm traying to access my Red Hat 8.0 box from windows 2000 professional.
> I'm using samba 2.2.7a and I can see the linux box on the windows 2000
> network , but when I click on it I get the message 'System error 53 can't
> find the netwok path... can some one help me please
>   I don't have any problem accessing the windows 2000 box
>   from my linux server.
>   I tried both DHCP and fixed IP address and I get the same
>   results.  I use 'support Wins' on my smb.conf and the linux server IP as
> my wins server on the windows 2000.
> 
> 
> 
> 


-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba



RE: [Samba] Please help! Updated to Redhat 8.0, now can't getsamba to work

2003-01-13 Thread A. Rosina Bignall
On Sat, 2003-01-11 at 23:18, naugaranch wrote:
> A couple of questions,
> 
> Did you re-establish user passwords in Samba?
> Why do you have the smb.conf line
> 
>   deny hosts = ALL

So that when I have my internet connection up, other hosts out there
cannot connect to my machine, only the ones on my local net. The next
line that says hosts allow ... lets in the machines on my local net. Am
I misunderstanding this? At any rate, this is exactly how I had it
before I upgraded and it worked.

> 
> Seems like this would reject all connections.
> 
> Is the firewall running (IPCHAINS & IPTABLES).  If so, have you set it up
> properly?
> 

Hmm... I think so, but I haven't done much with the firewall since I
installed, just left it with the defaults.  Let me open it up wide and
see what happens...

Oh yes! That worked.  Thank you very much! I should have thought about
the firewall. I set eth0 to be a trusted device and the security level
at High, so I should be pretty well set now.

Thanks again.

Rosina



-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba



[Samba] Please help! Updated to Redhat 8.0, now can't get samba to work

2003-01-10 Thread A. Rosina Bignall
I just installed Redhat 8.0, got the errata samba packages, but I still
can't get Samba to work.  I have gone through the Diagnosis.txt file
with the following results:

Test 1:
everything appears OK

Test 2:
pings work both ways

Test 3:
OK

Test 4:
# nmblookup -B lion __SAMBA__
querying __SAMBA__ on 192.168.8.14
192.168.8.14 __SAMBA__<00>

OK

Test 5: 
# nmblookup -B cub '*'
querying * on 192.168.8.15
192.168.8.15 *<00>

Test 6:
# nmblookup -d 2 '*'
added interface ip=192.168.8.14 bcast=192.168.255.255 nmask=255.255.0.0
added interface ip=172.16.191.1 bcast=172.16.191.255 nmask=255.255.255.0
added interface ip=192.168.250.1 bcast=192.168.250.255
nmask=255.255.255.0
querying * on 192.168.255.255
querying * on 172.16.191.255
Got a positive name query response from 172.16.191.128 ( 172.16.191.128)
172.16.191.128 *<00>

Not the same as Test 5, but I think it's still okay.

Test 7:
OK

Test 8:
C:\WINDOWS> net view \\lion
Error 59: An unexpected network error has occurred.  Quit all running
programs, restart your computer, and then try again.  If the problem
persists, contact your network administrator.

The problem persists.  I'm not an expert in network stuff and this is
just a network between my Linux host and my PC runinng on VMWare on the
same machine. I have no idea what would cause this. Please help.

Test 9:
C:\WINDOWS> net use x: \\lion\tmp

Same message as in Test 8

Test 10:
# nmblookup -M Workgroup
querying Workgroup on 192.168.255.255
querying Workgroup on 172.16.191.255
172.16.191.128 Workgroup<1d>

Test 11:
File manager won't connect to it.

Please help me understand what is wrong and how to fix it.  Below, I've
included my smb.conf.  Let me know of any other information that is
needed.

Thanks!

Rosina

# 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 = Workgroup

# 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 deny = ALL
hosts allow = 192.168. 127. 172.16.

# 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 = 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
# The argument list may include:
#   password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
# or to auto-locate the domain controller/s
#   password server = *
;   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
   encrypt passwords = yes
   smb passwd file = /etc/samba/smbpasswd

# The following is needed to keep smbclient from spouting spurious errors
# when Samba is built with support for SSL.
;   ssl CA certFile = /usr/share/ssl/certs/ca-bundle.crt

# The following are needed to allow password changing from Windows to
# update the Linux system 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