[2898] in SIPB_Linux_Development

home help back first fref pref prev next nref lref last post

Warning: could not send message for past 4 hours

daemon@ATHENA.MIT.EDU (Mail Delivery Subsystem)
Wed Jul 26 13:17:55 2000

Date: Wed, 26 Jul 2000 13:17:39 -0400 (EDT)
From: Mail Delivery Subsystem <MAILER-DAEMON@media.mit.edu>
To: <linux-dev@MIT.EDU>

This is a MIME-encapsulated message

--NAB02920.964631859/aleve.media.mit.edu

    **********************************************
    **      THIS IS A WARNING MESSAGE ONLY      **
    **  YOU DO NOT NEED TO RESEND YOUR MESSAGE  **
    **********************************************

The original message was received at Wed, 26 Jul 2000 09:14:33 -0400 (EDT)
from PACIFIC-CARRIER-ANNEX.MIT.EDU [18.69.0.28]

   ----- The following addresses had transient non-fatal errors -----
jrandall-e@canard.media.mit.edu
    (expanded from: <jrandall@MEDIA.MIT.EDU>)

   ----- Transcript of session follows -----
jrandall-e@canard.media.mit.edu... Deferred: Connection timed out with canard.media.mit.edu.
Warning: message still undelivered after 4 hours
Will keep trying until message is 5 days old

--NAB02920.964631859/aleve.media.mit.edu
Content-Type: message/delivery-status

Reporting-MTA: dns; aleve.media.mit.edu
Arrival-Date: Wed, 26 Jul 2000 09:14:33 -0400 (EDT)

Final-Recipient: RFC822; <jrandall@MEDIA.MIT.EDU>
X-Actual-Recipient: RFC822; jrandall-e@canard.media.mit.edu
Action: delayed
Status: 4.4.1
Remote-MTA: DNS; canard.media.mit.edu
Last-Attempt-Date: Wed, 26 Jul 2000 13:17:39 -0400 (EDT)
Will-Retry-Until: Mon, 31 Jul 2000 09:14:33 -0400 (EDT)

--NAB02920.964631859/aleve.media.mit.edu
Content-Type: message/rfc822

Return-Path: <linux-dev@MIT.EDU>
Received: from MIT.EDU (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.69.0.28])
	by aleve.media.mit.edu (8.9.3/8.9.3/+ALEVE) with SMTP id JAA28072
	for <jrandall@MEDIA.MIT.EDU>; Wed, 26 Jul 2000 09:14:33 -0400 (EDT)
Received: from GRAND-CENTRAL-STATION.MIT.EDU by MIT.EDU with SMTP
	id AA07903; Wed, 26 Jul 00 09:15:09 EDT
Received: from melbourne-city-street.MIT.EDU (MELBOURNE-CITY-STREET.MIT.EDU [18.69.0.45])
	by grand-central-station.MIT.EDU (8.9.2/8.9.2) with ESMTP id JAA29877;
	Wed, 26 Jul 2000 09:14:22 -0400 (EDT)
Received: from SACSLABPC2 (SACHSLABPC2.MIT.EDU [18.78.1.88])
	by melbourne-city-street.MIT.EDU (8.9.3/8.9.2) with SMTP id JAA17789;
	Wed, 26 Jul 2000 09:14:22 -0400 (EDT)
Message-Id: <2.2.32.20000726161426.03aefbfc@po9.mit.edu>
X-Sender: ables@po9.mit.edu
X-Mailer: Windows Eudora Pro Version 2.2 (32)
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Wed, 26 Jul 2000 09:14:26 -0700
To: Jay Kirsch <jkirsch@MIT.EDU>, linux-help@MIT.EDU
From: "David C. Ables" <ables@MIT.EDU>
Subject: Re: can't connect to ethernet

>I have a Dell GX1 on campus which is partitioned half-Windows98 and half
>RedHat Linux 6.2. When I boot the Windows partition I have no difficulty

two things to check:

1. are you using static or dynamic ip addressing? (look at the network
control panel under configuration, find the tcp/ip adapter for your ethernet
card in the list, and click on properties. see if you are set to specify an
ip address or obtain it automatically.)

2. from the start menu, select run, and type "winipcfg". select your adapter
from the pop-up menu, and click on more info. this will give you all of the
numbers for your ip setup. it would be a good idea to copy all of this down.

>If I type "ifconfig eth0" I get:
>
>eth0	Link encap: Ethernet HWaddr 00:B0:D0:1A:BE:5c
>	BROADCAST MULTICAST    MTU:1500   Metric: 1
>	RX packets :0  errors:0  dropped:0 overruns:0 frame:0

this is a problem. you should get something like

eth0      Link encap: Ethernet HWaddr 00:B0:D0:1A:BE:5c
          inet addr:18.78.0.186  Bcast:18.78.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
	  RX packets :0  errors:0  dropped:0 overruns:0 frame:0

but with your ip address instead of mine. you can just type

ifconfig eth0 your-ip-address

your-ip-address is the ip address you got from winipcfg under windows. if
you were using dynamic, then dhcp will have to be configured, but first
things first. try assigning an ip address to eth0 and see what that does.

-david

---
David C. Ables
3D Printing Lab
Massachusetts Institute of Technology
ables@mit.edu


--NAB02920.964631859/aleve.media.mit.edu--


home help back first fref pref prev next nref lref last post