[K12OSN] k12LTSP and static IP

Mon Feb 23 20:39:09 UTC 2004

Ah, I think I follow you now.  To run the K12LTSP apps on the Win2K 
boxes, you'll need what's called an X11 server on the Windows boxes.  
This can be anything from winaXe to Hummingbird to that X11 server that 
runs on Cygwin.  The X11 server that you run on the Win boxes should 
support XDMCP, and they'll log right in to K12LTSP just like a thin 
client does.  If the X11 server doesn't support XDMCP, that's OK too, 
but you'll just have to show your users how to use telnet or ssh.  
Believe it or not, that really isn't so hard.  My users routinely use an 
old green-screen telnet app, and they're fine with that.

Here's another option, and how I have my Windows users do it.  They 
actually run MS Office (or OpenOffice.org, for those whom I've 
enlightened somewhat) on the Win boxes, and they map their "J: drive" to 
a Samba share on the K12LTSP server.  Yes, it's boring, but it works.

--TP

Kevin Boone wrote:

> I like this setup.  I will try it.
> When I said I wanted to runn k12LTSP apps I mean running the apps 
> within the GNOME desktop envirnment. Can that be done with this setup?
>
>
>> From: "Terrell Prude', Jr." <microman at cmosnetworks.com>
>> Reply-To: k12osn at redhat.com
>> To: k12osn at redhat.com
>> Subject: Re: [K12OSN] k12LTSP and static IP
>> Date: Sat, 21 Feb 2004 18:21:30 -0500
>>
>> Then consider what I do, which is run a single-NIC K12LTSP server, 
>> like this:
>>
>>    REALLY BIG WAN
>>          |
>>          |
>>        Router
>>      (Cisco 3600)
>>          |
>>          |
>> --------------------------------------------   MAIN LAN
>>  |         |                 |        |      (say, 10.40.0.0/20)
>> K12LTSP    K12LTSP           Win2K    DHCP
>> Client     Server            Client   Server
>>           (10.40.0.254)
>>
>>
>> In this scenario, we make sure that dhcpd does *NOT* start when the 
>> system comes up.  That means doing chkconfig on dhcpd, like so:
>>
>>  chkconfig --level 2345 dhcpd off
>>
>> If for some reason that doesn´t work for you, then we do it 
>> manually.  Go into these directories:
>>
>>  /etc/rc.d/rc2.d
>>  /etc/rc.d/rc3.d
>>  /etc/rc.d/rc4.d
>>  /etc/rc.d/rc5.d
>>
>> and rename Sxxdhcpd to Kxxdhcpd, where ¨xx¨ is some number.  On my 
>> system, it´s S65dhcpd, for example.  I renamed it to K65dhcpd in _all 
>> four_ of these directories.  Double check that it´s done in all 
>> four.  Really.
>>
>> My K12LTSP server, you will note, is running in a single-NIC 
>> configuration on a switched (Catalyst 3500) network, and the K12LTSP 
>> server has Gig-E fiber.  A Bay/Nortel 350T or 450T switch w/ the 
>> Gig-E interface will work equally well.  Since I happen to run the 
>> infrastructure, I´m therefore the administrator for DHCP too, so I 
>> can add the LTSP stuff to the scope myself.  If you´re not so 
>> fortunate, then just ask your DHCP admin to add that stuff to the 
>> existing DHCP server´s scope.  Yes, it does work, and no, you won´t 
>> have any DHCP issues.  The Windows boxes will simply ignore the TFTP 
>> and NFS stuff when the OS boots.  With one tweak, this is exactly how 
>> I run it, my tweak being that the Cisco 3600 is itself the DHCP 
>> server (yep, they can do that).
>>
>> --TP
>>
>> Kevin Boone wrote:
>>
>>>
>>>
>>>
>>> This is good....yes win2k machines would be mapped to the k12box via 
>>> UNC path,shortcut on the desktop etc....to the executable that would 
>>> k12linux gui, programs etc on the win2k machine.
>>>
>>> I didn't want the win2k machines to pick up "new" ip 
>>> addresses...unless it can be done without setting  the k12ltsp 
>>> server to run dhcp.   Our school is already running a dhcp server, 
>>> I've been told that I cannot put a dhcp server on the school network 
>>> for the obvious reasons.
>>>
>>>
>>>
>>>> From: "Terrell Prude', Jr." <microman at cmosnetworks.com>
>>>> Reply-To: k12osn at redhat.com
>>>> To: k12osn at redhat.com
>>>> Subject: Re: [K12OSN] k12LTSP and static IP
>>>> Date: Fri, 20 Feb 2004 15:38:54 -0500
>>>>
>>>> Having to make a few assumptions here.  Do you mean kind of like this?
>>>>
>>>>  Win2K     Win2K     Win2K
>>>>    |         |         |
>>>> --------------------------   MAIN LAN (say, 10.40.0.0/20)
>>>>           |
>>>>           |
>>>>           |  10.40.0.200
>>>>         K12LTSP
>>>>         Server           |  192.168.0.254
>>>>           |
>>>>           |
>>>> ----------------------------   K12LTSP LAN
>>>>   |         |         |       192.168.0.0/24
>>>> K12LTSP    K12LTSP   K12LTSP
>>>> Client    Client    Client
>>>>
>>>>
>>>> In this scenario, folks would hit Network Neighborhood / My Network 
>>>> Places from the Win boxes, find a share called, say, 
>>>> \\K12LTSPBOX\coolapps\AdobeAcrobat, where acrord32.exe lives, and 
>>>> run it from there.  They may also have a desktop shortcut pointing 
>>>> to this UNC path, or maybe a mapped drive (say, N:\AdobeAcrobat).
>>>>
>>>> Is this what you have in mind?  If I´m off base here, please 
>>>> correct me.
>>>>
>>>> --TP
>>>>
>>>> Kevin Boone wrote:
>>>>
>>>>> Sort of in the reverse of attaching to a MS Terminal server with 
>>>>> rdesktop...win 2K machines would point to the k12 TS and run apps 
>>>>> on it.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> From: "Terrell Prude', Jr." <microman at cmosnetworks.com>
>>>>>> Reply-To: k12osn at redhat.com
>>>>>> To: k12osn at redhat.com
>>>>>> Subject: Re: [K12OSN] k12LTSP  and static IP
>>>>>> Date: Thu, 19 Feb 2004 23:17:27 -0500
>>>>>>
>>>>>> Kevin Boone wrote:
>>>>>>
>>>>>>> Can the TS work the same if it were given a static IP address?  
>>>>>>> In other word, can we point the clients to the server IP to run 
>>>>>>> ltsp?
>>>>>>>
>>>>>> Not sure what you mean here.  The TS should always have a static 
>>>>>> IP address itself, and by default, it does on the ¨inside¨ 
>>>>>> interface (assumes a two-NIC installation).  You have to have 
>>>>>> something consistent for your clients to point to, for both the 
>>>>>> TFTP server and the NFS server.
>>>>>>
>>>>>> Do you mean giving the clients themselves static IP addresses?
>>>>>