|
NOTE: In 1988, after I had given an all-day, everything-you-need-to-know-about-computers presentation for ICLE, someone said after seeing my course materials, "You ought to publish this stuff!" I began to put together The Law Office Computer Survival Guide, which I intended to sell and keep up to date as a loose-leaf reference service. It never was published, as I set it aside to get "Corporate Update" out the door. This is the beginning of my efforts, in a different format, to do a "brain dump" of information and opinions, and to keep this up to date. The good news is that you won't have to file the pocket parts, and I won't have to ship it to you. The bad news is that I haven't figured out how to charge for it. Stay tuned, and feel free to ask questions, answer questions, or make suggestions. -- Jim Eidelman | 
|
People and Planning
as of January 20, 1997
Note: I'd love to find a way to avoid some of the headaches of dealing DNS issues. I haven't had a chance to look at it seriously yet, by there may be help from Microsoft with Microsoft DNS Server.
*** Security Note ***: See "Bindings" below to prevent internet users from being able to access your hard disk. If you aren't careful, if your network is connected to the Internet, you can be giving access to the outside world to get into your network!
TCP/IP is the protocol of Unix and the Internet. In order to "surf the web" with Netscape and MS Internet Explorer, and to use Internet mail on Pokey (our Unix system), one must have TCP/IP properly configured.
Once it is working, you can Telnet to any computer by name (eg "Telnet Lawtech"), and you can "ping" a computer by IP address or name, such as "ping lawtech.com", like this:
The following describes the setup to make this work:
This is setup under Windows 95's control panel, 
Under Network Components, select TCP/IP. :
To make it work on Kohl2, the PROPERTIES settings under the tabs are set like this:
*** Security Issues **** : Note that having Bindings set correctly is critical for security reasons.
If you are using Peer-to-peer networking in which hard disks are shared with others in-house, or if you have internal drives or directories on your Web server, you can have the equivalent of a fire-wall by making sure that TCP/IP is only available for use as a "client" on the network and not for "sharing." This will prevent outside users using TCP/IP, coming in through the Internet, to be able to access the disks that are available to users on the LAN through NetBUIE (Microsoft) or IPX (Novell) protocols.
Back to Jim's Tips: www.lawtech.com/jimtips
Back to Eidelman Assocates' www.lawtech.com
