Linux-Networking Digest #281, Volume #10 Mon, 22 Feb 99 08:13:29 EST
Contents:
Weird behaviour on ethernet network (Stuart Ballard)
Re: Samba as domain login server ("Jeff")
Re: LDAP...POP3 (Stefan Nehlsen)
Re: pppd REJ's prot c029, should NAK it (Phil Howard)
Delayed packet in network (Nguyen Tuan Hung)
Re: Win98->Linux semi-newbie ("Jeff")
Re: Win98->Linux semi-newbie ("Thomas S. Martinson")
Re: Win98->Linux semi-newbie ("Jeff")
Re: Diald disconnects after packets stop (Mike Jagdis)
Machine name themes - what do you use? (Stuart Summerville)
Re: Machine name themes - what do you use? (Merton Campbell Crockett)
Re: 3com 3c509 ISA card problem with 2.2.1 ("NewsOO")
----------------------------------------------------------------------------
From: Stuart Ballard <[EMAIL PROTECTED]>
Subject: Weird behaviour on ethernet network
Date: Sun, 21 Feb 1999 04:42:50 +0000
I'm attempting to set up a simple 2-node BNC ethernet network between a
laptop with credit card ethernet and a desktop computer. Both computers
are running stock Red Hat Linux 5.1, no kernel recompiles or anything.
I've tried replacing the network card on the desktop machine and the
cable, and neither makes any difference. Both network cards (and the
credit card network card) have worked well in the past. So have the
cables. Basically, I'm pretty sure it isn't a hardware problem.
The behaviour I'm seeing is as follows - on the desktop machine:
"ping laptop" gives no response
"ifconfig" after doing that shows that eth0 still has 0 TX and RX
packets, but the TX packets on lo did increase by the number of ping
packets sent.
on the laptop:
"ping desktop" gives no response
"ifconfig" after doing that shows the expected behaviour, ie, the ping
packets went to eth0.
When I pinged it from the desktop, *some* RX and TX packets showed up on
the eth0 interface, but not as many as were sent by the ping.
I've looked over and over the configuration to try to figure out what's
different between the laptop and the desktop. I've got the same setup
working before with no problems. I've had other people who know what
they're doing look over it and they can't explain it either. The
netmasks, routes, etc, all appear to be correct. Whatever it is seems to
not be an "obvious" problem (touch wood).
Oh, one other thing that might give a clue - I looked in /proc/net/route
and it showed what I expected, a line for eth0 and a line for lo, with
the expected IP addresses on each. But /proc/net/rt_cache showed the
same two lines... but this time both of them were "lo" and eth0 was
nowhere to be seen.
I'm tearing my hair out here - please help if you have any ideas! Thank
you in advance,
Stuart.
------------------------------
From: "Jeff" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Re: Samba as domain login server
Date: Mon, 22 Feb 1999 05:46:33 -0500
Just a guess but as far as I know in your client for microsoft windows
properties
you should take the check mark out of Log into NT server. Just have it log
in and reestablish the connections. IE remove the check mark from the top
box, and make sure the last option has a black dot in it.
works for me.
Jeff
Juergen Fiedler wrote in message <7aqm6j$f2t$[EMAIL PROTECTED]>...
>
>Hi,
>
>I have the weirdest problem with Samba and Win95:
>We have one Linux Server that runs Samba 2.0.2 and three Win95 machines.
>I set Samba up to act as a domain login server. The general section of
>smb.conf looks like this:
>
>>-------SNIP-------<
>
># Global parameters
> workgroup = NANOSOFT
> domain logons = Yes
> os level = 33
> preferred master = Yes
> domain master = Yes
> local master = Yes
> guest account = guest
> update passwords = Yes
>
>>-------SNIP-------<
>
>Now, I set the Win95 machines up to connect to the Samba server. The first
>one (actually Win98) was easy: I set the 'Client for Microsoft Networks' to
>connect to NT domain NANOSOFT and set the access control to user-level,
>with NANOSOFT as the source for the list of users and groups. Everything
>worked fine.
>Then, I set up the next machine (an HP Pavilion - ack!). When I set the
>access control, it said it couldn't find the domain NANOSOFT. I insisted
>and told it that it was an NT domain (as opposed to an NT server). After
>that, it worked: The HP can now connect to the Linux server.
>But then came the last computer - a Compaq Armada 6500 with Win95. It also
>told me that it couldn't find NANOSOFT. I also insisted - but this time,
>it didn't work. When I try to log in to this computer, it tells me that
>the login server couldn't be found and that some network resources might
>not be accessible. And indeed, I can see the two other Win95 machines,
>but not the Linux box - and of course I can't browse the Windows machines
>for lack of a login server.
>
>Does anybody know what I did wrong here?
>
>TIA,
>Juergen
------------------------------
From: [EMAIL PROTECTED] (Stefan Nehlsen)
Subject: Re: LDAP...POP3
Date: 22 Feb 1999 10:50:07 GMT
In <[EMAIL PROTECTED]> Chris Cocozzo <[EMAIL PROTECTED]>
writes:
>hello all,
>2 questions:
>1. Is there a LDAP server for RH5.1?
Have a look at http://www.OpenLDAP.org/ and http://www.rage.net/ldap/ .
>2. Is it possible to have some sort of POP3 server without making user
>accounts on the box running POP3?
If there is a pop daemon that is able to use pam it should be easy.
cu, Stefan
--
Stefan Nehlsen Email: [EMAIL PROTECTED]
Rechnerbetriebsgruppe Tel.: +49-431-77572-106 FAX: -103
Technische Fakultaet der Christian-Albrechts-Universitaet zu Kiel
------------------------------
From: [EMAIL PROTECTED] (Phil Howard)
Subject: Re: pppd REJ's prot c029, should NAK it
Date: Sun, 21 Feb 1999 05:11:12 GMT
| I need to pay more attention to logs. I don't know what's going on
| here although it's not likely a CBCP problem. I added some comments
| below - it's strange whatever it is. BTW James Carlson frequents the
| comp.protocols.ppp newsgroup and is very good at diagnosing problems.
During the course of trying several things, including a new kernel and
lots of config changes, the problem has vanished. But I don't know why.
It's now connecting OK. I hate problems that fix themselves without an
explanation.
Ordinarily pppd uses the ethernet address as the local address, if there
is one. It was 208.152.116.20. But I noticed 208.152.116.17 going over
the negotiation. One thing I do notice when things started working was
that I had changed the default route from being 208.152.116.17 to none
(to let it be the PPP connection). So maybe pppd was picking up on the
existant default route and doing something with it that affected the PPP
negotiations. I would have thought all routing info, if any, would have
been done using a routing protocol such as RIP, OSPF, or whatever. Maybe
I'm wrong about that.
One more thing that might have affected pppd was that the packet routing
was turned off with /proc/sys/net/ipv4/ip_forward having a value of 0.
I added a line to my PPP wrapper script to set it to 1.
| Everything seems OK until this point, with the IPCP negotiations
| completed. Then the ISP starts to shut everything down. This is
| well before the CBCP request and I don't have an explanation for it.
I noticed the "Term" requests, but I wasn't sure what they mean as I
have seen them in good session startups. The semantics of a lot of
protocols are, on occaision, different than the terms used for them,
at least as I have sometimes seen.
| The only thing missing is authentication and presumably you do a chat
| scripted login/password that you just chose to omit from the lines of
| /var/log/messages you posted.
The chat log is stored in a different file. It shows the sequence of
logging in up to the password prompt, with the password not echoed, and
then nothing more. It seemed all the PPP negotiation was taking place
after that point.
--
-- *-----------------------------* Phil Howard KA9WGN * --
-- | Inturnet, Inc. | Director of Internet Services | --
-- | Business Internet Solutions | eng at intur.net | --
-- *-----------------------------* phil at intur.net * --
------------------------------
From: Nguyen Tuan Hung <[EMAIL PROTECTED]>
Crossposted-To: comp.unix.programmer,comp.protocol.tcp-ip
Subject: Delayed packet in network
Date: Mon, 22 Feb 1999 11:54:45 +0100
Hi.
I am working in network traffic project to simulate delayed packet.
The following my program run in the machine that is between the two
another machines. My program receive all packet from one of the two and
delay 1000 milli seconds and later send to another machine towards, or
inversely
static void doit(int InSock, int OutSock);
main()
{
int maxfd;
int FirstInSock, SecondInSock;
fd_set readMask;
/* Some code here
.
.
.
*/
maxfd = (FirstInSock>SecondInSock ? FirstInSock : SecondInSock);
while(1) {
bzero(&readMask,sizeof(fd_set));
if( seleect(maxfd,&readMask,NULL,NULL,NULL)<0) {
exit(1);
}
if(FD_ISSET(FirstInSock,&readMax)) {
doit(FirstInSock,SecondInSock);
}
if(FD_ISSET(SecondInSock,&readMax)) {
doit(SecondInSock,FirstInSock);
}
}
}
void doit(int InSock, int OutSock)
{
char buf[8096];
int ret;
if((ret=recvfrom(InSock,buf,8096,0,......))<0)
return;
sleep(1);
/* ??????
The problem is here. What heppens now if packet has
received on
some socket, but later I jus have time ro read it.
I think in this the case the packet has discarded by
kernel, if I don't read in time.
I have another solution. I can create two child process,
that handle packet
receiving , delaying, and sending through two pipe. In
case I have one question
if the parent writes data to pipe more than the child
can read from pipe, because
the child sleep sometimes. What heppens with data that
in pipe.
?????????????
*/
/* Some code here
.
.
.
*/
return (sendto(OutSock,buf,ret,....));
}
------------------------------
From: "Jeff" <[EMAIL PROTECTED]>
Subject: Re: Win98->Linux semi-newbie
Date: Mon, 22 Feb 1999 05:14:25 -0500
This is a multi-part message in MIME format.
=======_NextPart_000_0058_01BE5E22.36E48EC0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Ok I am as much a newbie as you are, but I do have samba and =
masquerading working. This is my suggestion.
I am assuming you can ping the machines by now..
1) cp /etc/smb.conf /root/samba <--- just in case you really get screwed =
up
2) vi /etc/smb.conf=20
3) comment out all the lines in the sample configuration
4) add these lines=20
[global]
encrypt passwords =3D True
password level =3D 8
username level =3D 8
interfaces =3D 192.168.1.1/24
netbios name =3D "your hostname"
wins support =3D True
path =3D /home/%u
this will set your linux machine up to handle the domain log ons etc
then on your windows machines
edit your /control panel/network/tcp-ip settings (preferably on the nic =
card not the dial up adapter) to enable wins resolution and to the wins =
server should be 192.168.1.1
<if your gonna use masquerade you have to add the DNS and gateway as =
well>
make sure that the primary network log on is set to=20
"Client for M$ networks"
It works wonderfully for me.
a good site I found and printed out was;
http://eunuchs.org/linux/samba/samba_content.html
if your having trouble pinging the other boxes make sure your firewall =
rules are correct.
I had that problem. if you turn off all the firewall options with these =
commands sent to me by someone here see if you have any better luck.
" ipfwadm -I -f
ipfwadm -O -f
ipfwadm -F -f
ipfwadm -I -p accept
ipfwadm -O -p accept
ipfwadm -F -p accept
That opens the firewall completely so you probably don't want to do it =
while
you're
connected to the internet (I don't know, but I don't)."
quoted from an email to me from JJ.
=======_NextPart_000_0058_01BE5E22.36E48EC0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>
<META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type>
<META content=3D'"MSHTML 4.72.3110.7"' name=3DGENERATOR>
</HEAD>
<BODY>
<DIV>Ok I am as much a newbie as you are, but I do have samba and =
masquerading=20
working. This is my suggestion.</DIV>
<DIV>I am assuming you can ping the machines by now..</DIV>
<DIV> </DIV>
<DIV>1) cp /etc/smb.conf /root/samba <--- just in case you really get =
screwed=20
up</DIV>
<DIV>2) vi /etc/smb.conf </DIV>
<DIV>3) comment out all the lines in the sample configuration</DIV>
<DIV>4) add these lines </DIV>
<DIV>[global]</DIV>
<DIV>encrypt passwords =3D True</DIV>
<DIV>password level =3D 8</DIV>
<DIV>username level =3D 8</DIV>
<DIV>interfaces =3D 192.168.1.1/24</DIV>
<DIV>netbios name =3D "your hostname"</DIV>
<DIV>wins support =3D True</DIV>
<DIV>path =3D /home/%u</DIV>
<DIV> </DIV>
<DIV>this will set your linux machine up to handle the domain log ons =
etc</DIV>
<DIV> </DIV>
<DIV>then on your windows machines</DIV>
<DIV>edit your /control panel/network/tcp-ip settings (preferably on the =
nic=20
card not the dial up adapter) to <STRONG>enable wins resolution =
</STRONG>and to=20
the wins server should be 192.168.1.1</DIV>
<DIV><if your gonna use masquerade you have to add the DNS and =
gateway as=20
well></DIV>
<DIV> </DIV>
<DIV>make sure that the primary network log on is set to </DIV>
<DIV>"Client for M$ networks"</DIV>
<DIV> </DIV>
<DIV>It works wonderfully for me.</DIV>
<DIV>a good site I found and printed out was;</DIV>
<DIV><A=20
href=3D"http://eunuchs.org/linux/samba/samba_content.html">http://eunuchs=
.org/linux/samba/samba_content.html</A></DIV>
<DIV> </DIV>
<DIV>if your having trouble pinging the other boxes make sure your =
firewall=20
rules are correct.</DIV>
<DIV>I had that problem. if you turn off all the firewall options with =
these=20
commands sent to me by someone here see if you have any better =
luck.</DIV>
<DIV><BR>" ipfwadm -I -f<BR> ipfwadm =
-O=20
-f<BR> ipfwadm -F -f<BR> ipfwadm -I =
-p=20
accept<BR> ipfwadm -O -p accept<BR> =
ipfwadm=20
-F -p accept<BR>That opens the firewall completely so you probably don't =
want to=20
do it while<BR>you're<BR>connected to the internet (I don't know, but I=20
don't)."</DIV>
<DIV>quoted from an email to me from JJ.<BR></DIV></BODY></HTML>
=======_NextPart_000_0058_01BE5E22.36E48EC0==
------------------------------
From: "Thomas S. Martinson" <[EMAIL PROTECTED]>
Subject: Re: Win98->Linux semi-newbie
Date: Mon, 22 Feb 1999 01:57:28 -0600
The question is can you ping/Telnet across the network. If you can than the
first problem is solved. Next do you have Samba configured to the same
workgroup as you M$ 98 box. You should do this. After that is changed.
You need to go to www.samba.org and read about how to make win 98 work with
Samba. You will either have to enable encryption for the Samba server or
disable it for the Win 98 Box. I have had the most success when I disable
it on the Win98 box (that is if it is a small closed network)
Tom
Rodney Wade wrote:
> Maybe this will help some more... I posted this to another NG
> I have my kernel configured for tcp/ip and my ethernet card is detected,
>
> a big hurdle but I am still having problems with my win98 ->linux
> network. I have my IP's as follows
>
> IP Computer
> 192.168.1.1 Linux RH 5.1
> 192.168.1.2 Win98
>
> I have a 5 port SMC etherEZ hub and running Twisted pair.
> I have tried several suggestions trying to get my linux box or win98 box
>
> to recieve a ping from eachother always I get 100% loss. I have the
> following config on my win98 TCP/IP settings
>
> Win98
> IP 192.168.1.2
> subnet 255.255.255.0
> Gateway 192.168.1.1 (my linux box)
> Domain earthlink.net
> Host localhost.localdomain (does this matter???)
> Do I set this to the default under advanced tab?
> NetBIOS is enabled over TCP/IP (Shaded gray so that you cann't unselet
> it)
> Disable WINS Resolution
>
> LINUX
> My ethernet card is setup i checked my logs
> ppp0 is a modem connection to my isp
> my routeing table looks as follows
> Destination Gateway Genmask
> flags metric ref Use Iface
> 127.0.0.1 0.0.0.0 255.255.255.255
> UH 0 0 27 lo
> 206.155.151.159 0.0.0.0 255.255.255.255 UH
> 0 0 0 ppp0
> 208.254.219.6 0.0.0.0 255.255.255.255
> UH 0 0 0 lo
> 192.168.1.0 0.0.0.0 255.255.255.0
> U 0 0 1 eth0
> 127.0.0.0 -
> 255.0.0.0 ! 0 - 1795 -
> 0.0.0.0 206.115.151.159 0.0.0.0
> UG 0 0 3 ppp0
>
> ifconfig shows
> lo
> eth0 inet addr 192.168.1.1 Bcast:192.168.0.255 mask:255.255.255.0
> ppp0
>
> I would appreciate any help with samba or any other util that will help
> me get this up and running
>
> Thanks alot
>
> Rodney Wade
------------------------------
From: "Jeff" <[EMAIL PROTECTED]>
Subject: Re: Win98->Linux semi-newbie
Date: Mon, 22 Feb 1999 05:22:54 -0500
This is a multi-part message in MIME format.
=======_NextPart_000_00C7_01BE5E23.66695D00
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
OH Dear god I left out an important step.. you have to log on as root
read the man smbpasswd
then use=20
bash]$smbpasswd -a <user> <password>
so that you can log into the smb account
doh!!! sorry
Jeff wrote in message ...
Ok I am as much a newbie as you are, but I do have samba and =
masquerading working. This is my suggestion.
I am assuming you can ping the machines by now..
=20
1) cp /etc/smb.conf /root/samba <--- just in case you really get =
screwed up
2) vi /etc/smb.conf=20
3) comment out all the lines in the sample configuration
4) add these lines=20
[global]
encrypt passwords =3D True
password level =3D 8
username level =3D 8
interfaces =3D 192.168.1.1/24
netbios name =3D "your hostname"
wins support =3D True
path =3D /home/%u
=20
this will set your linux machine up to handle the domain log ons etc
=20
then on your windows machines
edit your /control panel/network/tcp-ip settings (preferably on the =
nic card not the dial up adapter) to enable wins resolution and to the =
wins server should be 192.168.1.1
<if your gonna use masquerade you have to add the DNS and gateway as =
well>
=20
make sure that the primary network log on is set to=20
"Client for M$ networks"
=20
It works wonderfully for me.
a good site I found and printed out was;
http://eunuchs.org/linux/samba/samba_content.html
=20
if your having trouble pinging the other boxes make sure your =
firewall rules are correct.
I had that problem. if you turn off all the firewall options with =
these commands sent to me by someone here see if you have any better =
luck.
=20
" ipfwadm -I -f
ipfwadm -O -f
ipfwadm -F -f
ipfwadm -I -p accept
ipfwadm -O -p accept
ipfwadm -F -p accept
That opens the firewall completely so you probably don't want to do =
it while
you're
connected to the internet (I don't know, but I don't)."
quoted from an email to me from JJ.
=======_NextPart_000_00C7_01BE5E23.66695D00
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>
<META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 =
HTML//EN">
<META content=3D'"MSHTML 4.72.3110.7"' name=3DGENERATOR>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT color=3D#000000 size=3D2>OH Dear god I left out an important =
step.. you=20
have to log on as root</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT><FONT size=3D2>read the man=20
smbpasswd</FONT></DIV>
<DIV><FONT size=3D2>then use </FONT></DIV>
<DIV><FONT size=3D2>bash]$smbpasswd -a <user> =
<password></FONT></DIV>
<DIV><FONT size=3D2>so that you can log into the smb =
account</FONT></DIV>
<DIV><FONT size=3D2>doh!!! sorry</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #000000 solid 2px; MARGIN-LEFT: 5px; PADDING-LEFT: =
5px">
<DIV>Jeff<[EMAIL PROTECTED]> wrote in=20
message<Z3AA2.6878$[EMAIL PROTECTED]> ...</DIV>
<DIV>Ok I am as much a newbie as you are, but I do have samba and=20
masquerading working. This is my suggestion.</DIV>
<DIV>I am assuming you can ping the machines by now..</DIV>
<DIV> </DIV>
<DIV>1) cp /etc/smb.conf /root/samba <--- just in case you really =
get=20
screwed up</DIV>
<DIV>2) vi /etc/smb.conf </DIV>
<DIV>3) comment out all the lines in the sample configuration</DIV>
<DIV>4) add these lines </DIV>
<DIV>[global]</DIV>
<DIV>encrypt passwords =3D True</DIV>
<DIV>password level =3D 8</DIV>
<DIV>username level =3D 8</DIV>
<DIV>interfaces =3D 192.168.1.1/24</DIV>
<DIV>netbios name =3D "your hostname"</DIV>
<DIV>wins support =3D True</DIV>
<DIV>path =3D /home/%u</DIV>
<DIV> </DIV>
<DIV>this will set your linux machine up to handle the domain log =
ons=20
etc</DIV>
<DIV> </DIV>
<DIV>then on your windows machines</DIV>
<DIV>edit your /control panel/network/tcp-ip settings (preferably on =
the nic=20
card not the dial up adapter) to <STRONG>enable wins resolution =
</STRONG>and=20
to the wins server should be 192.168.1.1</DIV>
<DIV><if your gonna use masquerade you have to add the DNS and =
gateway as=20
well></DIV>
<DIV> </DIV>
<DIV>make sure that the primary network log on is set to </DIV>
<DIV>"Client for M$ networks"</DIV>
<DIV> </DIV>
<DIV>It works wonderfully for me.</DIV>
<DIV>a good site I found and printed out was;</DIV>
<DIV><A=20
=
href=3D"http://eunuchs.org/linux/samba/samba_content.html">http://eunuchs=
.org/linux/samba/samba_content.html</A></DIV>
<DIV> </DIV>
<DIV>if your having trouble pinging the other boxes make sure your =
firewall=20
rules are correct.</DIV>
<DIV>I had that problem. if you turn off all the firewall options =
with these=20
commands sent to me by someone here see if you have any better =
luck.</DIV>
<DIV><BR>" ipfwadm -I -f<BR> =
ipfwadm -O=20
-f<BR> ipfwadm -F -f<BR> ipfwadm =
-I -p=20
accept<BR> ipfwadm -O -p =
accept<BR> =20
ipfwadm -F -p accept<BR>That opens the firewall completely so you =
probably=20
don't want to do it while<BR>you're<BR>connected to the internet (I =
don't=20
know, but I don't)."</DIV>
<DIV>quoted from an email to me from =
JJ.<BR></DIV></BLOCKQUOTE></BODY></HTML>
=======_NextPart_000_00C7_01BE5E23.66695D00==
------------------------------
From: [EMAIL PROTECTED] (Mike Jagdis)
Subject: Re: Diald disconnects after packets stop
Date: 22 Feb 1999 11:53:13 GMT
In article <kTru2.4$[EMAIL PROTECTED]>, Brady wrote:
>As soon as I leave a program that diald has connected for, it disconnects
>and I have to wait for it to dial again when I try to ftp to a different
>server. Any suggestions?
This is because diald is smart enough to notice that the TCP connection
has closed and reduces the amount of time the connection gives the
link. This is sensible because there is no point in keeping the link
up for connections which no longer exist. This is bad because the
amount of time the link gets after the last connection goes dead is
too short for many people to type the next ftp/telnet command.
There is a fix :-).
Look in your /usr/lib/diald/standard.filter (or whatever filters
you are using) for the line:
keepup tcp <n> !tcp.live
The <n> is the amount of time the link will stay up after the last
connection goes dead. It is probably something like 5 seconds by
default. I use 20 seconds which "feels" about right for me. Some
may prefer something longer - especially if they pay flat rate
for phone calls rather than time charges :-).
Mike
--
A train stops at a train station, a bus stops at a bus station.
On my desk I have a work station...
.----------------------------------------------------------------------.
| Mike Jagdis | Internet: mailto:[EMAIL PROTECTED] |
| Roan Technology Ltd. | |
| 54A Peach Street, Wokingham | Telephone: +44 118 989 0403 |
| RG40 1XG, ENGLAND | Fax: +44 118 989 1195 |
`----------------------------------------------------------------------'
------------------------------
From: [EMAIL PROTECTED] (Stuart Summerville)
Crossposted-To:
vmsnet.networks.misc,microsoft.public.windowsnt.domain,comp.unix.solaris,comp.os.os2.networking.server,comp.os.ms-windows.nt.admin.networking,comp.infosystems.www.servers.unix,comp.protocols.tcp-ip.domains
Subject: Machine name themes - what do you use?
Date: Tue, 16 Feb 1999 11:52:03 GMT
Reply-To: [EMAIL PROTECTED]
Hi peoples,
Just curious to know what themes you use for machine names on your
local networks. I've heard of or used some of the following: animals,
fruits, alcoholic beverages, artists, movie stars, & musicians. What
about you? I'm sure there's some birarre ones being used out there....
Stu.
==============================================
Stuart Summerville
Home: [EMAIL PROTECTED]
Work: [EMAIL PROTECTED]
==============================================
------------------------------
Crossposted-To:
vmsnet.networks.misc,microsoft.public.windowsnt.domain,comp.unix.solaris,comp.os.os2.networking.server,comp.os.ms-windows.nt.admin.networking,comp.infosystems.www.servers.unix,comp.protocols.tcp-ip.domains
From: [EMAIL PROTECTED] (Merton Campbell Crockett)
Subject: Re: Machine name themes - what do you use?
Date: Mon, 22 Feb 1999 11:57:26 GMT
In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
says...
>
>It's 18 Feb 99 10:28:24,
>We'll return to [EMAIL PROTECTED] and All's
>discussion of Machine name themes - what do you use?
As my colleague had laid claim to TOY and PLAYPEN, I claimed SPIELZEUG and
SPIELPLATZ. I think playground is a better translation of the latter. And,
if I ever get a particularly unreliable system, I'll call it SPIELBANK.
Merton Campbell Crockett
------------------------------
From: "NewsOO" <[EMAIL PROTECTED]>
Subject: Re: 3com 3c509 ISA card problem with 2.2.1
Date: Mon, 22 Feb 1999 13:09:14 +0100
[EMAIL PROTECTED] heeft geschreven in bericht
<7ahcur$fmu$[EMAIL PROTECTED]>...
>I upgraded my kernel to 2.2.1 last nightand all went well but when i reboot
>my ethernet card is not initializing. I have tried to compile the drivers
>right into the kernel but i still have the same problem. This all worked
fine
>before (i was using a module for the card then. I also notice on bootup
now
>a messages coming up that says "configuring pnp isa cards, or something
like
>that. I don't have pnp compiled into the kernel why is this occurring? I
>appreciate any insight into this as i am lost without my network
connection.
>
>-----------== Posted via Deja News, The Discussion Network ==----------
>http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
There is one major problem with 3c509 in combination with Linux 2.2.1:
an old (version 1.12)-driver is supplied with the source. Many problems come
from the combination Soundblaster AWE (PnP) with 3c509. They both initialize
op io-port 0x100.
There is a solution: upgrade to driver version 1.16 (1.17 is also available,
but doen'st compile right). The problem is solved, together with some other
minor problems (timings, interrupts etc...).
This should help.
comments to: [EMAIL PROTECTED] (remove nospammers)
------------------------------
** 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
******************************
