RE: Using Static IP addresses

["Rutherford, John (Library)" <Rutherford@xxxxxxxxxx>]

One reason to use the same IP address for
staff connections can be security. The
innopac tables will allow you to prevent
staff logins from all but library staff
pc's for the various services provided by
the Innopac (ftp, telnet, z39.50, Millennium
connections etc.)

This can be useful, and can also be used to
autologin public terminals connected to 
term servers with known IPs.

With DHCP this can be a problem since the IP's
can change each day. One way to get around this
that seems to work ok is to set up reserved DHCP
addresses based on the Hardware (MAC) address of
your network interface. We do this and rarely have
problems.

John Rutherford
Conn State Univ.

-----Original Message-----
From: Michael P. Roche [mailto:mproche@xxxxxxxxxx]
Sent: Thursday, August 09, 2001 9:10 AM
To: innopac@xxxxxxxxxx
Subject: RE: Using Static IP addresses


We do not use Millenium at RCPL but I do understand DHCP.

Static IP addresses are assigned to each client manually and one must have
enough IP addresses for all hosts connected to the network.  If you have
enough IP addresses and someone to correctly input and maintain the network
than static works wonderfully.  Static IP addresses are easier on the
network.

DHCP assigned addresses are easier to implement and make changes to when
necessary.  You only have to make changes to the scope on that subnet.  The
first time you start your computer it needs to get an address from the DHCP
server.  Every time you reboot your computer it will update it use of the
DHCP address with the server and at 50% of the duration of the lease it will
again update its use of the IP address.  Thus creating a demand on your
network infrastructure.

The choice will be one of which provides the best use of resources.  First,
do you have enough IP addresses for all of your hosts?  If you do either
will work fine.  Second, do you have more hosts than IP addresses?  If you
do than you need to use DHCP.  Third, depending upon your network, it is
quite easy to have a mixture of static and DHCP assigned addresses.

The only reason to require Static IP addresses would be if III software had
to have a consistent IP address to talk to the client.  That would not make
much sense, but might be a reason.

Michael P. Roche

Automation Librarian

Rockingham County Public Library
527 Boone Rd.
Eden, NC 27288

work:    (336) 623-1707
fax:        (336) 623-1258

email:    mproche@xxxxxxxxxx


-----Original Message-----
From: owner-innopac@xxxxxxxxxx
[mailto:owner-innopac@xxxxxxxxxx]On Behalf Of Ruth O. Owopetu
Sent: Wednesday, August 08, 2001 18:47
To: innopac@xxxxxxxxxx
Subject: Using Static IP addresses

It is my understanding that III recommends the use of static IP
addresses for workstations running the Millenium products. My
institutionn uses DHCP.  Can any of the libraries running static IP
addresses share with me the advantages over DHCP?

How did you convince your IT people to go from DHCP to Static IP
addresses for your workstations?

What are the problems associated with DHCP?


This is very urgent.

Thanks for your help.
Ruth O. Owopetu

--
This message was distributed through the Innovative Users Group INNOPAC
list.
Private replies:  "Michael P. Roche" <mproche@xxxxxxxxxx>
Public replies:   INNOPAC@xxxxxxxxxx
Archives:  http://innopacusers.org/list/archives/
--
This message was distributed through the Innovative Users Group INNOPAC list.
Private replies:  "Rutherford, John (Library)" <Rutherford@xxxxxxxxxx>
Public replies:   INNOPAC@xxxxxxxxxx
Archives:  http://innopacusers.org/list/archives/