[K12OSN] one more time
sbetts at msad71.net
Thu Feb 24 17:24:09 UTC 2005
Nathan Sinton <nsinton at gmail.com> on Wednesday, February 23, 2005 at 1:04
PM +0000 wrote:
>Just to clarify, you have linux clients and a windows server and you
>need the clients to be able to log on to the windows server and access
>file shares, printers, etc... Right?
Yes, I have Linux clients and a windows network -- this is working fine.
I want to add a linux terminal server to the mix.
>On Wed, 23 Feb 2005 11:54:26 -0600, Jim Kronebusch <jim at winonacotter.org>
>> > I tried to ask this previously, but wasn't clear, I guess.
>> > Is there anyway to incorporate LTSP into an existing Windows
>> > 2000 / 2003 network? I have a Windows network with DHCP,
>> > authentication/file and terminal servers running. I would
>> > like to add an LTSP to the network --
>> > but HOW? The clients need to access every resource -- they
>> > are all local
>> > bootable clients (no true thin clients booting from the server).
>> I too am a little confused as to what you want. I read this as you have
>> an existing all windows network. You don't want to change anything with
>> the Windows setup. But you want to add a LTSP server to the existing
>> network and then either boot the current Windows machines via a boot
>> floppy (or some other means) to the ltsp server when needed, and then be
>> able to reboot back to a full local install of windows when needed. Or
>> do you mean you want to connect to the ltsp server from a windows
>> If the first assumption is correct I think you just need to build a
>> single NIC install of ltsp. Set DHCP to run on an alternative port.
>> Then set your boot floppys or whatever to get dhcp from the alternate
>> port. I would think you could setup a custom boot loader on the local
>> installations that would give you a menu to choose boot Windows or LTSP,
>> then not mess with any boot disks. I am pretty sure I have seen this
>> done before. I think that would be your most seamless option.
>> This message has been scanned for viruses and
>> dangerous content by the Cotter Technology
>> Department, and is believed to be clean.
>> K12OSN mailing list
>> K12OSN at redhat.com
>> For more info see <http://www.k12os.org>
>K12OSN mailing list
>K12OSN at redhat.com
>For more info see <http://www.k12os.org>
MSAD#71 Director of Educational Technology
sbetts at msad71.net http://www.msad71.net 207-985-1100
"To err is human - and to blame it on a computer is even more so."
More information about the K12OSN