<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Okay, I missunderstood his hook up. Mine is as described below and
there are 4 servers on my campus. Our next step is Vlan so that it
doesn't matter where in the school we are or what server we need to
access.<br>
Bye<br>
Pat<br>
<br>
Les Mikesell wrote:
<blockquote
cite="mid1105990112.13450.101.camel@les-home.futuresource.com"
type="cite">
<pre wrap="">On Mon, 2005-01-17 at 12:58, John P. Conlon wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Wouldn't specifying a fixed IP for eth0 avoid conflicts with the WIN2K
server?
</pre>
</blockquote>
<pre wrap=""><!---->
The network-booted clients need to pick up everything via dhcp
assignments, and unless you play tricks with a non-standard
port you can only have one DHCP server on the same network.
If you can split the networks so eth1 picks up an address from
your existing server and eth0 is isolated on a separate
switch/network with the clients, everything will work
with the default setup.
</pre>
</blockquote>
</body>
</html>