Linux-Networking Digest #170, Volume #12 Tue, 10 Aug 99 05:13:47 EDT
Contents:
Re: Bridge using Linux (Vidar Andresen)
Problems w/ mini LAN... ("Srinivas Rao")
Re: How to configure two 3c509 n (Vidar Andresen)
Re: POP3 server for Red Hat 6.0 ? ([EMAIL PROTECTED])
Re: Three ethernet cards, one no (Vidar Andresen)
Re: PPP connection made but can't even ping peer by address ("Andrew Taylor")
Samba Shares ("MW")
Re: [HELP] [RH6.0] PnP Ne2000 (Matt Cole)
Re: HWAddress -> IP address ("Almer. S. Tigelaar.")
Cobalt Qube 2 Windows file sharing partial failure -- FIXED! (actually workaround)
(Lucius Chiaraviglio)
Please help me! (AMir Saradzic)
Re: Cross-over cable? (Jeffery Browning)
accessing mars-nwe using NETX (Kiyu Gabriel)
Re: Converting an NT server to Redhat 6.0 (F. Tolar)
Re: need telnet client for NT (Rod Roark)
PPTP or IPSec Liunx VPN (Willis Sarka III)
Re: Please help me! (Colin Watson)
----------------------------------------------------------------------------
From: [EMAIL PROTECTED] (Vidar Andresen)
Subject: Re: Bridge using Linux
Date: Tue, 10 Aug 1999 06:36:31 GMT
In article <[EMAIL PROTECTED]>,
Graeme Woollett <[EMAIL PROTECTED]> wrote:
>I'm trying to get a ethernet bridge going using two NE2000 clones &
>RH6.0. I followed the Bridge HOWTO instructions concerning copying the
>loop back network scripts to ifcfg-eth0 & eth1 to get rid of allocated
>IP addresses. I then ran BRCFG -ena to start the bridge, it seemed to
>be happy:
Dont know, dont run 2.2.* kernel. But.
http://support.broadjump.com/cerberus/ is a bridge rewritten for 2.2.*
I belive. Got some info.
There is two older versions of bridge out there, they both have a
script 'bridge' which is to be placed in '/etc/rc.d/init.d/' and to be
called as '/etc/rc.d/init.d/bridge start' or '/etc/rc.d/init.d/bridge
stop'
(that is where I place it, the script says different, assumes
./init.d/ straight on /etc/) Goes like this on the newest version of
the two old versions... for 2.0.*.. :
#! /bin/sh
# /etc/init.d/bridge: Start or Stop bridge operation
# This is a script for Debian style management of the bridge
# It will also work with any other distribution on its own.
test -x /sbin/brcfg || exit 0
# Here all interfaces to be bridged should be listed
INTERFACES="eth1 eth0"
case "$1" in
start)
for i in $INTERFACES; do ifconfig $i up promisc; done
brcfg start
# Use the following to just bridge strange protocols. Use the more
# efficient routing for localtalk and tcp/ip traffic
# brcfg start exempt 802_3 802_2 ip arp
;;
stop)
brcfg stop
for i in $INTERFACES; do ifconfig $i -promisc; done
;;
*)
echo "Usage: /etc/init.d/bridge {start|stop}"
exit 1
esac
exit 0
So. What it does is first checking for '/sbin/brcfg' and then (if
found) either put out 'Usage: /etc/init.d/bridge {start|stop}' or if
the bridge is started correct via the script, it does either start or
stop the bridge. This meaning you dont have to mess with 'BRCFG -ena',
its taken care of.
If the script you got is like this:
#! /bin/sh
# /etc/init.d/bridge: Start or Stop bridge operation
# This is a script for Debian style management of the bridge
# It will also work with any other distribution on its own.
test -x /usr/sbin/brcfg || exit 0
# Here all interfaces to be bridged should be listed
INTERFACES="eth1 eth0"
case "$1" in
start)
for i in $INTERFACES; do ifconfig $i up promisc; done
brcfg -enable
;;
stop)
brcfg -disable
for i in $INTERFACES; do ifconfig $i -promisc; done
;;
*)
echo "Usage: /etc/init.d/bridge {start|stop}"
exit 1
esac
exit 0
Then you got the very first version of the bridge. Works ok to. But
without the opportunity to filter like
'brcfg start exempt 802_3 802_2 ip arp'
The line
'INTERFACES="eth1 eth0"'
decide wich interface is first and second (and third and ..)
activated. I let the interface I want to talk to be activated last.
The line above lets eth0 be activated last, and i can use that without
any tweaking.
If I want to talk to or have contact to the bridge itself (from the
first card activated) it either need routing or an 'ifup eth1' if i
want to have contact to the eth1 side. (Or 'ifup eth0' if eth1 is the
last activated by the bridge.)
>ifconfig eth0 returned
>
>eth0 Link encap:Ethernet HWaddr 00:80:AD:70:3C:4B
> inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0
> UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
> RX packets:2 errors:0 dropped:0 overruns:0 frame:0
> TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> Interrupt:10 Base address:0x320
>
>ifconfig eth1 returned
>
>eth1 Link encap:Ethernet HWaddr 00:80:AD:70:3C:3C
> inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0
> UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
> RX packets:5432 errors:0 dropped:0 overruns:0 frame:22
> TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> Interrupt:11 Base address:0x340
>
>Running tcpdump -i eth* gave the expected traffic on each side of the
>bridge, but nothing that's surposed to get though it does.
>Copying the lo configuration file does in fact give each ethernet card
>an IP address of 127.0.0.1 etc. But if you remove this from the
>ifcfg-eth* files the BRCFG program fails to work.
I would have deleted those two files..
I dont remember what the howto suggested. But I think it is better to
give both interfaces a real ip-adress (or a bogus, but valid, like
10.0.0.1 and 10.0.0.2). As long as this is in a privat network, (is
it?) give them something. If you like to be abel to talk to the
bridge from other machines, that is. (But the side you can use
depends on the last interface activated or routing on the bridge)
That mean to set up the machine normally with two nic's, give it
ip-adresses (dont think dhcp will work on both sides, if that is in
use).
That produce two valid ifcfg-eth* files, (maybe even with routing? not
neccesary, but if you want to contact the bridge itself, it can be
nice. Dont export route, I think.)
Get the nic's activated and up and running with ip-adresses.
And then start the bridge.
That work on 2.0.* kernels.
Mvh Vidar Andresen
------------------------------
From: "Srinivas Rao" <[EMAIL PROTECTED]>
Crossposted-To: linux.appletalk
Subject: Problems w/ mini LAN...
Date: Mon, 9 Aug 1999 10:49:57 -0400
Hey Folks!
First a little background:
Linux: SuSE Linux 6.1 w/ a 2.2.7 kernel (compiled w/ PNP support, support
for NIC, TCPIP, IP masq, Netatalk, PPP, SLIP, etc.)
NIC: 3Com Etherlink III (3c509) PNP on ISA bus (io address=0x300, IRQ=10)
CPU: K6/2 350MHZ
MB: Soyo 5EHM
This PC is networked to my G3 mac and HP LJ 4m via a standard 5-port hub.
About two weeks ago, I successfully configured linux for both appletalk and
IP masquerading w/ PPP. My mac had no problems mounting linux partitions or
accessing the web with the linux box acting as a router to my PPP
connection. On my local network, my Mac had an IP address of 192.168.0.1
and linux used 192.168.0.99. However, several days ago, I flash upgraded my
PC's bios. Immediately, I had some problems under win98 accessing my serial
ports; this turned out to be due to some configuration issues in my bios,
which I subsequently resolved. However, at this point, both Netatalk and IP
masq stopped working under linux! Ifconfig does not note any errors w/
eth0. While atalkd is coming up, the "Act/Rc" LED on my hub flash
appropriately, but then I cannot see any appletalk devices on my hub.
However, the problem is not limited to appletalk; I can no longer
ping/telnet/ftp my Linux box from my mac. I then ran Netpresenz on my Mac
and tried ftp'ing to the Mac from linux. Ftp failed w/ "cannot find route
to host."
So here's what I tried:
-confirmed that everything still worked w/ my mac connecting to win98, which
it did.
-downgraded bios to original state -> no changes in the problems
-I thought that maybe there was an irq/io address conflict. So I made a new
kernal w/o PNP or built-in support for my NIC, and then used pnpdump -c to
make an isapnp.conf file. This looked fine, and so I booted w/ isapnp. The
adapter appears to initialize okay, but still no networking. So then I
tried different io addresses and irqs w/o any luck.
-made a new atalk.conf file w/ just "eth0" as an entry. Atalkd reconfigured
w/o a problem, but still no connectivity.
-played w/ route. I tried "route add -host 192.168.0.1 dev eth0". The
routing table was updated, but still no luck. So I tried playing with
route.conf, again unsuccessfully.
-verified my /etc/hosts, /etc/networks files, which all seem fine
-looked at a bunch of faqs/how to's/mini how to's re: netatalk, networking,
ethernet, etc -> no dice
It's almost as though linux box is not responding to any input coming in
from eth0. At this point, I'm out of ideas, short of the standard
MacOS/win95/98/NT step of reinstalling the system.
Sorry for the long post, but any help would be *greatly* appreciated!
--Srinivas Rao
------------------------------
From: [EMAIL PROTECTED] (Vidar Andresen)
Subject: Re: How to configure two 3c509 n
Date: Tue, 10 Aug 1999 06:36:29 GMT
In article <[EMAIL PROTECTED]>,
QuestionExchange <[EMAIL PROTECTED]> wrote:
>> I have two ISA 3c509 ethernet cards. I used dos program to set
>> their io and irq to 210,5 and 300,10. How to edit my
>> conf.modules to make them work on my linux box? Thanks.
>
> SEND ONLY ANSWERS ENDORIGINAL Body IS: If your using
>kernel 2.2.5 or later it should be relatively automatic,
>however, make sure you disable pnp bios (As this causes
It can be a good thing to disable 'boot with pnp-os' in the _machines_
bios.
But. The 3com 509b card's have pnp turned on on them, that is a option
wich can be turned off in the cards EEPROM with a setup-util from
3com. Normally follows the card on a floppy, a 3c5x9cfg.exe. But
that floppy, setup-util can also be downloaded from 3com.
That have to be done to the nic, not to the machine bios, which is a
different matter. But it can also help to set the irq chosen for the
nic to be a 'legacy isa' or 'isa only' irq in the machine-bios.
>problems with the 3c509 drivers) And make sure 3com drivers
>are installed as either a module or as a kernel based
>installation. It is not default, so you will need to reinstall
>your kernel. If your dual booting, make sure its a cold boot
I belive the 3c509 module is very default. No need to do any
reinstall. And as long as the 3com 509b card's have pnp turned off
with the 3com-setup util, there should be no cold/warm boot issue.
You might confuse the 3com 509 nic with the 3com 905 nic. And then
your advice make sense.
>into linux, and lastly, the nicest tool for configuring
>interfaces is netcfg for XWindows. It should be available in
>most distributions, and it will help guide you through system
>configurations for the network cards.
Linuxconf is normally a better choice, I belive, a updated version
dont harm, the GUI is getting more 'IGUI', that is 'Intuitiv Graphical
User Interface' or something... Well.
(Some people hate things like linuxconf, i kind of understand, but
everyone wont work on the bare metal.)
Mvh Vidar Andresen
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: POP3 server for Red Hat 6.0 ?
Date: Tue, 10 Aug 1999 06:28:20 GMT
Hello "bigboss"
for the pop3 you need to install:
imap-4.5-3.i386.rpm
This includes both the IMAP and POP3 services.
Cheers
JD
In article
<[EMAIL PROTECTED]
uk>,
"Bigboss" <[EMAIL PROTECTED]> wrote:
> Hello
>
> I like to install POP3 server for linux, and I
have Red Hat 6.0, can anyone
> tell me which RPMs it live int. The "inted.conf"
file say its "ipop3d".
>
> Thanks.
>
>
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
------------------------------
From: [EMAIL PROTECTED] (Vidar Andresen)
Subject: Re: Three ethernet cards, one no
Date: Tue, 10 Aug 1999 06:36:28 GMT
In article <[EMAIL PROTECTED]>,
Question Exchange, Inc. <[EMAIL PROTECTED]> wrote:
>Ensure your /etc/conf.modules has a set of lines resembling
>
>
>alias eth0 3c509
>alias eth1 3c509
>alias eth2 3c509
>options 3c509 io=0x350,0x330,0x640
>
>where the 0x350,0x330,and 0x640 are your respective IO addresses.
>
>if those dont work, we can try forcing this like so:
>
>alias eth0 3c509-1
>alias eth1 3c509-2
>alias eth2 3c509-3
>options 3c509-1 io=0x350 irq=7
>options 3c509-2 io=0x330 irq=8
>options 3c509-3 io=0x640 irq=9
I belive the 3c509 module dont need the 'io=*' value passed. But it
does need the 'irq=*' value. Something like this (assuming irq-values
of 10, 11 and 12) would be better, I think:
alias eth0 3c509
alias eth1 3c509
alias eth2 3c509
options 3c509 irq=10,11,12
Mvh Vidar Andresen
------------------------------
From: "Andrew Taylor" <[EMAIL PROTECTED]>
Subject: Re: PPP connection made but can't even ping peer by address
Date: Tue, 10 Aug 1999 07:59:45 +0100
What rules have you got set up in ipchains ? ipchains -L
Andy
Philip Payne wrote in message <[EMAIL PROTECTED]>...
>Hi,
>
>I'm running Caldera OpenLinux 2.2. I've just converted to an ISDN
>telephone connection and an ISDN modem and have spent a frustratingly
>large amount of time failing to solve the following problem.
>
>I can make a PPP connection to my ISP but I can't even ping the remote
>IP address he sends me, let alone go somewhere else on the Internet.
>This happens both using kppp and when configuring pppd manually.
>
>Here is a tail on /var/log/messages:
>
> Aug 9 23:20:03 dellxps300 pppd[3413]: Serial connection established.
> Aug 9 23:20:04 dellxps300 pppd[3413]: Using interface ppp0
> Aug 9 23:20:04 dellxps300 pppd[3413]: Connect: ppp0 <--> /dev/ttyS0
> Aug 9 23:20:05 dellxps300 pppd[3413]: Remote message:
> Aug 9 23:20:05 dellxps300 pppd[3413]: local IP address 195.24.90.210
> Aug 9 23:20:05 dellxps300 pppd[3413]: remote IP address 172.29.1.104
>
>The output from route is then:
>
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref
>Use Iface
> 172.29.1.104 * 255.255.255.255 UH 0 0
>0 ppp0
> 127.0.0.0 * 255.0.0.0 U 0 0
>0 lo
> default 172.29.1.104 0.0.0.0 UG 0 0
>0 ppp0
>
>When I do 'ping 172.29.1.104' then I see the transmit and receive lights
>on the modem flashing (and I see the bytes in and out ticking over if I
>use 'kppp') but ping fails to get/recognize any reply.
>
>ifconfig then shows:
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:3924 Metric:1
> RX packets:573 errors:0 dropped:0 overruns:0 frame:0
> TX packets:573 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
>
> ppp0 Link encap:Point-to-Point Protocol
> inet addr:195.24.90.210 P-t-P:172.29.1.104
>Mask:255.255.255.255
> UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1524 Metric:1
> RX packets:11 errors:9 dropped:0 overruns:0 frame:9
> TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:10
>
>which seems to show that all the receive packets were in error. But what
>does the 'frame:' count mean????
>
>The problem is definitely with my Linux setup, because from Windows NT I
>can connect to both my ISP's using this ISDN modem. Also, I was able to
>connect to them from Linux using my old analog modem before I changed to
>ISDN.
>
>Does anyone have any idea what might be wrong here???????
>
>Regards,
>Philip Payne ([EMAIL PROTECTED])
>
------------------------------
From: "MW" <[EMAIL PROTECTED]>
Subject: Samba Shares
Date: Tue, 10 Aug 1999 09:19:15 +0100
Reply-To: "MW" <[EMAIL PROTECTED]>
I've configured my samba (well, i hope)..but one thing doesn't work:
i use win95 and suse 6.?, i have 4 partitions: one win-boot, one linux-boot
and two data (FAT16)...and i want to public this two data drives in my LAN
(little area network)...it works, but only the user who mounted them has
write access and i don't need 8 GB of data only to look on...
i've found no doc on this problem, but maybe anybody knows...
MW
------------------------------
From: Matt Cole <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.help,comp.os.linux.hardware
Subject: Re: [HELP] [RH6.0] PnP Ne2000
Date: Tue, 10 Aug 1999 02:56:41 -0500
I have a similar card (PnP NE2000). The kernel claimed to see it when it
booted up, but ifconfig couldn't configure it. Let me know if you find
anything out.
Jean-Baptiste Queru wrote:
> I've installed a Redhat 6.0 over the network (ftp from redhat's site),
> and the install program would not find the NIC in my machine (PnP Ne2k).
>
> I had to borrow a card from another machine (non-PnP Ne2k), and
> installing
> went rather fine.
>
> I'd like to switch back to my usual card (the PnP one). I have no idea
> how to get it to work.
> My BIOS tells me it's configured on IRQ 10, my other OS (BeOS) uses it
> on IRQ 3, port 0x240. How can I know how it is configured under linux,
> and in which network config file do I have to report this config?
>
> Please be aware that I haven't used any version of linux for the last
> 18 months, and that my previous install was a slackware 3.5 (IIRC) with
> a monolithic kernel 2.0.x. I also don't have X really running yet
> (it's only doing 320x200)
>
> Thanks for answering by e-mail.
--
"So Lone Starr, now you see that evil will always triumph, because good is
dumb."
-- Dark Helmet (Rick Moranis), "Spaceballs"
------------------------------
From: "Almer. S. Tigelaar." <almer-t@!SPAMbigfoot.com>
Subject: Re: HWAddress -> IP address
Date: Tue, 10 Aug 1999 10:16:02 +0200
>> Since the user is apparantly not in my ARP cache it appears that I have
to
>> find some
>> utility that makes a request shouting : 'who has this MAC address', over
the
>> entire network.
>
> Um, you could force a ping packet to the ip address and inspect the arp
cache
> then??
How? I only have the MAC address.....
(I need the IP address)
Yours,
Almer. S. Tigelaar.
almer-t@!NOSPAMbigfoot.com
(remove !NOSPAM to reply)
------------------------------
From: [EMAIL PROTECTED] (Lucius Chiaraviglio)
Crossposted-To: comp.os.ms-windows.nt.admin.networking,comp.protocols.smb
Subject: Cobalt Qube 2 Windows file sharing partial failure -- FIXED! (actually
workaround)
Reply-To: [EMAIL PROTECTED]
Date: Tue, 10 Aug 1999 07:21:53 GMT
I won't bore you all by reposting the details of the problem,
but to summarize, I found out earlier that some accounts on the Cobalt
Qube 2's (we have 2, on in each of 2 offices) cannot log into their
shared file folders using Windows file sharing. The chance
distribution of this problem had led me to believe that it was
specific to one office (San Luis Obispo, CA), but that is not the
case. The symptom, in brief, is that the user gets an "Incorrect user
name or password" error message upon double-clicking on the Qube under
Network Neighborhood, even after typing in the user name and password
correctly. This had the Cobalt Networks tech support people stumped.
By accident, I found that the real reason for this is that the
Cobalt Qube 2 main password (for unix logon and accessing your
personal profile and web pages) and Windows file sharing (Samba)
password are stored separately, and the synchronization between
changes to these passwords is not completely reliable. The workaround
is to go the "public site" of the Qube (http://yourQubeName/cobalt/ --
note that you need the last slash or it won't work) and then choose
"Personal Profile" (you will need to log in with your user name and
password either initially or at this point) and change your password
from there (you can even change it to the same password it already
is). This will usually synchronize the passwords properly -- if
it doesn't, try again until it does.
Lucius Chiaraviglio | [EMAIL PROTECTED]
========
To reply to this message, remove the "not at" characters from in front of the
abbreviation of the company name (Advanced CMP Products, Inc.). If you are
seeing this in an e-mail message, it is because I am posting it and e-mailing
it at the same time -- normal e-mail messages from me do not have this feature.
Note: I am trying a new news server -- it seems to work well, but it has a
very short expiration time (1 week for most groups), so I will likely miss your
reply unless you send it by e-mail in addition to posting it.
------------------------------
From: AMir Saradzic <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup,redhat.config
Subject: Please help me!
Date: Tue, 10 Aug 1999 07:30:42 GMT
I bought Linux-Mandrake 6.0. Which comes with 3 cd-disks a floppy disk and
User guide.
I have 4.3 Gb hard disk with two particion (FAT 16)on it. On the first one
I have installed Windows 95 and second particion is not formated at all.
When I boot my system with Linux Boot disk and when I get to the point to
choose particion I get lost! It ask me to enter MOUNT POINT for choosen
particion and in the manual and on the Internet I could not find anything
about MOUNT POINT?? I can't believe, because this looks big problem for me
and I am preaty sure many people get stuck at this point. Please help me to
solve this problem. I can't wait to start using Linux.
Thank you very much, I am looking forward on your coperation.
================== Posted via CNET Linux Help ==================
http://www.searchlinux.com
------------------------------
From: Jeffery Browning <[EMAIL PROTECTED]>
Subject: Re: Cross-over cable?
Date: Mon, 09 Aug 1999 07:51:13 -0400
WT Tang wrote:
>
> How do I know whether a UTP cable is a cross-over cable or not? Is it by
> holding the two end of the RJ45 connectors and comparing the sequence of
> the colored wires? If the sequences are the same, does it mean that it
> is not a cross-over cable?
If the two ends are the same it isn't a cross-over cable. If pins 1 and
3, and pins 2 and 6 are opposite then it is a cross-over cable. That is
viewing the ends with the clip down.
--
Jeffery C. Browning, Enhanced Solutions
Computing
Systems Administrator 2251 Old Cornelia Hwy
Gainesville, Ga 30507
------------------------------
From: Kiyu Gabriel <[EMAIL PROTECTED]>
Subject: accessing mars-nwe using NETX
Date: Tue, 10 Aug 1999 01:47:31 -0500
Hello-
I am running mars-nwe under RH6 and can't get access from clients
running the NETX shell. Access from the same workstations using the
client32 shell work fine. Here is my startnet.bat. and net.cfg - I am
using an ne2000 compatible - any suggestions?
startnet
SET NWLANGUAGE=3DEnglish
lsl.com
n2000.com
ipxodi.com
netx.exe
net.cfg
Link Drive N2000
INT 3 (it really is on IRQ3)
PORT 300 (and really on 300)
FRAME Ethernet_II (I am running Ethernet II on the server)
Netware DOS Requester
FIRST NETWORK DRIVE =3D F
NETWARE PROTOCOL BIND
Protocol IPX
IPX SOCKETS 40
Any suggestions are greatly appreciated!
--
YBIC,
Kiyu Gabriel
============================================
=93Every day millions of people wish for immortality who
don't know what to do with themselves on a Sunday afternoon.=94 ;-)
------------------------------
From: [EMAIL PROTECTED] (F. Tolar)
Crossposted-To: comp.os.linux.setup
Subject: Re: Converting an NT server to Redhat 6.0
Date: Tue, 10 Aug 1999 03:46:43 -0400
Reply-To: [EMAIL PROTECTED]
On Sun, 08 Aug 1999 13:10:48 +0100, Piet Schipper <[EMAIL PROTECTED]> wrote:
>Hi Chris
>
>> The windows 9x machines login to the
>> server, making sure only the right people con login. I have it using
>> microsoft networking with the NT maching as a Domain Controller. All the 9x
>> machine users must then have their login verified by the domain server to
>> access windows. If I put redhat 6 on that computer, can I do anything
>> similar to restrict access on the 9x machines
>
>I assume that you will be using samba for sharing drives and printers.
>You can still have the verification done by the domain controller.
>In your /etc/smb.conf file, set:
>
>security = domain
>password server = <NT-Server-Name>
>
>
>Good luck,
>
>Piet
I think he wants to "replace" his NT server with a samba server, doing the
same things. (Login validation, etc.)
I assume this is possible, but I haven't actually done it, yet. Right now,
I use samba to share directories of this workstation with the NT server and
a pair of Win95 workstations.
--
Floyd L.Tolar
[EMAIL PROTECTED]
"When the going gets tough,
the tough change the Rules."
[Ferengi 78th. Rule of Aquisition]
------------------------------
From: Rod Roark <[EMAIL PROTECTED]>
Subject: Re: need telnet client for NT
Date: 9 Aug 1999 16:18:23 GMT
Gerald Krause <[EMAIL PROTECTED]> wrote:
>can someone tell me where i can find some fine
>telnet client for Windows NT? in my opinion
>the original is very #~?"=\`*� :)
I know what you mean. Try NetTerm.
-- Rod
======================================================================
Sunset Systems Preconfigured Linux Computers
http://www.sunsetsystems.com/ and Custom Software
======================================================================
------------------------------
From: [EMAIL PROTECTED] (Willis Sarka III)
Subject: PPTP or IPSec Liunx VPN
Date: 10 Aug 1999 07:58:45 GMT
Greetings,
I am aware of PoPToP PPTP server for Linux, but am unaware of any IPSec server.
Is there any info out there of an IPSec server for Virtual Private Networking? The
reason I ask is because more and more of the employees at work are signing up for
ADSL, and would like to access our LAN over the Internet. Any pointers to web pages
or docs is much appreciated!
Thanks in advance,
------------------------------
From: [EMAIL PROTECTED] (Colin Watson)
Crossposted-To: comp.os.linux.setup,redhat.config
Subject: Re: Please help me!
Date: 10 Aug 1999 09:33:20 +0100
In article <[EMAIL PROTECTED]>,
AMir Saradzic <[EMAIL PROTECTED]> wrote:
>I bought Linux-Mandrake 6.0. Which comes with 3 cd-disks a floppy
>disk and User guide.
>I have 4.3 Gb hard disk with two particion (FAT 16)on it. On the
>first one I have installed Windows 95 and second particion is not
>formated at all. When I boot my system with Linux Boot disk and when
>I get to the point to choose particion I get lost! It ask me to enter
>MOUNT POINT for choosen particion and in the manual and on the
>Internet I could not find anything about MOUNT POINT??
I'm amazed the manual said nothing about this (if it didn't, it's very
badly broken - it may be referred to by a different name), but still:
A mount point is a directory on which a filesystem is logically
located. In Windows terms, the mount points are "A:", "B:", "C:", etc.
In Linux, all accessible files and directories are under one tree,
rooted at "/". Additional filesystems can be "grafted" onto this tree
at various points: for instance, it's common to have a separate
partition for personal data files mounted at /home, or to mount
Windows partitions on /mnt/c, /mnt/d, etc. None of these extra
partitions are necessary, but you definitely need a / partition
otherwise nothing will work.
So, when you're asked for a mount point, choose "/" (without the
quotes, obviously). You'll also need a separate partition (say, 64 to
128 Mb) for swap space to use as virtual memory; the mount point for
this is "swap" - there's no leading "/" since it isn't really part of
your filesystem. Any other partitions you want to create should have a
leading "/", such as "/home", "/usr", "/var", and so on - but, if you
don't really understand this, I'd stick with just / and swap
partitions for the time being.
HTH,
--
Colin Watson [cjw44 at cam.ac.uk]
Trinity College, Cambridge, and Computer Science [riva.ucam.org]
"Then hast thou joined the ARPANET? / Oh come to me, my bankrupt boy!
Quick, call the NIC! Send RFCs! / He chortled in his joy." - RFC 527
------------------------------
** 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
******************************
