About PenyuLAN

Penyu Radius is a special unit under Millennium Radius Sdn Bhd (“MR”) which has been setup, organized and operated in Dungun, Terengganu, MALAYSIA since January 2010.

PenyuLAN is a free software to monitor computers in a local area network. PenyuLAN is most suitable for internet café monitoring system. However, the features are also useful for school computer labs for monitoring purpose.

PenyuLAN can be used on local area network (LAN) whereby it will connect to the client PCs through the IP using designated port number.

PenyuLAN can perform the following remote control and monitoring on client PCs:-

1. Lock and unlock screen
2. Logoff
3. Restart
4. Shutdown
5. Send warning message
6. Capture screen
7. Check running program

Screenshot

Additional features which are suitable for internet cafe operations are:-

1. Record time and amount of usage for each PC
2. Currency is based on computer regional setting
3. To record food and beverage and other services
4. User account control
5. Comprehensive management report

PenyuLAN comes in three (3) editions which are Ganu Edition, Keropok Edition and Ikang Edition. The only difference between these editions is on the number of computers it can monitor.

As to date, PenyuLAN software is totally free without any limitation on number of use or any advertisement or nagging screen. For Keropok and Ikang Editions, you need to register to activate the software and registration is free.

With Penyu Radius software, internet cafe operators can now automate their business operation with free cyber cafe software. PenyuLAN is a cyber cafe software which is easy to use. PenyuLAN cyber cafe software will update PC monitoring usage for every second. This will allow the administrator to monitor PC usage with most updated information.

They are  also offer software customization to suit your special needs. PenyuLAN is not only suitable for internet cafe but also useful for schools or colleges computer lab. You will find it easier to monitor every computers in your computer lab.

Make sure you get the latest version of PenyuLAN software to ensure your cyber cafe operates with the latest version. They are gradually fix any problem with PenyuLAN cyber cafe software. Improvement and enhancement has been continuously performed to ensure their users get the best performance out of the free cyber cafe software.

You can download PenyuLAN from here : Download Site

Millennium Radius
(Dungun Branch)
No 4, Jalan Pak Sabah
23000 Dungun, Terengganu
MALAYSIA
Tel: 609-8444 277
Fax: 609-8445 277
Email: penyu@penyuradius.com
URL: http://www.penyuradius.com

Although this site was dedicated to the Open Source Softwares technologies for cyber cafe, but the document still got a relation to the FOSS technology. Perhaps this old instruction could give us some motivation to search and to develop new kind of methods to full utilizes open source softwares for cyber cafe purpose.

This old document just made me to remember my old days dealing with NT 4.0 / 2k Terminal Server running with Citrix Metaframe before I met Linux and LTSP, but right now I was falling in LOVE with DRBL.

So guys, I hope you all could give some suggestion or some ideas for us to share at OSSCC Community, and please have a look to the document below.

Creating Linux Diskless Client For Windows 2k/2003 Terminal Service
By Avinoam Levkovich

version 1.0

The company I work for has many old computers that are no longer suitable for the common application today ( try Running Office XP/2k on a P-I 100MHZ with 32MB Ram, and you will find out that this is not a pleasant experience ). We start looking for a solution that will save the money of buying new computers or Brand thin-clients. The goal was to use our old computer and still get good performance . We find the Linux solution just great for my goals.

we still use our old computer and the only investment we will have to make is buying the Windows 2K/2003 licenses and hardware .

The solution is actually an integration of the following Sub systems : LTSP, rdesktop and wilisystem , fortunately those systems are integrating quite naturally as you will see .

LTSP  : ( http://www.ltsp.org )

Is the backbone of all the system which provide the Linux terminal services for the diskless client. after installing LTSP it create the /opt/ltsp/i386 Directory.

this Directory will be the root system of our diskless clients. when booting the client it will get its kernel by tftp from LTSP and then it will mount /opt/ltsp/i386 as its root directory.

So after your client finish its boot process you will be logged to your LTSP Server and your file system will be the /opt/ltsp/i386 Directory. and then the Wilisystem start Working.

Rdesktop : (http://www.rdesktop.org )

Microsoft has developed a protocol called RDP which is used for the Terminal Server communication with the client.

The rdesktop package is an application that opens RDP Session with a Windows Server and by doing it , the Linux station become a Windows Terminal Client.

Wilisystem : ( http://www.wilisystem.com/ )

The Wilisystem is actually a patch for the LTSP server. what is does is make the connection to the Windows Terminal Server as easy as it can get.

The Wilisystem uses the rdesktop package and finish the Diskless client boot process with the Windows login screen. by doing this it make the LTSP Session invisible to the user who feel as if he is plugged directly to the Windows Server .

I must thank the wilisystem developers for a great job !

Rom-O-Matic : ( www.rom-o-matic.net )

This is where you get you boot image for you selected boot Device ( I used a floppy ). after specifying your Ethernet card model you can download your boot image.

Great implementation for a great idea.

please read the documentation from the Above web site’s. when you read the documentation you will discover all the options and benefits that you can get from this system and how to tune it to your needs.

what you need :

1. Linux Server , I used P-III 800 with 256MB RAM , With Red Hat 9.0 .

2. Diskless Client, I used a P-I 133MHZ , 32MB RAM, Ati – Rage XL (mach64 Family) Display Adaptor, with the intel 100/pro Ethernet .

3. Windows 2K/2003 Server With Terminal Services installed, configured and Running .
I used a P-4 1.7MHZ with 256MB RAM.

Create your diskless Client Environment:

The Diskless Client will be called ws009.

The Linux Server Side :

1. Find your Client ( ws009 ) Display card Model and his Ethernet mac address and write them down, you will need them later.

2. Download and install the Following packages from http://www.ltsp.org :

ltsp_core-X.X-X.rpm
ltsp_kerne-X.X-X.rpm
ltsp_x_core-X.X-X.rpm
ltsp_x_fonts-X.X-X.rpm

3. Install the rdesktop package from your RedHat CD or Download it form http://www.rdesktop.org/ .

4. Download the wilisystem patch from www.wilisystem.com , and install it .

5. Make sure that the packages for the Dhcp,Nfs,Tftp servers are installed.

6. Edit the file /opt/ltsp/install_scripts/CONFIG and change the settings to match your network Setting.

7. Run /opt/ltsp/templates/ltsp_initialize

# cd /opt/ltsp/templates/ltsp_initialize

# ./ltsp_initialize

8. Copy /etc/dhcpd.conf.example to /etc/dhcpd.conf and check that all the network numbers match your network Configuration.
Check the Mac address of your client and update the client configuration section ( host ws009 ) in the dhcpd.conf file.

Here is my /etc/dhcpd.conf :

ddns-update-style none;

default-lease-time 21600;
max-lease-time 21600;

option subnet-mask 255.255.255.0;
option broadcast-address 192.168.1.255;
option routers 192.168.1.100;
option domain-name-servers 192.168.1.100;
option domain-name “my-domain.com”;
option root-path “192.168.1.100:/opt/ltsp/i386″;

option option-128 code 128 = string;
option option-129 code 129 = text;

shared-network WORKSTATIONS {
subnet 192.168.1.0 netmask 255.255.255.0 {
}
}

group {
use-host-decl-names on;
option log-servers 192.168.1.100;

host ws009 {
hardware ethernet 00:02:B3:2D:B0:D2;
fixed-address 192.168.1.113;
filename “/lts/vmlinuz-2.4.21-ltsp-1″;
}

}

9. Check /etc/exports. check that the IP numbers match your network Configuration. if everything is fine run :

# exportfs -r
# exportfs -a

10. Check that your client is properly listed in /etc/hosts. if your client name is w009 and your domain is my-domain.com you should add a line to your /etc/hosts file like :

192.168.1.112 ws009.my-domain.com ws009 this name (ws009) should be the same as the client name ( host ws009) that you configured in your dhcp.conf

12. Check /opt/ltsp/i386/etc/lts.conf at the end of the file you should see the wilisystem configuration

Here is my Wilisystem Config , I added my remarks for the configuration part:

# Config part for the http://www.wilisystem.com
# example ws009 accessing the W2K/NT4 TSE
[ws009]
RDPSERVER = 192.168.1.3 # The ip of your W2K/NT4 Terminal Server
RUNLEVEL = 7 # runlevel 7 for wilisystem
SERVER = 192.168.1.100 # The IP of your LTSP server
XSERVER = auto # auto Discovery of your Display-card

# if your display card fail in the auto mod, you should download the proper ltsp_x336-XXX from www.ltsp.org and specify it like XSERVER = XF86_Mach64

X_MODE_0 = 1024×768 # The Resolution that you want, ( 1024×768 , 800×600 …)

X_COLOR_DEPTH = 15 # The color Depth .. i think win2k server only support 8 bit (256) color.

# the folowing line configure your mouse , check the Documentation page for more mouse type configuration : http://www.ltsp.org/documentation/

X_MOUSE_PROTOCOL = “PS/2″
X_MOUSE_DEVICE = “/dev/psaux”
X_MOUSE_RESOLUTION = 400
X_MOUSE_BUTTONS = 3

13. Make sure that the tftp service is enabled in the xinetd directory. run :

# service dhcpd restart
# service xinetd restart

# service nfs restart

The verify that the tftp server is running. run : netstat -anp | grep “:69 “

you should get something like : udp 0 0 0.0.0.0:69 0.0.0.0:* 799/xinetd

verify dhcp server by : netstat -anp | grep “:67 “
you should get something like : udp 0 0 0.0.0.0:67 0.0.0.0:* 2086/dhcpd

If dhcp is not working try restarting it .
If tftp is not working then you have to enable tftp in /etc/xinetd.d/tftp and restart it.

14. The default runlevel is specified in /opt/ltsp/i386/etc/lts.conf is runlevel 5 BUT in the wilisystem section it override the default with its own Runlevel 7 ( if you take a look at /opt/ltsp/i386/etc/inittab you will see wilisystem Configuration for this runlevel.). if you exerience problems you should change it. try to load your client with one of the other clients configuration that you have in /opt/ltsp/i386/etc/lts.conf , ws001 is a good start . remember to change your dhcp configuration and your hosts file to match your new host name. and choose the runlevel 3 . this will only load the ltsp system without trying to connect to the Windows Terminal Server.

then you will be able to debug the system.

The Diskless Client Side

1. Get your initial client boot kernel from : http://rom-o-matic.net/
To creat a boot floppy from the image you downloaded run :
# cat eb-5.0.10-yournic.lzdsk > /dev/fd0
where “eb-5.0.10-yournic.lzdsk” is where you stored your downloaded ROM image.

2. Reboot the client with the boot floppy that you created from the boot image.

After The boot process finished ,you should get the Windows logon screen

Problems
=====================

i experienced screen flickers when the X Server was trying to load and failes with message “no screens found ” , it was because the system didnt recognized my display adaptor , which is “mach64″ family , it was solved after I downloaded the proper Xfree 3.3 Drivers from the ltsp site. and I used the ” XSERVER = XF86_Mach64 ” in the lts.conf file.

You must first enable the Remote Desktop feature on your office computer so that you can control it remotely from another computer. You must be logged on as an administrator or a member of the Administrators group to enable Remote Desktop on your Windows XP Professional-based computer.

To setup your office computer to use Remote Desktop

1.	Open the System folder in Control Panel. Click Start, point to Settings, click Control Panel, and then double-click the System icon.
2.	On the Remote tab, select the Allow users to connect remotely to this computer check box, as shown below.
3.	Ensure that you have the proper permissions to connect to your computer remotely, and click OK.
4.	Leave your computer running and connected to the company network with Internet access. Lock your computer, and leave your office.

Note If you’re running Windows XP Service Pack 2 (SP2) and you enable Remote Desktop, Windows Firewall will be automatically configured to allow Remote Desktop connections to your computer. However, Remote Desktop will not work if you have Windows Firewall configured to allow no exceptions. To allow exceptions in Windows Firewall, in the control panel open the Security Center, click Windows Firewall and clear the check box next to Don’t allow exceptions.