Isolating a thin client setup

[fafster]

How would I got about setting up Server 2003 to act as a gateway between a room of thin clients and the rest of the network? It's the default setup for LTSP but all the Windows solutions I've heard of broadcast the boot server details over the whole network.

 

Unfortunately we can't do that, so we're restricted to a single room. I've looked at going down the Edubuntu route, but it's going to cause headaches from the number of applications that need to be run.

 

Thoughts?

[Geoff]

Use a VLAN?

[fafster]

I don't have access to the switches. I don't know if you saw my FFS thread, but the LEA won't be of any help. Each time we ask for something we're turned down.

 

Maybe I'll try something like smoothwall...

[Geoff]

If you have physical access to the switches, it's not amazingly difficult to gain access.

[dhicks]

I don't have access to the switches.

 

Could just buy a separate switch (£100?) and create a mini-LAN just inside the classroom. That's what we have for our Edubuntu setup - the server has two network cards in, one for network/Internet access and one to connect to the dedicated switch and talk to the thin clients.

 

--

David Hicks

[fafster]

I can always utilise the switch already in place for the class. It's just that I want to place something between that switch and the link back to the backbone. In an LTSP setup (like your Edubuntu server) that's all taken care of. I was just wondering if the same thing's possible in Server 2003.

[Ric_]

There's nothing to stop you binding services to a particular NIC in a server - e.g. a DHCP service bound to NIC 2 (your classroom netork) whilst NIC 1 is sat on your 'normal' network.

[fafster]

There's nothing to stop you binding services to a particular NIC in a server - e.g. a DHCP service bound to NIC 2 (your classroom netork) whilst NIC 1 is sat on your 'normal' network.

 

Now that's exactly what I'm looking for! Cheers Ric.

 

Now to create another thread on thin clients