SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, Southern California OS/2 User Group. ALL RIGHTS RESERVED.

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.

The Southern California OS/2 User Group
USA

SCOUG-HELP Mailing List Archives

Return to [ 09 | January | 2002 ]

>> Next Message >>


Date: Wed, 9 Jan 2002 01:37:50 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.
=====================================================

> Peter Skye wrote:
> >
> > First try pinging your own machine:
> >
> > ping 127.0.0.1

Sheridan George wrote:
>
> I don't think this will work if he is using 192.168.123.x? As
> you pointed out, Peter, he has a long lease time so he may
> be on DHCP on his LAN. In that case he will have to ping
> whatever DHCPMON says his machine's IP is currently.

Hmm. Sheridan and Ray, try pinging 127.0.0.1 on your machines and see
what happens.

I *think* that the address 127.0.0.1 is a spec which I read in an RFC
and that it always points to your local machine.

I *think* that 127.0.0.1 is a valid IP address on every single machine
on a network but it always points to the machine where you are located
-- in other words, the address 127.0.0.1 goes to a machine's TCP/IP
stack which looks at it and says, "hey, that's me!".

Out on the network, however, nobody else can get to your machine using
127.0.0.1 because *their* TCP/IP stack will say "hey, that's me!" and
think they are requesting access to their own machine.

So any of you guys with firewalls in place, try pinging 127.0.0.1 and
see what happens (unplug the network cable for this test to make sure
the response doesn't come from elsewhere).

*My* SMC firewall is still in its box, where it has been vacationing
since I bought it six months ago. I don't have a firewall. That's why
I'm not giving any of you my IP address. :)))

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

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


>> Next Message >>

Return to [ 09 | January | 2002 ]



The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA

Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS RESERVED.

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.