[openthinclient-user] tftp server problem
Hello, Since a couple of days, my tftp server does not seems to work anymore :( A new device comes in the PXE clients list, but when configured it does not boot ! (I get error : PXE-E32: TFTP open timeout) Do you have any idea ? Can you tell me how can I trace the problems ? Thx, Christophe This communication and its attachments, if any, may contain confidential and privileged information the use of which by other persons or entities than the intended recipient is prohibited. If you receive this transmission in error, please contact the sender immediately and delete the material from your system. -- ___ The Open Source Thin Client Solution http://openthinclient.org openthinclient-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openthinclient-user
Re: [openthinclient-user] Local boot problem
hi piergiorgio, * regarding local boot: if your server/client VLANs are in a local area network, there is most probably no need for local boot (see previous mail thread OTC server with clients in different subnets) the intended use of local boot is in slow networks (WANs) or where no DHCP server is available. in addition, the local boot package is currently broken in experimental and therefore this package won't work with the openthinclient-server-0.1.3 virtual appliance. if you need localboot, stick with the openthinclient-0.4.5 JAR release. if you need to have all data (OS, applications, ...) locally on your thin client, you have to change the local boot application setting: System files: NFS to System files: Local and reinitialize your thin client storage device (make sure it's booted via PXE when executing the local boot application). The setting System files: NFS will only add boot loader, kernel and initrd to the desired storage device and the root file system will still be on NFS. * regarding boot process is very slow: take a look at SUITE-383 (make sure you are logged in to see all comments): https://issues.openthinclient.org/otc/browse/SUITE-383 cheers, martin Piergiorgio Venuti schrieb: Hi all, I've a Openthinclient server in a VLAN and my thin client in a another VLAN, I set up accordly the LDAP and the NFS server in local boot application, so my client are able to login but the boot process is very slow, about 30 min. If I move the server in the same VLAN of client all works fine, 1 min to login. I set the local boot program as follow: System file: NFS LDAP URL: my server root-address of the NFS: my server/openthinclient home-address of the NFS: my server/home obtain network parameters: automatic over DHCP I don't have any error messages in login phase and in thin client log from Manager console. The DHCP server is in the same VLAN of client so the client get the address but spend a lot of time in TCOS building phase. Is there a way to solve this problem? My server is a quad core processor with 4 Gb of RAM and I try with only one client so I don't think that is a hardware problem. Best regards -- Ing. Piergiorgio Venuti, CCSP GnuPG Key D791168C piergior...@gigasec.org -- ___ The Open Source Thin Client Solution http://openthinclient.org openthinclient-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openthinclient-user
Re: [openthinclient-user] [Openthinclient-user] Automount local devices
hi edv'ler, this problem should only show up in experimental. if you need (non USB) floppy disk and/or (non USB) CD/DVD rom support, please use the current stable release (v0.4.5 as of today). however, would you please file a bug regarding this issue at: https://issues.openthinclient.org/ and select: Affects Version/s: experimental thanks, martin edvler schrieb: Hi, first, i'm using the experimental OTC Packages! USB devices like USB-Flashmedia, USB-CD/DVDRoms or USB-floppydisks are OK and short time after insertion there are mounted well! But there are problems with local (build-in) devices like floppydrives (/dev/fd0) and CD-/DVD-Rom-Drives (/dev/cdrom ...) - If i put in a floppydisk or a CD/DVD-Rom nothing happens... - If i mount the devices on the command promt i.e. (mount /dev/fd0 /media/floppy) the device is working fine... Whats the problem here? I'm too stupid? Best regards edv'ler -- ___ The Open Source Thin Client Solution http://openthinclient.org openthinclient-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openthinclient-user
Re: [openthinclient-user] OTC server with clientsin differentsubnets
Do you have to log in to create a ticket? For some reason I can't log
in.
Brian
-Original Message-
From: Martin Kreiner [mailto:m.krei...@levigo.de]
Sent: Tuesday, May 04, 2010 8:27 AM
To: openthinclient-user@lists.sourceforge.net
Subject: Re: [openthinclient-user] OTC server with clientsin
differentsubnets
hi brian,
regarding your problem:
error in /scripts/nfs-bottom/tcos_squashfs: //root/sfs/base.sfs not
found
i recommend you open a ticket at:
https://issues.openthinclient.org/
so it's way easier to handle attachments and log-files.
regards,
martin
Clarke, Brian schrieb:
Martin,
Sorry to bother you again, but it seems the problems aren't over. It
seems like the client only successfully boots sometimes. Other times
it
stops on the premount faze and gives some errors like error in
/scripts/nfs-bottom/tcos_squashfs: //root/sfs/base.sfs not found
etc...
I also attached the service log which has the last entry ofINFO
|
jvm 1| 2010/05/03 15:44:34 | 15:44:34,814 INFO
[AbstractPXEService]
Expiring expired conversation
Conversation[1/00:23:7d:cb:dd:ab/2127289771]: age=67969,
client=[Client
name=TC3895, description=null, ip=0.0.0.0, location=English
applicationGroups={}, applications={}]
I tried building the OTC server from scratch in case some things got
messed up some how. But the client still only boots properly
periodically. Could this still be related to network communication
issues?
Regards,
Brian
-Original Message-
From: Clarke, Brian
Sent: Monday, May 03, 2010 11:18 AM
To: 'openthinclient-user@lists.sourceforge.net'
Subject: RE: [openthinclient-user] OTC server with clientsin
differentsubnets
Hey Martin,
Seems like we were able to get it working. The network guys said they
used some sort of option to forward the broadcasts, perharps something
similar to the IP helper address system. Anyways, thanks again for the
advice because it seemed to point them in the right direction. I guess
my only other question is, can the OTC server reboot thin clients
remotely without having to log in to each thin client individually?
Regards,
Brian
-Original Message-
From: Clarke, Brian
Sent: Monday, May 03, 2010 8:25 AM
To: 'openthinclient-user@lists.sourceforge.net'
Subject: RE: [openthinclient-user] OTC server with clientsin
differentsubnets
Thanks Martin, I will talk to them again. We actually tried option 66
and 67 with those options and also added a thin client manually, but
for
some reason when I checked the logs the client still wasn't contacting
the OTC server. I will look into these options further and I will get
them to test the IP helper address. Thanks again for your help.
Regards,
Brian Clarke
-Original Message-
From: Martin Kreiner [mailto:m.krei...@levigo.de]
Sent: Monday, May 03, 2010 8:15 AM
To: openthinclient-user@lists.sourceforge.net
Subject: Re: [openthinclient-user] OTC server with clientsin
differentsubnets
hi brian,
i'am pretty sure the concerns of your network admins are unnecessary.
if you have multiple ip helper-addresses defined, any UDP broadcasts
recieved
on the allowed udp ports will be unicasted to EACH of the IP helpers.
as the openthinclient DHCP proxy does not interfere with DHCP servers
it's
absolutely save to add the second ip helper-addresses.
furthermore this is best practice for using DHCP proxies and i've seen
this
setup working dozens of times at more complex otc installations.
however, there is an alternative solution for your problem. apparently
you will
lose the auto-discover feature of openthinclient and you have to add
your
thin clients manually:
you can add two DHCP options to tell your thin client where to boot
from
and
which Network Bootstrap Program (NBP) to use. these options depend on
your DHCP
implementation and should be set to:
next-server/TFTP Boot Server Host (DHCP Option 66):
IP_OR_NAME_OF_YOUR_OTC_SERVER
filename/Bootfile Name (DHCP Option 67):
pxelinux.0 or /pxelinux.0
regards,
martin
Clarke, Brian schrieb:
Thanks again for the reply Martin,
It seems that the network guys had considered this. But, they said
that
since they already have an ip helper-address assigned to the dhcp
server, that if they configured another IP-helper address in the
system,
that the clients would only look to either the DHCP server OR the OTC
server, meaning that both can't be configured at the same time. Does
this sound accurate to you? Perhaps I'll ask them about it again. But
I
was hoping that there were other configurations that we could do, say
on
the DHCP server, that would simply point the clients to the OTC
server.
Let me know what you think.
Regards,
Brian
-Original Message-
From: Martin Kreiner [mailto:m.krei...@levigo.de]
Sent: Monday, May 03, 2010 7:10 AM
To: openthinclient-user@lists.sourceforge.net
Subject: Re: [openthinclient-user] OTC server with
Re: [openthinclient-user] OTC server with clientsin differentsubnets
hi brain,
well, you can't use your mailing list account for the issue tracker and you
have to register first here:
http://openthinclient.org/tiki-register.php
you will then be able to log in to the tracker with the same login and password
you registered for the Wiki.
regards,
martin
Clarke, Brian schrieb:
Do you have to log in to create a ticket? For some reason I can't log
in.
Brian
-Original Message-
From: Martin Kreiner [mailto:m.krei...@levigo.de]
Sent: Tuesday, May 04, 2010 8:27 AM
To: openthinclient-user@lists.sourceforge.net
Subject: Re: [openthinclient-user] OTC server with clientsin
differentsubnets
hi brian,
regarding your problem:
error in /scripts/nfs-bottom/tcos_squashfs: //root/sfs/base.sfs not
found
i recommend you open a ticket at:
https://issues.openthinclient.org/
so it's way easier to handle attachments and log-files.
regards,
martin
Clarke, Brian schrieb:
Martin,
Sorry to bother you again, but it seems the problems aren't over. It
seems like the client only successfully boots sometimes. Other times
it
stops on the premount faze and gives some errors like error in
/scripts/nfs-bottom/tcos_squashfs: //root/sfs/base.sfs not found
etc...
I also attached the service log which has the last entry ofINFO
|
jvm 1| 2010/05/03 15:44:34 | 15:44:34,814 INFO
[AbstractPXEService]
Expiring expired conversation
Conversation[1/00:23:7d:cb:dd:ab/2127289771]: age=67969,
client=[Client
name=TC3895, description=null, ip=0.0.0.0, location=English
applicationGroups={}, applications={}]
I tried building the OTC server from scratch in case some things got
messed up some how. But the client still only boots properly
periodically. Could this still be related to network communication
issues?
Regards,
Brian
-Original Message-
From: Clarke, Brian
Sent: Monday, May 03, 2010 11:18 AM
To: 'openthinclient-user@lists.sourceforge.net'
Subject: RE: [openthinclient-user] OTC server with clientsin
differentsubnets
Hey Martin,
Seems like we were able to get it working. The network guys said they
used some sort of option to forward the broadcasts, perharps something
similar to the IP helper address system. Anyways, thanks again for the
advice because it seemed to point them in the right direction. I guess
my only other question is, can the OTC server reboot thin clients
remotely without having to log in to each thin client individually?
Regards,
Brian
-Original Message-
From: Clarke, Brian
Sent: Monday, May 03, 2010 8:25 AM
To: 'openthinclient-user@lists.sourceforge.net'
Subject: RE: [openthinclient-user] OTC server with clientsin
differentsubnets
Thanks Martin, I will talk to them again. We actually tried option 66
and 67 with those options and also added a thin client manually, but
for
some reason when I checked the logs the client still wasn't contacting
the OTC server. I will look into these options further and I will get
them to test the IP helper address. Thanks again for your help.
Regards,
Brian Clarke
-Original Message-
From: Martin Kreiner [mailto:m.krei...@levigo.de]
Sent: Monday, May 03, 2010 8:15 AM
To: openthinclient-user@lists.sourceforge.net
Subject: Re: [openthinclient-user] OTC server with clientsin
differentsubnets
hi brian,
i'am pretty sure the concerns of your network admins are unnecessary.
if you have multiple ip helper-addresses defined, any UDP broadcasts
recieved
on the allowed udp ports will be unicasted to EACH of the IP helpers.
as the openthinclient DHCP proxy does not interfere with DHCP servers
it's
absolutely save to add the second ip helper-addresses.
furthermore this is best practice for using DHCP proxies and i've seen
this
setup working dozens of times at more complex otc installations.
however, there is an alternative solution for your problem. apparently
you will
lose the auto-discover feature of openthinclient and you have to add
your
thin clients manually:
you can add two DHCP options to tell your thin client where to boot
from
and
which Network Bootstrap Program (NBP) to use. these options depend on
your DHCP
implementation and should be set to:
next-server/TFTP Boot Server Host (DHCP Option 66):
IP_OR_NAME_OF_YOUR_OTC_SERVER
filename/Bootfile Name (DHCP Option 67):
pxelinux.0 or /pxelinux.0
regards,
martin
Clarke, Brian schrieb:
Thanks again for the reply Martin,
It seems that the network guys had considered this. But, they said
that
since they already have an ip helper-address assigned to the dhcp
server, that if they configured another IP-helper address in the
system,
that the clients would only look to either the DHCP server OR the OTC
server, meaning that both can't be configured at the same time. Does
this sound accurate to you? Perhaps I'll ask them about it again. But
I
was hoping that there were other configurations that we could do, say
on
the DHCP server,
