Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!ukma!rutgers!att!ulysses!nsscb!det
From: det@nsscb.UUCP (Dennis Erwin Thurlow)
Newsgroups: comp.sys.att
Subject: Re: 3b2/600 Wollogong woes...
Keywords: WIN TCP/IP 2.1
Message-ID: <782@nsscb.UUCP>
Date: 3 May 89 22:01:10 GMT
References: <2703@cadre.dsl.PITTSBURGH.EDU> <781@nsscb.UUCP> <11314@ea.ecn.purdue.edu>
Reply-To: det@nsscb.UUCP (Dennis Erwin Thurlow)
Organization: AT&T NSSC 5000 Hadley Rd. S. Plainfield, NJ 07060
Lines: 20

In article <11314@ea.ecn.purdue.edu> kindred@ea.ecn.purdue.edu.UUCP (Donald Kindred) writes:
>I originally reported my problems with WIN TCP/IP on Jan. 6, 1989
>to AT&T's Hotline.  I've talked to both AT&T NJ, and AT&T Lyle IL.
>I'm still waiting for some of the "fixes".


Don, I've looked up that ticket, talked to the engineer that
worked with you, and sent this posting to several higher-ups
here at the hotline. You and I can continue this off-line.

In general, let me say this. I don't get paid to read the nets,
or respond. If you want TCP/IP fixes, call 1-800-922-0354 and
tell them you have a problem with tcpip. Ask for det in networking
(x6336). That way I can keep my job.

If enough people were to write someone here like Judy Huseman
and request that someone (like me) get paid to read the nets
and direct problems thus discovered to the proper problem
solvers, maybe they'd do it.
-nsscb!det