Linux-Networking Digest #54, Volume #11 Thu, 6 May 99 00:13:32 EDT
Contents:
Re: Sybase ASE on Linux faq needed (Ryan Lubke)
SAMBA: How to get a complete list of computers Netbios name and IP addresses in a NT
network using a SAMBA CLIENT? ("John Wong")
SAMBA: How to get a complete list of computers Netbios name and IP addresses in a NT
network using a SAMBA CLIENT? ("John Wong")
SAMBA: How to get a complete list of computers Netbios name and IP addresses in a NT
network using a SAMBA CLIENT? ("John Wong")
Re: Apache Server Problem (Jim Roberts)
Sybase ASE on Linux faq needed ([EMAIL PROTECTED])
Re: Crontab woes with RH5.2 ("Curt")
Re: Redhat 6.0... the good, the bad, and the ugly ("Erik")
Re: 3Com 3C900 Broke With Kernel 2.2.3 Upgrade (help please!) ([EMAIL PROTECTED])
Re: Linux Uptimes (David Polete)
Re: IP forwarding doesn't forward!! ("Dan Miller")
Re: NT Domain authenticating through Linux IP Masq? (Ron Black)
Apache Server Problem (JLocke1122)
Re: Samba as a printer server->suggestions (Rich Piotrowski)
----------------------------------------------------------------------------
Date: Wed, 05 May 1999 22:01:07 +0000
From: Ryan Lubke <[EMAIL PROTECTED]>
Subject: Re: Sybase ASE on Linux faq needed
Crossposted-To:
sybase.public.sqlserver.linux,comp.os.linux.setup,comp.os.linux.hardware
Hello,
Take a peek at Michael Peppler's FAQ for ASE on Linux:
http://www.mbay.net/~mpeppler/Linux-ASE-FAQ.html
His page also has links to other sybase related sites (not necessarily Linux
though)
Regrards,
Ryan Lubke
Sybase, Inc.
[EMAIL PROTECTED] wrote:
> Hello everyone,
>
> Can someone plese post a faq on Sybase ASE installation in Redhat Linux?
>
> I'm a newbie to Linux (1 week) and Sybase (3 weeks) although I have some
> background in Unix and MS SQL. Got a book on Linux, few books on Sybase but
> I noticed that each version and Operating system platform has certain
> differences.
>
> Linux is running without X windows yet. I still have to download
> X drivers for my SIS 6326 video card. I've also extracted Sybase
> using Redhat Package Manager to /opt/sybase
>
> I need to find out the permissions, block directory structure and
> general installation procedure. Don't know how to access the documentation
> (*.gif files) from a Win95 station yet.
>
> Any input on directory size requirements, connectivity via Win95- Sybase
> Central, etc. I've tried open client at work.
>
> Thanks in advance
>
> -----------== Posted via Deja News, The Discussion Network ==----------
> http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
------------------------------
From: "John Wong" <[EMAIL PROTECTED]>
Subject: SAMBA: How to get a complete list of computers Netbios name and IP addresses
in a NT network using a SAMBA CLIENT?
Date: Thu, 6 May 1999 07:16:16 +0800
Dear Linux Advancers,
I have a Linux box on an NT network and use smbclient. However, I have
to know the IP of the service-providing computer in advance. That's
troublesome..
How to get a complete list of computers Netbios name and IP addresses in
a NT network using a SAMBA CLIENT?
Thank you
Best Regards
John
------------------------------
From: "John Wong" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux,comp.os.linux.help,comp.os.linux.setup
Subject: SAMBA: How to get a complete list of computers Netbios name and IP addresses
in a NT network using a SAMBA CLIENT?
Date: Thu, 6 May 1999 07:20:13 +0800
Dear Linux Advancers,
I have a Linux box on an NT network and use smbclient. However, I have
to know the IP of the service-providing computer in advance. That's
troublesome..
How to get a complete list of computers Netbios name and IP addresses in
a NT network using a SAMBA CLIENT?
Thank you
Best Regards
John
------------------------------
From: "John Wong" <[EMAIL PROTECTED]>
Subject: SAMBA: How to get a complete list of computers Netbios name and IP addresses
in a NT network using a SAMBA CLIENT?
Date: Thu, 6 May 1999 07:14:59 +0800
Dear Linux Advancers,
I have a Linux box on an NT network and use smbclient. However, I have
to know the IP of the service-providing computer in advance. That's
troublesome..
How to get a complete list of computers Netbios name and IP addresses in
a NT network using a SAMBA CLIENT?
Thank you
Best Regards
John
------------------------------
From: [EMAIL PROTECTED] (Jim Roberts)
Subject: Re: Apache Server Problem
Date: Thu, 06 May 1999 02:40:56 GMT
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] (JLocke1122) writes:
> How do I let my users modify web page space (via the network) with an apache
> server running. I can view the html files, but I can't upload files. Same with
> the ftp.
>
> Help!
>
> Jeremy
Jeremy,
Check at http://www.cgi-resources.com/ There you will find
all kind of web based upload and administration scripts that
will work with the Apache server. Most are free.
--
Jim Roberts Never enough time!
[EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED]
Crossposted-To:
sybase.public.sqlserver.linux,comp.os.linux.setup,comp.os.linux.hardware
Subject: Sybase ASE on Linux faq needed
Date: Wed, 05 May 1999 22:40:56 GMT
Hello everyone,
Can someone plese post a faq on Sybase ASE installation in Redhat Linux?
I'm a newbie to Linux (1 week) and Sybase (3 weeks) although I have some
background in Unix and MS SQL. Got a book on Linux, few books on Sybase but
I noticed that each version and Operating system platform has certain
differences.
Linux is running without X windows yet. I still have to download
X drivers for my SIS 6326 video card. I've also extracted Sybase
using Redhat Package Manager to /opt/sybase
I need to find out the permissions, block directory structure and
general installation procedure. Don't know how to access the documentation
(*.gif files) from a Win95 station yet.
Any input on directory size requirements, connectivity via Win95- Sybase
Central, etc. I've tried open client at work.
Thanks in advance
============= Posted via Deja News, The Discussion Network ============
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
------------------------------
Reply-To: "Curt" <[EMAIL PROTECTED]>
From: "Curt" <[EMAIL PROTECTED]>
Subject: Re: Crontab woes with RH5.2
Date: Wed, 5 May 1999 19:50:41 -0500
The simplest way to add a cron job under redhat is to add a working script
to /etc/cron.daily, hourly, weekly, monthly. However, this may not meet
your needs.
------------------------------
From: "Erik" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.hardware,comp.os.linux.setup
Subject: Re: Redhat 6.0... the good, the bad, and the ugly
Date: Wed, 5 May 1999 20:44:29 -0600
>>Where is everyone getting RH6.0? I thought it wasn't available until the
>>10th May....
>
>Nope been out at least a week by now.
>www.redhat.com and all its mirrors. The pressing shops probably will not
>be shipping for another week however.
I got a confirmation that cheapbytes shipped my RH6 CD today.
Erik
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: 3Com 3C900 Broke With Kernel 2.2.3 Upgrade (help please!)
Date: Thu, 06 May 1999 00:36:55 GMT
I think you should try the new dhcpcd rpm. Redhat 5.2's dhcpcd doesn't work,
so you should upgrade, if you haven't already.
You could try configuring the IP address manually, if you have a static one.
This would show whether dhcpcd is to balme or not
Mark.
In article <7evf52$[EMAIL PROTECTED]>,
"Chris Cantwell" <[EMAIL PROTECTED]> wrote:
> Perhaps this driver was compiled in the old kernel, and now it is configured
> as a module. Have you setup the conf.modules properly?
> alias eth0 3c5x9 (I think this is right, you may want to check the driver
> name)
>
> did you rerun lilo?
> /sbin/lilo -v
>
> If all else fails, try recompiling the kernel with the 3c5x9 module, and
> setup conf.modules as above. Rerun lilo, and retry. See the Kernel-HOWTO.
>
> Chris Cantwell
>
> Howard Au wrote in message <[EMAIL PROTECTED]>...
> >I'm getting very desperate. I installed Mandrake Linux 5.3 (Kernel
> >2.0.36) for the first time a couple weeks ago and have been using it
> >problem free. But I recently installed the RPM's for the Kernel
> >2.2.3-ac4 upgrade using kpackage, updated the lilo.conf file, and the
> >new kernel booted just fine, except that my ethernet card has suddenly
> >stopped working. The "using DHCP for eth0" line found during the boot
> >process now says "Failed" after a few seconds. It's a PCI card, 3Com
> >3C900-TPO connected to a RoadRunner cable modem (uses DHCP server). When
> >I upgraded I installed all the RPM's available on the FTP site,
> >including the DHCP update, and as far as I can tell they all installed
> >with no problem.
> >
> >The card is detected properly during the boot and has no conflicts with
> >any other hardware. Here's some of the output from dmesg:
> >
> >-----------
> >3c59x.c:v0.99H 11/17/98 Donald Becker
> >http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html
> >eth0: 3Com 3c900 Boomerang 10baseT at 0xff00, 00:a0:24:d1:45:19, IRQ 10
> >
> >8K word-wide RAM 3:5 Rx:Tx split, 10baseT interface.
> >Enabling bus-master transmits and whole-frame receives.
> >-----------
> >
> >So I went to the /var/log/message file and had a look through it for any
> >info
> >that it might give about why it's not working... this is what I found
> >that was
> >related to my network card:
> >
> >-------------
> >Apr 9 20:47:05 COOLIE kernel: 3c59x.c:v0.99H 11/17/98 Donald Becker
> >http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html
> >Apr 9 20:47:05 COOLIE kernel: eth0: 3Com 3c900 Boomerang 10baseT at
> >0xff00, 00:a0:24:d1:45:19, IRQ 10
> >Apr 9 20:47:05 COOLIE kernel: 8K word-wide RAM 3:5 Rx:Tx split,
> >10baseT interface.
> >Apr 9 20:47:05 COOLIE kernel: Enabling bus-master transmits and
> >whole-frame receives.
> >Apr 9 20:46:32 COOLIE kerneld: Starting kerneld, version 2.1.121 (pid
> >141)
> >Apr 9 20:46:32 COOLIE kerneld: kerneld startup succeeded
> >Apr 9 20:46:32 COOLIE kerneld: started, pid=141, qid=0
> >Apr 9 20:46:32 COOLIE ifup: SIOCADDRT: Network is unreachable
> >Apr 9 20:46:34 COOLIE network: Bringing up interface lo succeeded
> >Apr 9 20:46:34 COOLIE ifup: Using DHCP for eth0...
> >Apr 9 20:46:34 COOLIE dhcpcd[233]: ioctl SIOCSIFBRDADDR (ifConfig):
> >Cannot assign requested address
> >Apr 9 20:47:04 COOLIE ifup: failed.
> >Apr 9 20:47:04 COOLIE network: Bringing up interface eth0 failed
> >--------------
> >
> >I can ping my own IP, but anything else just doesn't work. I've tried
> >specifying addresses manually (nameserver, gateway, etc) using ifconfig
> >and netcfg in X, as well as Linuxconf but nothing works. I usually get
> >the "cannot assign requested address" or some other such message. If
> >anyone has any ideas as to how to solve this, I'd be very grateful :)
> >
> >Howard
> >
>
>
============= Posted via Deja News, The Discussion Network ============
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
------------------------------
From: David Polete <[EMAIL PROTECTED]>
Subject: Re: Linux Uptimes
Date: Wed, 05 May 1999 20:33:24 -0500
I Hate SPAM wrote:
>
> On 28 Apr 1999 14:29:19 GMT, Willis Sarka III <[EMAIL PROTECTED]>
> wrote:
> >Hello all,
> >
> >I am writing a proposal to my work about the benefits of using Linux.
> >I would like to site some uptime examples. Does anyone out there have
> >some good uptimes of a year or more? Any famous examples or anecdotes?
> >
> >Much thanks in advance.....
>
> My 2 servers:ddd:hh:mm:ss
> Netware 3.11 899:15:23:26 and counting 486dx2/66 20 Mb RAM
> Netware 3.12 876:11:06:15 and counting 486dx2/66 16 Mb RAM
>
> Just getting the Linux box up, check back with me in 3 years <G>.
>
i hate to say it, but i have to....
the installation problem is that of the admin's competency, not the OS.
while i had a few problems with the install, it was solely due to the
diverse variety (non-standardization? non-comformance to standards??)
of the pee-cee equipment NOT the OS. once the quirks of your particular
hardware are known then linux is quite capable and not that difficult to
install. in short - blame the hardware manufacturers, not the poor
souls
left trying to sort out the mess during the install.
as for uptimes, i've personally seen 4+ months on machines without UPS's
and that i don't take seriously. on the other side of the coin, those
same machines weren't under much of a load.
as for one under a load, i have one that's been up for over 30 days at
since the last reboot due to modifications that required it. prior to
that i was seeing 4 to 6 weeks, again, with reboots only due to
upgrades/mods. this machine is a 486-dx4/100, no cache, 6gb of disk,
and
two network cards. it provides NAT, DNS, mail (host and pop/imap), http
proxy, samba file/print services, DHCP, news, and a ssh/ppp VPN tunnel
to
another site running a sparc 20 under solaris 2.6. NOT ONE DAMN HITCH!
sure, it could use some cache, a faster CPU, SCSI disks (vs. eide
_crap_)
but for $0.00 investment it works - and works well. it was a
hand-me-down
from someone who had to have a 'fast' machine (if there is such a
pee-cee)
to run winblows (aka-CPU pig). sure, i'd prefer to have another sparc
doing
the job, but capability-per-dollar it can't be beat (note i said
'capability'
_not_ performance). this particular platform wouldn't be my first
choice if
wanting to run linux as a personal workstation with staroffice and
netscape,
but i certainly wouldn't turn it down as a freebie. as to providing
basic
network services where the network often tends to be a bigger bottleneck
than
the host it is *extremely* viable.
btw, the linux box _is_ scheduled to be replace by another sparc 20, but
it
got us going in the near term, while arranging for the long term
solution.
notice something? no problem with linux matching wits with solaris.
since
linux is a **IX derivative i was able to take my 'true' **IX services
and
configure them on the linux box. this linux box can participate as a
'service'
equal to the sparc although certainly not a 'performance' equal.
context
switching on an x86 and i/o on an IDE device can't come close to sparc
(or
rs/6000, alpha, etc. pick your preference) and SCSI.
back to uptimes - M$ has been quite boastful about NT running for 'up to
28
days'. sadly enough, the reboots at that point are not normally
'scheduled'.
i think most **IX admins would agree - if our track record were that bad
we'd
be on the street (voluntarily?) looking for a new line of work. hell,
win95
can't even go 28 hours without displaying its BSOD (blue screen of
death,
ie - the 'windows screensaver'). typical **IX machines run for months
(often 12 or more) without a need for rebooting - voluntarily or
otherwise.
as for our novell friend - nothing wrong with that as a solution, and
from
my observations, just about as reliable in many ways. novell's only
downside
is that it is not as flexible or widely supported as **IX. you can't
cheaply
and easily source alternative solutions to your network needs as with
the **IX
world. regardless, novell is certainly viable in a small (even medium?)
sized
operation that wants a 'turn-key' solution and little administrative
overhead.
unfortunately, it is also a proprietary solution that leaves you buying
solutions
rather than providing them.
naturally IMHO,
dp
------------------------------
From: "Dan Miller" <[EMAIL PROTECTED]>
Subject: Re: IP forwarding doesn't forward!!
Date: Wed, 5 May 1999 18:58:39 -0700
.... from the "server" machine:
# netstat -nr
Destination Gateway Flags Use Interface Pmtu
127.0.0.1 127.0.0.1 UH 0 lo0 8232
192.168.72.200 192.168.72.200 UH 0 dleth0 8232
192.168.74.204 192.168.74.204 UH 0 dlsl0 8232
192.168.74.210 192.168.74.204 UH 3 dlsl0 1500
192.168.72.0 192.168.72.200 U 2 dleth0 1500
192.168.75.0 192.168.74.210 UG 0 dlsl0 1500
127.0.0.0 127.0.0.1 U 0 lo0 8232
0.0.0.0 192.168.72.1 UG 0 dleth0 1500
.... from the "client" machine:
# netstat -nr
Destination Gateway Flags Use Interface Pmtu
127.0.0.1 127.0.0.1 UH 0 lo0 8232
192.168.74.210 192.168.74.210 UH 0 dlsl0 8232
192.168.74.204 192.168.74.210 UH 36 dlsl0 1500
0.0.0.0 192.168.74.204 UG 0 dlsl0 1500
Curt wrote in message ...
>Please post the result of netstat -nr
>
>Dan Miller <[EMAIL PROTECTED]> wrote in message
>news:7gqmbj$[EMAIL PROTECTED]...
>> I have two linux machines connected via a point-to-point link...
>> The two machines can ping each other successfully. One of the
>> machines is connected to a LAN via Ethernet, and can
>> successfully ping and otherwise access that network. However,
>> the "remote" machine cannot access (even ping) the LAN...
>> in fact, it can't even ping the Ethernet side of the main machine.
>>
>> I *have* IP forwarding turned on, on both machines.
>>
>> What else do I have to know about this??? Why won't our
>> local server pass the packets along???
>>
>> Dan Miller
>>
>>
>>
>
>
------------------------------
From: Ron Black <[EMAIL PROTECTED]>
Crossposted-To: comp.os.ms-windows.nt.admin.networking
Subject: Re: NT Domain authenticating through Linux IP Masq?
Date: Wed, 05 May 1999 23:15:23 -0400
I did something like this last week.
net 1 = NT Server as PDC we 30 w 95 boxes
net 2 = 8 pc's with win95
router - linux (without samba)
net 2 pc's can get validation from net 1 pdc with the following - nt
domain logon, workgroup = domanin name and a manual modification to the
pc's routing table to point to the net1 network.
good luck
Adam Haeder wrote:
> My network -
> Formerly, we had a 64 IP subnet. But we changed ISPs and only got an 8
> IP subnet. So we had to put most systems behind a proxy. However, the
> PDC in our NT domain (that everyone logged into) also runs Exchange
> Server, so it needs a direct connection to the internet. NT
> PDC/Exchange Server is on a valid internet IP. Also on this same valid
> internet subnet, one NIC of a Linux machine running IP
> Fordwarding/Masquerading. The other NIC in the Linux box attached to a
> 192.168.x.x private IP network. My user's systems (mostly Win95) are
> on this private IP network and all point at the Linux machine
> (192.168.1.1) as their gateway. This works fine for internet access,
> etc. Plus, if they use their login/password for the NT PDC to log into
> their Windows stations, they can map drives (net use y:
> \\NT_PDC\share). However, they cannot log in to the domain like they
> used to. Obviously, it's because the PDC is now on a different subnet,
> but I don't know if it's as simple as that.
> All I've read about connecting or browsing different subnets assumed
> that both were using routable addresses and were connected by a
> router. My 2 subnets are connected by an IP Forwarder/Masquerader, and
> one subnet is non routable. I've tried putting the PDC's IP in the
> lmhosts file on the systems, using #PRE and #DOM, to no avail. The PDC
> is running WINS, and all the private IP workstations point to it, but
> I don't see the server in the browse list and I can't log into the
> domain. I even looked at having the Linux box join the NT domain
> through Samba, and it did, but it won't authenticate logins meant for
> the domain. Is there any easy way out of this? Currently, I don't have
> the users log into the domain anymore and I just put a shortcut to
> their login script in their Startup folder. Terrible, I know, but I
> tried many other things and finally gave up.
> Has anyone been in a similar situation and could give me some advice?
> TIA
>
> Adam Haeder
> Technical Coordinator, AIM Institute
> [EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED] (JLocke1122)
Subject: Apache Server Problem
Date: 6 May 1999 01:10:55 GMT
How do I let my users modify web page space (via the network) with an apache
server running. I can view the html files, but I can't upload files. Same with
the ftp.
Help!
Jeremy
------------------------------
From: Rich Piotrowski <rpiotrow*nospammin'*@worldnet.att.net>
Crossposted-To: uk.comp.os.linux,comp.os.linux.setup
Subject: Re: Samba as a printer server->suggestions
Date: Wed, 5 May 1999 22:39:51 -0500
On Wed, 05 May 1999, Jose L Gomez Dans wrote:
>Hi!
> After tinkering about with samba for a couple of days, I am unable
>to have a decent printer server up and running. All that is needed is access
>to a single printer (two in the future, if that one works :D). I'd like to
>know how one can achieve that. I read the smb.conf documentation, and the
>other documentation, but got swamped. The FAQ was quite useless, and the
>only resource which was somewhat useful was the SMB-HOWTO. My question is:
>does anyone have one such thing set up, and would be willing to share
>his/her knowledge with me (regarding smb.conf's and stuff like that)? I'm
>getting desperate now!!!
>
> Also, does anyone know how to go around on the clients side, when
>they're using WfWg? I downloaded a TCP/IP driver, and disk sharing is no
>problem. It's only printing that doesn't happen!
>
> Thanks for your help.
>
>--
>Jose L Gomez Dans PhD student
> Radar & Communications Group
> Department of Electronic Engineering
> University of Sheffield UK
Jose,
Here is what works for me. I hope it is some help. Don't forget to create users
and passwords. See "man smbpasswd" .
Rich Piotrowski
*********************** start of smb.conf *******************
# 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 = home
# server string is the equivalent of the NT Description field
server string = jeeves
# 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.100.3 192.168.100.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/smbpasswd
# Unix users can map to different SMB User names
; username map = /etc/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/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 IPTOS_THROUGHPUT SO_RCVBUF=4096 SO_SNDBUF=4096
# 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
# 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 ==============================
# 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
[hpdeskje]
valid users = rich jake mona
printer = hpdeskje
path = /var/spool/samba
public = yes
writable = no
printable = yes
[pub]
path = /pub
valid users = rich jake mona
public = yes
writable = yes
create mask = 0777
[recvq]
comment = Fax Recieve Queues
browseable = yes
path = /var/spool/fax/recvq
public = yes
writable = no
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list (and comp.os.linux.networking) via:
Internet: [EMAIL PROTECTED]
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Networking Digest
******************************
