SCOUG-HELP Mailing List Archives

<< Previous Message <<

Date:	Tue, 5 Feb 2002 14:46:04 PST7
From:	Steve Carter <scarter@vcnet.com >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: DHCP

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.
=====================================================

On 2/05/02, Peter Skye wrote, in part:

>> the W4 FP 12/15 machine won't acquire a lease.
>Did you set up TCP/IP?
>Did you fix SETUP.CMD?
>
>In TCP/IP Configuration, on the Network tab, select your interface and
>check the "Automatically, using DHCP" box.

As I stated in my original message, this machine has been working
on fixed IP for 2 years -- first as an Injoy gateway with two NICs,
and later on the SMC7004BR router. It is STILL working on fixed IP,
because I put it back after I could not get DHCP to work.

The first (and almost only) thing I did was to enable DHCP for
the PCI 10/100 NIC connected to the network (in the TCP/IP notebook).
I did not delete the contents of the route, DNS and other TCP/IP
notebook settings since I expected them to be supplied by the DHCP
server in my SMC7004BR. It works OK with the two windows machines
on DHCP.

The 10Base-T (ISA) Lan card is still installed in the machine (as Lan0),
but disabled since I'm no longer using the machine as a gateway.
I could remove it, but since it is not part of the problem, it is
more convenient just to leave it there.

I made

NO MODIFICATION to setup.cmd.

At one time, I did enable the loopback 127.0.0.1 interface and I can
still ping myself (when configured for DHCP), but I have no IP address.
(I want 127.0.0.1 still enabled, aliases and all.)

Regrettably, I know nothing about DHCPMON, iptrace, inetver and
almost nothing about syslevel.

>Although it doesn't affect acquiring the DHCP lease, you have to fix
>your \MPTN\BIN\SETUP.CMD file if you're using 127.0.0.1. Move the
>"ifconfig lo 127.0.0.1" line so it is *after* the "dhcpstrt ..." line.

This is the kind of information I was looking for. Can I leave
it modified permanently even when/if I go back to fixed IP (I'm
back there now 'cause I need the connectivity)? Will is stay put
or will I have to remember to hack setup.cmd each time I switch
back and forth?

>If it still doesn't work, where does the error occur? Is there a
>"dhcpstrt ..." line in your \MPTN\BIN\SETUP.CMD file?

Didn't check. I'll check when I get close to the machine again.

>Do you get a DHCPSTRT error message during bootup?
>Does DHCPMON show an error? >- Peter

There is no indication of an error.
No error message appears.

I'm not intentionally starting DHCPMON.

If there are DHCP fixes for TCP/IP required, how do I find out
about them? I've been to the IBM site but did not find anything
that I thought I should have. I'm running TCP/IP (about) 4.02,
I think.

-- Steve

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

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".

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

Return to [ 05 | February | 2002 ]

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.