[nzlug] Server B***s-up

[Cliff Pratt]

Michael Adams wrote:
> We run a small C Class network on 192.168.0.X in an educational
> environment at work (my first attempt). It was handled by an IPCop box
> just fine. IPCop is at ...0.1, Printer 1 at ...0.25, Printer 2
> at...0.50. IPCop dishes out other adresses from ...0.60 to ...0.250. Ran
> sweet.
> 
> 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.
> I don't know much about this stuff. The IPCop box is still dishing out
> the IP addresses but I can't log into it at
> https://ipcop.localdomain:445 like i could before. I still can on
> https://192.168.0.1:445 but it is as intermittent as hell.
> 
> This new server has been set up on "newsvr.local" as its
> hostname.domainname. Are the two domains conflicting or do i look
> elsewhere for the mix-up?
> 
> Ping works fine from a thin client windows command prompt to 192.168.0.1
> (which is effectively from the new server to IPCop, i think, as
> opposed to being from the client box itself). Didn't think to ping
> ipcop.localdomain, neither did i try from a normal box to any other. I
> left there at six tonight and i am not happy. We've not been able to
> run a course since Wednesday. No, i didn't do the install. I did have
> one small consolation, in that the thin clients themselves are HP
> t5135's running linux.
> 
What's the DNS setup? The two 'domains' should not be a problem though 
they are more correctly workgroups. I would check that the Windows box 
is not running DNS, not running DHCP, not running WINS and not running 
Active Directory. Especially DHCP.

If you are running Terminal Server on the Windows box, you do realise 
that you need a Windows licence for all the thin clients, don't you? If 
a box is able to show a Windows desktop, Microsoft reckons that you need 
a) a Windows client licence for the box that is showing a Windows 
desktop, even if it doesn't run Windows and a Terminal Server client 
license for the thin client.

Cheers,

Cliff