Hi Corey,
Some explanations are necessary.
Firstly I am working with a system using a P3 500 Mb RAM Server, with a Dell
Optiplex GX 280 system as client, a 6 port 10/100/1000 Mbps switch and a Belkin
Router which is intended to give me the DHCP serviced required. I have set this
up with a pool of addresses and that is it.
The intention is to see how well this runs with both the Dell Optiplexes and
also with the Dimension 1100's in the same place. These account for the 30
machines in total in the room intended to run OTC.
I guess you have DHCP being provided by another server and hence the options
you can setup.
So far all the testing has been done with a single thin client.
I think you are right about the server and I shall see what else I can get hold
of for the testing.
I am not sure why the above arrangement works on some occasions and not on
others, but following this conversation, shall change the server and see what
happens.
Thank you for your help it has really cleared up a few things for me.
Regards
Dave
________________________________
From: Corey Murtagh <corey.murt...@ourvacationcentre.com>
To: "openthinclient-user@lists.sourceforge.net"
<openthinclient-user@lists.sourceforge.net>
Sent: Thursday, 29 September 2011, 23:48
Subject: Re: [openthinclient-user] Re - Inconsistencies
PXE-E53 happens when the client gets a DHCP response but doesn’t get any
information on the boot server… and maybe a few other reasons. We had this
problem when we started trying to use OTC because our network wasn’t letting
the OTC server see the DHCP requests. I had to setup various options (43, 60,
66, 67) on our DHCP server to tell the thin clients where the server was and
what to ask for. Since then, no E53s.
Have you tried running WireShark on your server to see what’s happening when
you get an E53 error on a client? Can you configure your DHCP server to
provide the PXE information directly instead of relying on the OTC server to
intercept?
As for the slow loads… are they consistently slow across all the machines or
are you only seeing this occasionally? Since the server hosts the file system
for all of the clients there’s a lot of traffic between clients and server,
especially at load time. We tried to setup two subnets on one server (using
DHCP settings) and found some network bottlenecks were causing slow loads
between the subnets. Again, WireShark will give you some insight into what’s
going on there.
I’d also suggest upgrading your OTC server to something with a bit more grunt,
preferably with a nice fast NIC – Gbit if your network supports it. A slow
server or a server with a slow NIC will drive you slowly insane… and after all,
you’re saving on hardware at the terminals J
Regards,
Corey Murtagh
Asia-Pacific IT Support
International, Cruise & Excursion, Inc
Phone: 07 5514 3333 Extn 8197 | Mobile: 0435417766
From:David Wilson [mailto:nenena...@yahoo.co.uk]
Sent: Friday, 30 September 2011 7:51 AM
To: openthinclient-user@lists.sourceforge.net
Subject: [openthinclient-user] Re - Inconsistencies
So what do you want from a Thin Client System ?
Speaking personally, I want a system that behaves similarly every time I switch
it on, it is easy to configure, and has a good performance from the clients
viewpoint - in other words it boots reasonably quickly.
So what am I experiencing with Open ThinClient ?
The good news first....... !
I like the OpenThinClient Manager, although I have some worries which I shall
mention presently.
And the bad news........!
Should it be this slow,and why does it appear to be O.K. one day and then the
following day I will get PXE - E53 No Boot Filename Received error. I have
checked the router and it's indicating it is handing out an IP address.
I have tried to do some research about this and implemented the recommendation
about changing the boot filename to pxelinux.0 and not with the leading slash.
OPenThin Client is I understand listening for the IP address being given then
presumably doing its sixpennyworth or deutchmark and passing over the boot
filename.
I manually changed the filename yesterday and it seemed to work, but then
today, back comes E53 again.
So don't ask me why but I went to Package management and right clicked to
search for updates - it gave me a message about reloading the cache and
immediately afterwards, when I booted the client, the PXE -E53 message was gone
and it booted. ( Why did this clear the error ?)
Well it not so much booted but slithered, because I always have to wait minutes
from the username and password being entered to see a desktop - which once it
reaches here seems to be stable and not that slow! Wow !
So am I getting anywhere......!
I think the answer is that I will tell you tomorrow, especially if E53 appears.
She's part of the family now and of course is a female. I will miss her if she
goes.
If you can throw any light on my problems, and have some suggestions about
getting a more pokier server (P3 currently) and some more RAM (more than the
current 500 Mb) then please contact me in my dark and lonely place.
I would like to hear from you. Remember I only have E53 for company....now 7 of
9 would be better.
I await any communications via the aether,
Regards
Dave
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
The Open Source Thin Client Solution http://openthinclient.org
openthinclient-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openthinclient-user
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
_______________________________________________
The Open Source Thin Client Solution http://openthinclient.org
openthinclient-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openthinclient-user
