said:
>Ping is not a subject I am conversant with. I tried PING "isp domain"
It doesn't do that much. As usual for tcp/ip commands:
tcphelp ping
The reason I suggested it is that it will generate more traffic to your
ISP than will the DHCP Monitor.
>and PM Ping which apparently can figure out the identify of my ISP on its
>own. What result should I expect if I am unable to connect?
It depends on the failure. What I would do to check connectivity to
charter.net
- open command window
- iptrace
- open command window
- ping www.charter.net
- let if run for a minute or so
- Ctrl-C to kill it
- switch to iptrace window
- press enter to stop iptrace
- ipformat >pingfail.txt
- review pingfail.txt for ideas
If nothing obvious pops out at you, email me a copy of pingfail.txt as an
attachment and I'll see what, if anything, I can see.
Steven
--
----------------------------------------------------------------
"Steven Levine" MR2/ICE 2.30a #10183 Warp4/FP15
www.scoug.com irc.webbnet.org #scoug (Wed 7pm PST)
----------------------------------------------------------------
=====================================================
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 [ 07 |
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.