SCOUG-HELP Mailing List Archives

Return to [ 23 | July | 2000 ]

<< Previous Message <<


Date: Sun, 23 Jul 2000 20:26:06 PDT
From: Peter Skye <pskye@peterskye.com >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: GTE DSL Challenges Skye To Steel Cage Match

Content Type: text/plain

=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================

Steven Levine wrote:
>
> > "No interfaces to trace!"
>
> It probably needs to be:
>
> iptrace lan0

Yup. That did it. :)

First, I started IPTRACE LAN0. Then I started DHCPSTRT -I LAN0. After
DHCPSTRT gave me an error message and returned to the command line, I
stopped IPTRACE.

The IPTRACE and DHCPSTRT sessions follow. I'm sending the IPTRACE
output to Steven directly since it's a bit long for posting to this
list.

[F:\]iptrace lan0
lan0: tracing enabled
lan0:[ 0.000]: Dest: 255.255.255.255 Source: 0.0.0.0
lan0:[ 33.016]: Dest: 255.255.255.255 Source: 0.0.0.0
lan0:[ 18.031]: Dest: 255.255.255.255 Source: 0.0.0.0
lan0:[ 27.031]: Dest: 255.255.255.255 Source: 0.0.0.0
lan0: tracing disabled
[F:\]

[F:\]dhcpstrt -i lan0
DHCPSTRT: Waiting for DHCP client.(maximum wait = 60 seconds)
DHCPSTRT: DHCP client did not get parameters.
DHCPSTRT: Continuing to try in background.
[F:\]pstat | find /i "dh"
0021 0000 16 F:\MPTN\BIN\DHCPCD.EXE 01 0200 FDF27E14 ...
... Block 09DB A06F 01 DHCPCLNT
F:\MPTN\BIN\DHCPCD.EXE 0021 16 F:\MPTN\DLL\TCP32DLL.DLL
[F:\]

I'm sending Steven the formatted trace output directly, since it's a
little long for posting to this list.

> >DEVICE=F:\IBMCOM\MACS\AN16.OS2
>
> My notes say NIC must follow MPTS. Move this after
>
> DEVICE=F:\MPTN\PROTOCOL\IFNDIS.SYS

I moved it. Curious, though -- the sequence was created by the
installation software. Perhaps it got out of sequence during a
reinstall?

After moving it, I got the same DHCPSTRT.EXE error message.

> > DriverName = AN16$
> > interrupt = 10
> > iobase = 0x300
>
> This should be OK. IRQ 10 is usually free.

I picked IRQ 10 manually.

> >option 60 "IBMWARP_V3.1" # Vendor Class
> >option 77 "IBMWARP_V3.1" # User Class
>
> These look OK. You might want to turn on
> the logging options (i.e. logitem, logfile).

My only manually entered option is:

option 12 "localhost"

which I'm told is required.

> >LANTRAN.LOG:
>
> >IBM OS/2 LANMSGDD [01/03/00] 5.05 is loaded and operational.
> >IBM OS/2 LAN Netbind
>
> This is way too short. It should show the NIC loading and report the MAC
> address. See my suggestion re reordering the load statements.

I did the reordering. Here's the _new_ LANTRAN.LOG: :)))

[F:\ibmcom]type lantran.log
IBM OS/2 LANMSGDD [01/03/00] 5.05 is loaded and operational.
IBM OS/2 LAN Netbind

> When you boot, use Alt-F2 and watch for the driver loading message.

Umm, okay, since it was _you_ who asked me to do so, I did. Any
particular reason?

> Also, haul out your trusty hex viewer and see
> if the driver supports the VERBOSE keyword.

Nope. (I used EPM for a "quick look for text".) This particular driver
(the card has a UMC chip) doesn't appear to use _any_ command line
keywords.

> You might want to consider adding the NetBIOS
> protocol, just to make the logging more verbose.

Didn't try that yet. This has _gotta_ be an easy fix; it would be nice
if it was a _clean_ ("no NetBIOS needed") fix.

Some additional possibilities:

-- 1. Could it be my "localhost" setting? The IPTRACE info shows that
name being broadcast during the search for DHCP servers. (See RFC
2131.) Is it possible that GTE has a different name for my connection,
and that's why I'm not receiving their DHCP response packet even though
they send it?

-- 2. Could it possibly be the NIC driver? GTE DSL Support sees my
first broadcast packet, but maybe their response packet isn't getting
processed somehow; maybe I should put in a D-Link card and see if
there's any difference.

- Peter

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================


<< Previous Message <<

Return to [ 23 | July | 2000 ]