Immersed in networking hardware and software for 7 years at the Univ. of
Utah, Campus Networking Dept. This included design, installation, testing,
troubleshooting, and repair, from low level issues such as investigating
broadband problems with a spectrum analyzer, or Ethernet problems with an
oscilloscope, or using the correct 10BaseT plug for twisted versus solid wire,
up through extensive use of protocol analyzers and SNMP monitoring and analysis
tools. Physical layers included FDDI and other fiber optics, DS1/DS3, and all
forms of Ethernet from the original "yellow hose" through 10BaseT, linked
through repeaters, bridges, switches, and routers (primarily cisco). Protocols
included TCP/IP, AppleTalk, Novell IPX, and DECNet, among
others. 1988-1995
As a consultant and later an employee of RAHD Oncology Products, I was often
engaged in the design of special network setups. For example, in 1994, a
demonstration of remote radiation treatment planning between Salt Lake City and
both Los Angelos and San Francisco convention centers, via T1 lines. And, in
1999, the setup of a distributed software development environment via newly
available high speed cable modem home network access. I also would provide
remote network troubleshooting assistance for clients, such as remotely
diagnosing a speed problem for a client in New York across three hospitals
linked via ATM. 1993-2006
Designed and implemented a network transparent communication system for a
production distributed information retrieval system for the CIA. This was part
of my Computer Science M.S. research in networking and distributed systems, and
was in use for 10 years. 1984-1986
With my ongoing work for remote clients, networking continues to be a
fundamental part of my life. 2003-current
My interest in networking originated with the ARPAnet, which led me to
Computer Science at the Univ. of Utah, given its key involvement with the
ARPAnet from its inception. Along with later work in Campus Networking, I became
accomplished in network design, implementation, and troubleshooting, from low
level hardware and signals on a wire, to the use of protocol analyzers and SNMP
monitoring and anlysis.
