SCOUG-HELP Mailing List Archives

>> Next Message >>

Date:	Thu, 10 Jan 2002 08:14:21 PST7
From:	Peter Skye <pskye@peterskye.com >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: Cable connect analyze

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

Ray Davison wrote:
>
> As I said:
>
> If I click "loopback interface", 127.0.0.1 appears,
> there is no check in Enable box. I check enable,
> and now have: enable, manual, 127.0.0.1. Save
> and open again. Now have: enable, manual, no URL.

Mornin', Ray,

I don't have a URL either. 127.0.0.1 is an IP address -- is that what
you mean? (A URL is one of those things full of letters, like
www.scoug.com/kickaduck.html)

You can check manually for the loopback (127.0.0.1) configuration.
Following are the files which TCP/IP Configuration modifed (or at least
rewrote) when I tested here:

1-10-02 7:46a 251 0 SETUP.CMD
1-10-02 7:46a 0 0 INETD.LST
1-10-02 7:46a 87 0 RESOLV2
1-10-02 7:46a 13233 0 SENDMAIL.CF
1-10-02 7:46a 12899 0 sendmail.tmp
1-10-02 7:46a 12899 0 SENDMAIL.UML
1-10-02 7:46a 16384 0 deter___.DB~
1-10-02 7:46a 1526 0 TCPSTART.CMD
1-10-02 7:46a 251 0 SETUP.CMD
1-10-02 7:46a 1526 0 TCPSTART.CMD
1-10-02 7:46a 87 0 RESOLV.ORG

but the only ones that appear to have a 127.0.0.1 are the two SETUP.CMD
files. (TCP/IP Configuration is just a fancy front-end which modifies
some of your files such as SETUP.CMD.)

Look in the two SETUP.CMD files (\MPTN\BIN\, \tcpip\dos\bin\) for a line
that says

ifconfig lo 127.0.0.1

That's the line that configures the loopback to 127.0.0.1. To see if
you *currently* have it in your configuration table, from a command line
run

netstat -r

and see if you have a 127.0.0.1 table entry.

NOTE: If you also have a SETUP.CMD line that says "dhcpstrt ..." then
you should manually move the "ifconfig ..." line so it is *after* the
"dhcpstrt" line. The dhcpstrt program resets the network interface
configuration parameters so ifconfig must be after it. TCP/IP
Configuration (at least at the Fixpak 10 level which I run) erroneously
puts them out of sequence.

If you don't have a 127.0.0.1 entry in the "netstat -r" table, you can
manually set it without having to reboot. From a command line run

ifconfig lo 127.0.0.1

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

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

Return to [ 10 | January | 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.