Ingres Connection to a network

jgroves@vanbc.wimsey.com (Jim Groves) wrote:

>>Currently, we have an Ingres database (6.4) with a combination of dumb
>>terminals and serially connected PC's.  We will be moving towards OI in
>>the near future, as well as having a company wide LAN.  In the meantime,
>>however, I would like to start with just one computer which is physically
>>right by the HP box.  What hardware/software is required to do this? 

The minimum solution would be with :-

	Ethernet Card on the server
	PC Ethernet Card (3Com or NE2000 type should work ok)	
	suitable length of RG-58 coax with BNC Plugs on the ends
	2x BNC T Adaptor
	2x 50 Ohm Terminators

Example Setup :-

Terminator  [- T ----------------------- T --] Terminator
	          |                               |
	        HP		PC

Name	      SERVER		PC1
TCP/IP       10.10.10.1		10.10.10.2
Mask	      255.255.255.0	255.255.255.0

For client software windows 95 or windows NT out of the box would do or
any of the good 3rd party packaged TCP/IP solutions for windows 3.1

Assign different TCP/IP address in the same range for the server and client.
10.x.x.x is reserved to system not connected to internet.


 >>Is there more that one option? 
	
This a very open question, I remember starting very similarly in 1991 with 
about 3 PC and some ethernet cable. The system has now growth to
around 7 building with a fibre backbone. Since you are networking to Unix
it would be sensible to use ethernet and not token ring as almost all Unix box 
come with ethernet networking as standard.

Options :-

1) Physical  toplogy. Normal ethernet the easist option for Unix systems. The
Other choices are :-

	Ethernet 10Mibt
	fast-Ethernet 100Mbit
	Token ring 4Mbit
	Token ring 16Mbit
	FDDI Optical


1) Cabling. This really depends on the size of implementation for a few
computers in the same room thin wire ethernet cabling is simple and crap. For 
Larger implementation twisted pair structured cabling the only way to go. 
Think about for building and how they are cabled. If you have some good
structured cabling to the serial connections you may be able to reuse this
for ethernet networking. If not you may want to think about implementing this
as it's a godsend.

Choices :-
	Thin Wire
	Twisted Pair
	Optical fiber

2) Network Protocol. Again since you are link to Unix the choice is easy use
TCP/IP.  The Unix box will have the most TCP/IP functionality built in and
almost any computer has a TCP/IP stack available.

Choices :-
	IPX (novell)
	TCP/IP (Unix, LAN Manager,  ,Windows )
	Netbui (LAN Manager,  ,Windows )

3) Services. This is where any business case in made. The implementation of a
network allows for a large number of shared services. 

Options :-
	- Terminal Services to replace existing serial connections. (TELNET)
	- File Transfer to PC (FTP, TFTP)
	- File services (NFS or LAN-Manager)
	- Remote printer sharing (LPR,LPD, LAN-Manager)
	- Sockets interface (WINSOCK 1.1 or BSD )
	- Remote Procedure Call (Sun-RPC or DCE-RPC)
	- X-Windows for remote session on Unix (X11 on DOS or Windows)
	- Ingres/Net for pc connection to database
	- Openlink or SQL-Retriever for reliable ODBC connection to server
Ingres Q & A
To William's Home Page
Email William