In October I returned home from Ireland after giving a seminar on computer
security to find that I could not access OOL news server and use or access
various other TCP/IP services via the cable modem link. Hooray for my T1!

I spent several days calling support and I analyzed many TCPIPTRACE dumps
to try to understand what had happened. I finaly hit on it and reconfig-
ured my TCP/IP stack to not use TCP Window Scaling (RFC1323). That allow-
ed me to gain access once again to OOL's news server and run X apps, etc.,
on my X server.


After 2 months perpetually pinging support@optonline.net about this issue,
I received the following email on Christmas eve day to explain *WHY* TCP
Window Scaling was disabled on their network:

| Thank you for contacting us. We apologize if this is reaching you late.
| Our engineers use Internet standards when configuring the network. We
| apologize if this causes you any inconvenience.

RFC1323 (and other RFCs) and TCP Window Scaling are NOT internet standards!

Can somebody please direct me to the William Gates compendium of Windernet
standards. It seems obvious that this is what their "network engineers"
are using in lieu of the RFCs -- especially since they still can't seem to
distinguish an OS (if you'll call anything Weendoze an OS) from a network
function.

--
http://www.legacy-2000.com for the *best* OpenVMS system security
solutions that others only claim to be.
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)COM

"Well my son, life is like a beanstalk, isn't it?"