SCOUG-HELP Mailing List Archives

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

Date:	Mon, 7 Jun 2004 08:24:00 PDT7
From:	Peter Skye <pskye@peterskye.com >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: Chapman, this Sunday ?

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

George M. Boyd wrote:
>
> The Moz 1.3 opens, but does not find my.yahoo.com or any
> other URL and times out. The DSL and LAN lights on the DSL
> modem are on. The router shows connection to the NIC at port 1.
> ... In addition to the DSL problem, the IBM dialer into the dialup
> modem is now giving trouble. It used to halt at "slattach Version 2.0
> Revision 1.5" and restarting it by hanging up and clicking on "dial"
> would have it proceed. Tonite, it halted earlier and waited a long
> time before completing the string. It then dialed and connected to lafn.

For what it's worth, my Verizon DSL line was quite ill from Friday
evening to early this morning. I don't know who is subcontracted to who
but here's a quick summary in case you're part of the same "loop":

-- There was a major "dslam" (no need to Google, use
http://www.techweb.com/encyclopedia/) equipment failure in So.Cal last
week.

-- My problem appeared to be large packet failure; they wouldn't go
through the Verizon router. Tech Support couldn't see any traffic on my
side when large packets were inbound (i.e. from one of those large-file
"speed tests") but small packets like ping or NTP were fine. "No
traffic" means the problem wasn't a packet CRC failure on my side --
there weren't any retransmissions which you would get if there were CRC
errors. (If the CRC is 8 bits, then does that mean one out of every 256
bad packets gets through?)

-- When using telnet to maintain the SCOUG email server it could take as
long as four minutes to get a response rather than the usual
"instantaneous" response. I tried time-tagging a command to see where
the delay was, i.e. "DIR & TIME" on one line, and the response when it
finally arrived showed the command was received and executed by the
SCOUG server immediately but the response back to me took a long time
(the SCOUG server runs OS2NTPD and so do I so the clocks were
synchronized).

-- Funny moment of the day: One of the Verizon techs, when I said I was
using OS/2, replied "you mean you're using an old Mac?". (The Mac runs
OS9 and OS10).

This morning everything is working fine. Maybe the Verizon night crew
finally got to my trouble ticket.

- 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 [ 07 | June | 2004 ]

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.