[nzlug] Server B***s-up

[Cliff Pratt]

Michael Adams wrote:
> On Mon, 05 May 2008 22:03:19 +1200
> Cliff Pratt wrote:
> 
>> 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.
> 
> Is any of that needed for the thin clients?
>
Well, the thin clients are connected over the network. They either need 
to be statically configured or dynamically via some means. If the 
Terminal Server (TS) is handing out IP addresses to its clients, and the 
ipcop is doing the same confusion reigns.

I don't know TS enough to be sure, but the clients need to know what to 
connect to, which implies a WINS or DNS service, so that they can 
contact the TS.
 >
>> 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.
>>
> 
> 7 HP t5135s, 7 CALs. Not 100% sure about required licences for the
> existing XP boxes logging on for access to the user data and groups.
> Thought the XP licence covered that. Hmm, side issue leading me astray.
> 
OK, compliance is tricky for Terminal Server set ups. I'd get advice.

Another thing you could do is put a sniffer on the network and see what 
traffic is flying around.

Cheers,

Cliff