[K12OSN] k12LTSP and static IP

[Terrell Prude', Jr.]

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?
>
>