SCOUG-HELP Mailing List Archives

>> Next Message >>

Date:	Sun, 7 Apr 2002 10:58:58 PST7
From:	"Tom. Brown" <thombrown@san.rr.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.
=====================================================

Pinging 127.0.0.1 worked, but nothing else. I ran SETUP.CMD, no change.
Had to reboot.

"Tom. Brown" wrote:
>
> =====================================================
> 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.
> =====================================================
>
> Thanks, Peter!
>
> I haven't tried pinging localhost, but I can't ping my LinkSys router at
> 192.168.1.1 when I have this failure. Obviously, nothing else works
> since it's all beyond the router! :-(> Will try SETUP.CMD in the
> morning.
>
> Peter Skye wrote:
> >
> > =====================================================
> > 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".
> >
> > =====================================================
>
> =====================================================
>
> 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".
>
> =====================================================

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

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 [ 07 | April | 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.