[nzlug] Server B***s-up

[Warren]

On 5/May/08 22:10 , "Cliff Pratt" <enkidu at cliffp.com> wrote:

> Robin wrote:
>> On Mon, 05 May 2008, Michael Adams wrote:
>>> Now we have a new IBM Server running Windows Server 2008 going in
>>> at ...0.8 with thin clients and everything is bogging down on the
>>> internet for pre-existing boxes (non-thin clients) and with the
>>> IPCop box itself.
>> 
>> My initial guess would be that you have a doubling up of IP or MAC
>> addresses. That can cause a whole lot of strange.
>> 
> Agree. That could happen if you have two DHCP servers going at the same
> time, serving IP addresses from the same range.
> 
> 'ipconfig /all' will tell you where a machine is getting its IP address
> from.
> 

I'll second that notion - it sounds like there are now two DHCP servers on
the network - the Windows server will be using "itself" for DNS, hence the
ability to ping via IP address for the ipcop machine, but "random" answers
for trying the name.

Without knowing the setup of the thin clients, I couldn't comment on how
they work (could be magic bit set in DHCP?)

I would imagine that you either need to turn off the DHCP server on one of
the devices or alternatively add in the reservations to both servers and
change the dynamic portions to non-overlapping portions.

Of course, two DHCP servers builds in redundancy to your network (which is
irrelevant if you need internet access and that's handled through the failed
"gateway") and introduces the complexity of managing two DHCP servers with
reservations

HTH,
Warren