Linux-Networking Digest #624, Volume #12         Fri, 17 Sep 99 22:13:43 EDT

Contents:
  Re: Top 10 IP talker (DanH)
  Re: Why can't I telnet to root ?? (Theresa Halloran)
  Re: Mapping Drives in Linux ("William B. Arnold")
  looking for a final year undergrad project ("Rishabh Tandon")
  Re: ProftpdHelp: ftp: bind: Address already in use. Solaris 2.6 Sparc ("Chris 
Fanning")
  Re: admin contacts (DanH)
  Re: Why can't I telnet to root ?? (DanH)
  Disappearing Server and nmbd errors ("Michael L. Black")
  Re: can't locate module lo  and  eth0 (DanH)
  Re: Linux 4 A Small Office ("charles blackburn")
  Re: BNC == Rude. ("CFT")
  Re: Getting linux to notice 3Com Etherlink III ("William B. Arnold")
  Re: Help with Win95 and Samba ("William B. Arnold")
  Re: how to set up a bridge between 2 networks? (DanH)
  linux+win98 ("BT Internet News Server")
  Re: IP Forwarding based on hostname (Bernd Eckenfels)
  How to roll a kernel for debian? (Robi)

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

From: DanH <[EMAIL PROTECTED]>
Subject: Re: Top 10 IP talker
Date: Fri, 17 Sep 1999 19:47:11 -0400

Roar Pettersen wrote:
> 
> Hello !
> 
> I'm looking for a sofware which look at the subnet,
> and generte a "Top 10" IP talker.

You're looking for ntop. Do a web search on it (or linuxberg).

It's free too.

Dan
-- 
UNIX - Not just for vestal virgins anymore
Linux - Choice of a GNU generation

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

From: Theresa Halloran <[EMAIL PROTECTED]>
Subject: Re: Why can't I telnet to root ??
Date: Fri, 17 Sep 1999 15:32:02 +0000

Mark,
    You need to add the shell you are using when you login as root to the
/etc/shells file. Then it will let you telnet to linux machine.

Regards,
Ramesh

Mark Cooperstein wrote:

> Whenever I try to telnet to my Linux box as user "root", it will not
> authenticate me, even though I put in the correct password.  I can telnet to
> my Linux machine as any other user.  I can also "su" once I've done this and
> become root, but it sure would be nice to telnet there directly.
>
> Mark
>
> **  Remove ".nospam" when replying or email will bounce back to you...


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

From: "William B. Arnold" <[EMAIL PROTECTED]>
Subject: Re: Mapping Drives in Linux
Date: Fri, 17 Sep 1999 19:54:16 -0400

Lance Hoffmeyer wrote:
> 
> I am setting up a home network.  I have a server with a 'Data' directory
> that I want to client to be able to read.  I can ping the server but
> the client machine does not 'see' any of the servers directories.  How
> do I get the client to see directories on the server?
> 
> Both machines run linux and ext2 fs.
> 
> Lance
> 
> Sent via Deja.com http://www.deja.com/
> Share what you know. Learn what you don't.


Greetings,

The simpliest is NFS.

Server:   192.168.0.1   server

/etc/hosts
192.168.0.1   server
129.168.0.2   client

a directory /data exists on server, ensure it has read/write for users
and groups

/etc/exports
/data      client(rw,no_root_squash)     
     

running the nfs daemon 
verify by:
/etc/rc.d/rc3.d 
S55nfs

/etc/rc.d/init.d/nfs status
if not running start by
/etc/rc.d/init.d/nfs start
then check status
/etc/rc.d/init.d/nfs status
if running then

Client:   192.168.0.2   client

/etc/hosts
192.168.0.1      server
192.168.0.2      client

/etc/fstab
server:/data  /data    nfs users,exec,dev,suid,rw,noauto,bg,soft 1 1

issue command on client

mount server:/data 
or
mount /data

cd /data
ls -l

you should see all the files if the proper attributes are set on the
server.

Works like a champ.  Great to be used as a single file server holding
all the most recent updated rpm files to upgrade enmass clients:-)

Bill...

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

From: "Rishabh Tandon" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.ms-windows.programmer.networks
Subject: looking for a final year undergrad project
Date: Sat, 18 Sep 1999 02:20:25 +0530

guys I'm looking for a final year undergard project If U have anything at
the back of ur mind please let me know

Regards


--

Rishabh
http://members.tripod.com/rishabh_tandon

NEVER PROMISE MORE THAN WHAT "U" CANNOT DO AND ALWAYS DO MORE THAN WHAT "U"
PROMISE



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

From: "Chris Fanning" <[EMAIL PROTECTED]>
Subject: Re: ProftpdHelp: ftp: bind: Address already in use. Solaris 2.6 Sparc
Date: Fri, 17 Sep 1999 16:07:25 +0200

Try removing the the default ftp entry in /etc/inetd.conf

Chris

Abe Lin escribió en mensaje <[EMAIL PROTECTED]>...
>Sorry, guys, but I'm puzzled:
>
>Basically I installed Proftpd 1.2.0pre6 on a Solaris SPARC.
>ftp in okay, and when I do ls, it says ftp: bind: Address already in
>use.
>This didn't happen in Linux...
>
>Cannot figure out why, and port 20 is free. Help!
>
>Shuo
>
>
>
>Here's the detail:
>
>Install:
>./configure  --prefix=/usr/local/proftpd;make; sudo make install;
>
>Test configuration:changed the default one only by one line:
>Port                           2121
>
>Server run as standalone:
>sudo /usr/local/proftpd/sbin/proftpd -c
>/usr/local/proftpd/etc/proftpd.conf
>
>
>====================Begin Failed
>session===================================
>[shuo@mtlweb03 shuo]$ ftp xxx.xxx.com 2121
>Connected to xxx.xxx.com.
>220 ProFTPD 1.2.0pre6 Server (ProFTPD Default Installation) [mtlweb02]
>Name (xxx.xxx.com:shuo): shuo
>a331 Password required for shuo.
>Password:
>230 User shuo logged in.
>Remote system type is UNIX.
>Using binary mode to transfer files.
>ftp> bin
>200 Type set to I.
>ftp> ls
>500 Illegal PORT command.
>ftp: bind: Address already in use
>ftp> ls
>ls
>500 Illegal PORT command.
>ftp> 500 Illegal PORT command.
>====================End failed
>session+++===============================
>
>
>###################Tried to see if port 20 is
>occupied:################
>
>bash-2.02$ sudo ./lsof -i [EMAIL PROTECTED]:2121
>COMMAND   PID USER   FD   TYPE     DEVICE SIZE/OFF NODE NAME
>proftpd 24719 shuo    0u  inet 0x61868ae0    0t182  TCP
>mtlweb02:2121->montreal.sitepak.com:64136 (ESTABLISHED)
>proftpd 24719 shuo    1u  inet 0x61868ae0    0t182  TCP
>mtlweb02:2121->montreal.sitepak.com:64136 (ESTABLISHED)
>bash-2.02$ sudo ./lsof -i [EMAIL PROTECTED]:20
>bash-2.02$
>bash-2.02$ sudo ./lsof -i [EMAIL PROTECTED]:21
>bash-2.02$
>####################End try. It's
>free.################################



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

From: DanH <[EMAIL PROTECTED]>
Subject: Re: admin contacts
Date: Fri, 17 Sep 1999 20:02:39 -0400

Marek wrote:
> 
> [EMAIL PROTECTED] wrote:
> >
> > On Fri, 17 Sep 1999 16:53:30 -0500, Marek <[EMAIL PROTECTED]> wrote:
> >
> > >Im expireincing a lot of tries of breaks into my computer.
> > >I would like to contact with this domain administrator to see what is
> > >going on. How can I find administrator's email adress for specific
> > >domain.
> > >Is it always "root" or it could be diffrent one???
> > If you know the domain name (URL), run 'whois domain_name'.  If you
> > only know the IP, run 'nslookup IP' first and then whois on the domain
> > name nslookup spits out.  The administrative contact is always listed
> > in the whois record.
> >
> 
> well.. I know whois tool but the problem is that it does nto work for
> this domain.
> Any other tools??

traceroute to the IP address and write 'admin@' 'abuse@'  the last
couple domains you come across on the traceroute.  ISPs don't tend to
like it when downstream ISPs allow crackers to continue.

Dan
-- 
UNIX - Not just for vestal virgins anymore
Linux - Choice of a GNU generation

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

From: DanH <[EMAIL PROTECTED]>
Subject: Re: Why can't I telnet to root ??
Date: Fri, 17 Sep 1999 19:51:25 -0400

Theresa Halloran wrote:
> 
> Mark,
>     You need to add the shell you are using when you login as root to the
> /etc/shells file. Then it will let you telnet to linux machine.
> 
> Regards,
> Ramesh
> 
> Mark Cooperstein wrote:
> 
> > Whenever I try to telnet to my Linux box as user "root", it will not
> > authenticate me, even though I put in the correct password.  I can telnet to
> > my Linux machine as any other user.  I can also "su" once I've done this and
> > become root, but it sure would be nice to telnet there directly.

Most distros will not allow a telnet or any remote login from root by
default (as it should be.)  It's not in the shells, it's in
/etc/security/access.conf

Dan
-- 
UNIX - Not just for vestal virgins anymore
Linux - Choice of a GNU generation

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

From: "Michael L. Black" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.help
Subject: Disappearing Server and nmbd errors
Date: Fri, 17 Sep 1999 17:25:14 -0500

I have a RH 6.0 Linux server and a Windows 95 workstation.
I used to be able to browse the Linux server use Network Neighborhood,
But I am unable to now.

I also get messages as follows:

nmbd/nmbd_incomingdatagrams.c:process_get_backup_list_request(652)
process_get_backup_list_request: Cannot find workgroup <workgroupname> on
subnet UNICAST_SUBNET

Any assistance in determining the cause of these situations,
would be appreciated.

Michael Black



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

From: DanH <[EMAIL PROTECTED]>
Subject: Re: can't locate module lo  and  eth0
Date: Fri, 17 Sep 1999 19:15:57 -0400

Bo Forslund wrote:
> 
> >
> > For now you and i seems to be the only ones on the internet
> > with
> > this problem :-(
> >
> > Grtnx,
> >
> > Jan
> 
> Actually I have this problem on both my two machines. And my neighbour have
> the same on hes machine.
> I guess it isn't that unusual. =)

Check your networking startup scripts.  It's calling for a bogus
interface (or three or so).

Dan
-- 
UNIX - Not just for vestal virgins anymore
Linux - Choice of a GNU generation

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

From: "charles blackburn" <[EMAIL PROTECTED]>
Subject: Re: Linux 4 A Small Office
Date: Fri, 17 Sep 1999 23:30:45 +0100
Reply-To: "charles blackburn" <[EMAIL PROTECTED]>

don't forget linux passwords/logins are case sensitive, also win98 encypts
the password so you may have to turn that off. I can't remember how though.
you need to add a line into the registry.

[ Just remembered :) ]
I think there was a script on the win98 CD that did it actually, have a
trawl around the CD it was in reskit or something like that. it is on there
as I use that. when you find it, right click and select install then just
reboot and it should be OK.

--
Charles Blackburn
=======================================================================
Summerfield Technology Limited - Official SuSE Reseller
E-MAIL: [EMAIL PROTECTED] WWW: http://www.xfr02.dial.pipex.com
FAX: +44-(0)121-624 8698
The opinions stated in this message may not necessarily be
the opinions of the company. They are my own opinions.
=======================================================================

<[EMAIL PROTECTED]> wrote in message
news:7qrkbr$g3a$[EMAIL PROTECTED]...
> PERSONAL PROJECT
>
> I am going to network 3 computers using Win95/98 and Linux OS. The
> computer system might end up in a small office and the Linux will serve
> as a file server and a printer server. Please keep in mind that I never
> network before and I am new to Linux.
>
> I got two computers hook up already. One of the computer have Win 98 SE
> and the other computer have Caldera OpenLinux 2.2.  I made 3 users
> account on the Linux.
>
> NOW THE PROBLEM...
>
> I try to get Samba working but I ran into a problem. In the instruction
> book, it says do the following:
>
> cp smb.conf.sample smb.conf
>
> I did that. Now it says to copy the password file over to the other
> directory by doing this:
>
> cat /etc/passwd | mksmbpasswd > /etc/samba.d/smbpasswd
>
> Now it says to create a user for the Linux and for Windows so I did
> this:
>
> smbadduser Linux-craigc:Samba-craigc
>
> And I got this error:
>
> ERROR: Linux-craigc: Not in passwd database SKIPPING...
>
> So I decided to reboot the Linux with the SMB running and I reboot
> Win98SE to see if it will still work.
>
> Well, it did not work. Win98SE does not recoginize the Linux.
>
> I decided to see if I can ping each machine. On Linux I type:
>
> ping 192.168.1.4
>
> It does ping the Win98SE.
>
> On Win98SE I type
>
> ping 192.168.1.2
>
> It does ping the Linux.
>
> So how do I solve the problem?
>
> Craig
> [EMAIL PROTECTED]
>
> ---- SPECIFICATIONS ON MY COMPUTER SYSTEM ----
> ---- INFO ON LINUX OS ----
>
> On the COAS -> Network -> TCP/IP -> Resolver window
> -information source: host, nis, dns
> -Try to prevent spoofing: checked
> -Report spoof attempts: checked
> -DNS servers: none
>
> On the COAS -> Network -> Ethernet interfaces window
> - Network devices:eth0
> - PNP configuration: disabled
> - Interface address: 192.168.1.2
> - Network mask: 255.255.255.0
> - Broadcast address: 192.168.1.255
> - Default Route: enable
> - Default Gateway: 192.168.1.1
> - Init at boot time: enable
>
> Host name: craig.linux.cars
>
> Network card: Linksys Ether16 10BaseT LAN Model # LNE2000T
>
> -- INFO ON WIN98SE --
>
> In Network settings
> In configuration, it have these items listed:
> - client for Microsoft networks
> - D-Link DFE-530TX PCI Ethernet Adapter
> - TCP/IP
>
> In identifications, it have the following:
> - Computer name: CRAIG
> - Workgroup: WORKGROUP
> - Computer description: <blank>
>
> In Access Control, it have the "Share level access control" checked
>
> In the properties for "Client for Microsoft Networks":
> - Windows NT Domain name: craig.linux.cars
> - Logon and restore network connections (checked)
>
> In the properties for "TCP/IP":
> - IP Address: 192.168.1.4
> - Subnet mask: 255.255.255.0
> - WINS disabled
> - Gateway: 192.168.1.1
> - DNS enable
> - Host: craig
> - Domain: linux
> - DNS search order: 192.168.1.2
> - Netbios enable (can not be disable)
> - Allow binding to ATM - Value = Yes
> - (checked, can not be unchecked) set this protocol to be the default
> protocol
> - Binding (checked) client for Microsoft Networks
>
> The primary Network logon is "client for Microsoft Networks
>
> In the file and print sharing, it is UNchecked for "I want to be able to
> give other access to my files." and "I want to be able to allow others
> to print to
>
>
> Sent via Deja.com http://www.deja.com/
> Share what you know. Learn what you don't.







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

From: "CFT" <[EMAIL PROTECTED]>
Subject: Re: BNC == Rude.
Date: Fri, 17 Sep 1999 13:56:42 -0700

I don't know what's wrong with yours, since I'm fairly new, myself.

I do know that my Linksys EC2T works with thin coax just fine under card
services, so it's not
a support issue.

If that helps any.




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

From: "William B. Arnold" <[EMAIL PROTECTED]>
Subject: Re: Getting linux to notice 3Com Etherlink III
Date: Fri, 17 Sep 1999 19:22:47 -0400

[EMAIL PROTECTED] wrote:
> 
> Well, it seems that despite what the previous posting said, Red Hat 6.0
> installer DID find my SMC card after all.  But it didn't find my 3Com
> Etherlink III Adapter Driver -- so what do I do to get that one noticed?
> 
> Thanks again,
> -ML
> 
> Sent via Deja.com http://www.deja.com/
> Share what you know. Learn what you don't.

Greetings,

I didn't catch any of the previous posts so I'll just jump in :-).

I don't know if you are attempting to run two nics at once or you R&R'd
the two.  I'll presume the later.  If so, the kernal will find only the
first one, if plug and pray and set at the default settings used during
auto-probing.  It will fine the first and stop and continue with the
rest of the boot process.

at the command line after bootup:

modprobe 3c59x  

You should the card configured, IF set at default settings, if not, the
card is NOT set at default settings.  These parameters will have to be
passed as

insmod 3c59x 0x330,10

this of course assumes the card seetings are io = 330 and irq = 10

if so you will see the card initialized, and to note the above settings
are auto-probed so just try 

insmod 3c59x

all should go well.

if not goto this url:

http://cesdis.gsfc.nasa.gov/linux/drivers/index.html#PCI

once the card has been successfully manually added, then edit
/etc/modules.conf
alias eth1 3c59x
alias 3c59x options=ioport,irq  and other necessary options here

This should get you well on your way..

Bill...

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

From: "William B. Arnold" <[EMAIL PROTECTED]>
Subject: Re: Help with Win95 and Samba
Date: Fri, 17 Sep 1999 19:07:01 -0400

fishmaster wrote:
> 
> Thank you all for helping to solve this problem...
> 
> This is what I had done so far.
> 1.    C:\windows\lmhost.sam was renamed to lmhost - that took care of Samba
> Name resolution.
> 2.  c:\windows\hosts.sam was renamed to hosts. This file already had correct
> entries.
> 3.  c:\windows\network file was updated to show that my linux server is a
> local server. I think that this file keeps windows from dialing out to the
> internet!
> 4.  On the Linux side everything was up to the spec: wins support = yes in
> \etc\ smb.conf
> 
> At logon Win95 hangs up.... I think, because I am using Win95.C. This later
> version of windows will NOT support plain text passwords. I'll have to edit
> windows registry or recompile Samba to accept encrypted authentication. I
> can see Linux shares through Windows Explorer by 'finding' Linux server.
> Pinging works now without any problems.
> 
> I am a very happy now!!!  It is a small step for fishmaster toward the Linux
> kind. (So much for me trying to be on the moon)
> 
> Fishmaster
> Steve Cowles wrote in message ...
> >See below
> >
> >Steve Cowles
> >SWCowles at gte dot net
> >
> >
> >fishmaster <[EMAIL PROTECTED]> wrote in message
> >news:VBEA3.4707$[EMAIL PROTECTED]...
> >> Just another cry for help.
> >>
> >> I have two computers. PC1 runs Win95 (950.C) & PC2 runs Red Hat 6.0. I am
> >> trying to setup small local network with Linux being a file /printer
> server.
> >>
> >> Up to now I was able to ping SAMBA server from Win95 client
> >> ping 192.168.20.2, however when I tried to ping using servers name
> >> ping wild.fredy.com stupid Win95  is trying to dial out to internet
> provider
> >> (PC1 has a modem and a network card)!
> >
> >First, Samba (nmb/smb) and ping (ICMP) have nothing to to with each other.
> Samba
> >"typically" uses a WINS server or a lmhosts file for name resolution. It
> can also be
> >configured to use DNS (typically a last resort!!). Ping uses the resolver
> libs which use
> >either the hosts file or DNS for name resolution. I'd be willing to bet
> that your Win95
> >box is dialing out to the internet because you have not listed your linux
> box's ip address
> >in your Win95's hosts file. So it is trying to contact the DNS server of
> your ISP to
> >resolve wild.fredy.com. Another trick I learned (to keep your system from
> falsely dialing)
> >is to add the "workgroup/domain" name to the hosts file or DNS server. ie.
> If you are
> >using workgroup as your "workgroup" name
> >
> >192.168.20.2  wild.fredy.com  wild workgroup
> >
> >be sure that you also specify fredy.com in the "domain" section and also
> the "domain
> >suffix search order" of tcp/ip properties in MS.
> >
> >>
> >> Pinging from Linux is ok both with domain name and IP address!
> >> nmblookup -B ACLIENT '*' finds Win95 client
> >> 192.168.20.9 *<00>
> >>
> >> I am also able to login into Samba server on Linux PC
> >>
> >> I have modified lmhosts.sam file in c:\windows to reflect the server name
> >> (192.168.20.2       wild.fredy.com   #PRE)
> >
> >I hope this was a typo... lmhosts.sam is the "sample" lmhosts file provided
> my MS. If this
> >is not a typo, then rename "lmhosts.sam" to "lmhosts"
> >
> >>
> >> I have also set all the networking parameters in the Network setup
> windows
> >> in Win 95: IP address 192.168.20.9, subnet mask 255.255.255.0, WINS
> >> 192.168.20.2 and etc
> >
> >If your specifing a WINS address, did you enable the "wins support"
> component of Samba??
> >This tells Samba (nmbd) to be a WINS server. Then when your 95 box comes
> up... it will
> >register its self with the WINS server.
> >
> >>
> >> smbclient -L wild.fredy.com on Linux PC returns
> >> Share       Type    Comment
> >> --------         -------    -------------
> >> tmp            Disk      temp files
> >> Profiles     Disk
> >> etc
> >>
> >> SERVER            Comment
> >> -------------             -------------
> >> WILD                   Samba Server
> >>
> >> Workgroup          Master
> >> ---------------          ----------
> >> Mygroup
> >>
> >>
> >> -------------------------------------------------------------------------
> ---
> >> ------------
> >> My problem is some what multi level.
> >> 1. How do I get Win95 to ping properly?
> >
> >You will need to put the ip address of your linux box in the "hosts" file
> on your Win95
> >box. By doing so, your Win95 box will not try to issue a DNS query, which
> is probalby
> >causing your system to dial out to the internet. You should also put the ip
> address of
> >your Win95 box in the /etc/hosts file of your linux box.
> >
> >>
> >> 2. Net View reports error 53 (computer not found) How do I get Network
> >> Neighborhood to see Linux shares?
> >
> >First, enable the "wins support" as mentioned above. Also make sure that
> both win95 and
> >samba are configured for the same workgroup/domain. Then both Samba and
> win95 will
> >register with the WINS server and you will then be able to see both systems
> in "Network
> >Neighborhood". If you want to go one step further... configure Samba to be
> a "logon
> >server/domain controller" and then configure "Client for MS networking" to
> logon to the
> >domain.
> >
> >> I have gone over John Blairs book (Samba Integrating Unix and Windows)
> >> couple of time... I am missing something very obvious????
> >>
> >>
> >
> >
Greetings,

Recompiling Samba for encryted passwords is a no go, reason, to use
encryted passwords, you must:

/etc/smb.conf
[global}
 encrypt passwords = yes
 null paswords = no
 username map = /etc/smbusers
 smb passwd file = /etc/smbpasswd
 update encryted = yes or no
 password server = xxxx  if using a NT domain controller
 min passwd length = x
 passwd program = /bin/passwd
 passwd chat = a script file
 passwd level = ?
 username level = ?
 unix passwd sync = yes/no

and for trouble shooting
 log level = 10
 debug = 10
 log file = /var/log/samba/%m.log
 max log size = 5

The above parameters are used for encrypted passwds, you may not use all
of them depending on your desires.

To verify use of unencrypted or encrytped passwords by the client,
ensure you have a log file of reach machine.  Set the /etc/smb.conf
GLOBAl parameter debug = 10, attempt to use the share or login to the
domain.  Inspect the log file for the supplied client username, right
infront of it is the password that was passed by the client.  Can you
read this word just as if you had of typed it on the client, if yes, the
client is using unencrypted paswords.  If it looks like garble, then
encrypted passwords or being used.  

If encrypted passwords are being used by the client you can do 1 of 2
things.  Aplly the PlainTextPasswords to the Win registry

or 

enable encrypted passwords on the samba shares.  Apply the above global
parameters, read the manual of course, check and become familiar with
the log file of each client.

here is the format for the following files.

if you are using a client name and you wish it to be mapped to a
different username on the linux machine, then you must have a
/etc/smbusers file

unixname = smbname smbname smbname
  the smbname can be one name or many

example of samba users

admin = bill administrator admin supervisor 
nobody = guest pcguest anonymous
user1 = jack jill bobby
user2 = ray nathan robert sam

the names on the left or UNIX names, names of users on the LINUX
machine, while the names on the right are the names of the client users.

UNIX uid of the above example:
admin 100
user1 501
user2 502

/etc/smbpasswd

unixname:uid:32 X's:32 X's:user identifier:user shell

admin:100:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:SysGod:/bin/bash
user1:501:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:jackJillBobby:/bin/bash
user2:502:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:RayNathanRobertSam/bin/bash
user3:503:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:NO
PASSWORDXXXXXXXXXXXXXXXXXXXXX:anotheruser:/bin/bash

The username and UID MUST match that of the /etc/passwd file!

Then issue the command smbpasswd admin and for each user.  This will
generate a password hash on the right side of the above example.  Do
this for each user.  Now if you wish then to use no passwords, then in
the right side use NO

Bill attempts to login using the client, the request is then sent ot the
smb server, if domain logins apply, then a domain login will be
attempted, if domain logins are used or not, the steps are as follows,

client name is checked again the /etc/passwd file, if found, then the
/etc/smbpasswd file is checked for a translation of the client passwd to
be verified, then the unix passwd hash is used to pass to the linux
passwd file.  Now if the client name WAS NOT found, the the
/etc/smbusers file is check to see if a client name is translated to a
UNIX name, if not, then the connect aborts and closes.  Now if there is
a client name to UNIX name mapping, then the unix name is looked up in
the /etc/paswd file, the uid is then checked and verified, if good, it
will then do a password hash check, if this is good, then the user is
allowed access to the samba shares as a NON-GUEST.  Now if you have
[global] smb.conf   guest = yes, and the unknown client name will be
named to the default guest name of nobody unless specified directly.

Now remember the above will definitely get you up to speed in using
encrypted passwords. READ the log files, they contain valuable info when
things are not working correctly. The examples shipped with each distro
do not allow really quick setup of samba services.  It really depends on
what you want to do.  The services is highly flexibile, so the
possibilities of providing a great working smb.conf file without knowing
the specifications is almost pointless.  However, the more time you
spend debugging problems, will serve you well in the future should
problems arise.  Then it is so simple. Experience..  Once setup
properly, smb services will reward you with a fine seamless file and
printing experience for all.


Good luck,

Bill...

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

From: DanH <[EMAIL PROTECTED]>
Subject: Re: how to set up a bridge between 2 networks?
Date: Fri, 17 Sep 1999 19:22:09 -0400

[EMAIL PROTECTED] wrote:
> 
> my linux is between 2 windows networks. i want to set up my linux as a
> bridge. how am i going to do this?

It's called a router.  

Put two nics into the box, make sure they both work, on the subnet
they're supposed to be connected to, that you have a default route set
up and make sure you have ipforwarding turned on.  If you want to use it
ONLY as a router, recompile the kernel for 'optimize as router, not
host'.

Turn off ALL services (possibly except sendmail for messages) and if
you're using it as a firewall too (or it's your first box inside your
home/office) then check out ipchains and ipmasquerading.

Dan
-- 
UNIX - Not just for vestal virgins anymore
Linux - Choice of a GNU generation

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

From: "BT Internet News Server" <[EMAIL PROTECTED]>
Subject: linux+win98
Date: Sat, 18 Sep 1999 01:04:18 +0100

hi all

i've got two machines, ones win98 and the others linux (rh6) with static
ips, no dns or dhcp.. i can't get the linux mahcine to appear in the windows
network neighbourhood and can't get samba to connect to the 98 machine.. any
ideas?

thanks paul



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

From: Bernd Eckenfels <[EMAIL PROTECTED]>
Subject: Re: IP Forwarding based on hostname
Date: 18 Sep 1999 01:20:12 GMT

Steve Cowles <[EMAIL PROTECTED]> wrote:
> instead of "ipmasqadm mfw". If I understand your post correctly, you have two ip 
>addresses
> bound to your external interface along with two internal web servers.

It looks more like it is one ip with 2 hosts. This can be handled by
Web-Servers when they look at the "Host:" header. This Header can be
analysed (togeher with the URL). MS Proxy for example has this reverse proxy
feature. It is nothing you will usually do in kernel space.. unless you have
some inspect or LinuxDirector Engine doing it.

Greetings
Bernd

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

From: Robi <[EMAIL PROTECTED]>
Subject: How to roll a kernel for debian?
Date: Fri, 17 Sep 1999 17:08:51 +0200

Hi I just want  to ask, ho to roll a kernel for my shiny new debian
system.

thanks


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


** 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
******************************

Reply via email to