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 [ 06 | April | 2002 ]

<< Previous Message << >> Next Message >>


Date: Sat, 6 Apr 2002 20:39:16 PST7
From: Peter Skye <pskye@peterskye.com >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: TCP/IP dying

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

Tom. Brown wrote:
>
> TCP/IP or some component of it died
> Can anyone tell me if there was a resolution
> to the problem and what the fix is?

I don't remember any particular resolution or fix. From a command line
you can run the SETUP.CMD command file that's located in \MPTN\BIN\ --
that's how your CONFIG.SYS gets your machine started.

I've been getting a lot of TCP/IP hangs the past couple of weeks since I
switched to a different POP email host provider. Near as I can figure
my 4.02y stack isn't timing out when a request doesn't receive a
response. The 4.0 stack only allows for 2000 sockets so a lot of
"hanging sockets" will eventually fill the table and cause a freeze.
(Closing the apps or command line windows which these hanging sockets
are assigned to seems to free them.)

To troubleshoot:
===============

First ping yourself:

ping localhost
or
pint 127.0.0.1

to make sure your stack is working. (If your \MPTN\ETC\HOSTS text file
doesn't have a "127.0.0.1 localhost" entry then skip this step.)

Then ping your Domain Name Server to make sure it's available, for
example:

ping 4.2.2.1

(4.2.2.1 is Verizon's DNS - use your own ISP's DNS IP address instead.)

Then use NSLOOKUP on any known-good domain to verify that your Domain
Name Server (DNS) is working and can resolve URLs:

nslookup san.rr.com
-and in reverse-
nslookup 24.25.195.1

Maybe something in the above will help.

- 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 << >> Next Message >>

Return to [ 06 | April | 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.