Re: [openthinclient-user] Tftp error

2013-05-20 Thread Mohan Kumar
Dear friend

how it was working i connot get it work

please give me dhcp, tftp settings

Thankyou
MOhan

- Original Message - 
From: "Moore Jeff" 
To: 
Sent: Monday, May 20, 2013 6:56 PM
Subject: [openthinclient-user] Tftp error


>I have had openthinclient working fine for over a year.all of a
> sudden I am getting tftp error
>
> java = java 7 update 21
> OS = Windows server 2008 r2
> OTC = latest version 1.0.0
>
> 2013-05-20 18:30:57,703 INFO
> [org.openthinclient.tftp.tftpd.TFTPServer] Using blksize=1456
> 2013-05-20 18:30:57,703 INFO
> [org.openthinclient.tftp.tftpd.TFTPServer] TFTP startup took 0
> 2013-05-20 18:31:07,703 INFO
> [org.openthinclient.tftp.tftpd.TFTPServer] TFTP send to
> /xxx.xxx.xxx.xxx:2071 failed.
> java.io.IOException: Failed to transfer file: retries exceeded.
>at 
> org.openthinclient.tftp.tftpd.TFTPServer$TFTPSend.sendAndWaitForACK(TFTPServer.java:418)
>at 
> org.openthinclient.tftp.tftpd.TFTPServer$TFTPSend.run(TFTPServer.java:352)
>
> --
> Try New Relic Now & We'll Send You this Cool Shirt
> New Relic is the only SaaS-based application performance monitoring 
> service
> that delivers powerful full stack analytics. Optimize and monitor your
> browser, app, & servers with just a few lines of code. Try New Relic
> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
> ___
> The Open Source Thin Client Solution http://openthinclient.org
> openthinclient-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/openthinclient-user 


--
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
___
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] Tftp error

2013-05-20 Thread Julian Ohm
Hi

I had such a Problem before. The Solution was to reinstall Java. Then restart 
OTC Service. 

Greets
Julian

Sent from iPhone

Am 21.05.2013 um 03:56 schrieb Moore Jeff :

> I have had openthinclient working fine for over a year.all of a
> sudden I am getting tftp error
> 
> java = java 7 update 21
> OS = Windows server 2008 r2
> OTC = latest version 1.0.0
> 
> 2013-05-20 18:30:57,703 INFO
> [org.openthinclient.tftp.tftpd.TFTPServer] Using blksize=1456
> 2013-05-20 18:30:57,703 INFO
> [org.openthinclient.tftp.tftpd.TFTPServer] TFTP startup took 0
> 2013-05-20 18:31:07,703 INFO
> [org.openthinclient.tftp.tftpd.TFTPServer] TFTP send to
> /xxx.xxx.xxx.xxx:2071 failed.
> java.io.IOException: Failed to transfer file: retries exceeded.
>at 
> org.openthinclient.tftp.tftpd.TFTPServer$TFTPSend.sendAndWaitForACK(TFTPServer.java:418)
>at 
> org.openthinclient.tftp.tftpd.TFTPServer$TFTPSend.run(TFTPServer.java:352)
> 
> --
> Try New Relic Now & We'll Send You this Cool Shirt
> New Relic is the only SaaS-based application performance monitoring service 
> that delivers powerful full stack analytics. Optimize and monitor your
> browser, app, & servers with just a few lines of code. Try New Relic
> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
> ___
> The Open Source Thin Client Solution http://openthinclient.org
> openthinclient-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/openthinclient-user

--
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
___
The Open Source Thin Client Solution http://openthinclient.org
openthinclient-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openthinclient-user


[openthinclient-user] Tftp error

2013-05-20 Thread Moore Jeff
I have had openthinclient working fine for over a year.all of a
sudden I am getting tftp error

java = java 7 update 21
OS = Windows server 2008 r2
OTC = latest version 1.0.0

2013-05-20 18:30:57,703 INFO
[org.openthinclient.tftp.tftpd.TFTPServer] Using blksize=1456
2013-05-20 18:30:57,703 INFO
[org.openthinclient.tftp.tftpd.TFTPServer] TFTP startup took 0
2013-05-20 18:31:07,703 INFO
[org.openthinclient.tftp.tftpd.TFTPServer] TFTP send to
/xxx.xxx.xxx.xxx:2071 failed.
java.io.IOException: Failed to transfer file: retries exceeded.
at 
org.openthinclient.tftp.tftpd.TFTPServer$TFTPSend.sendAndWaitForACK(TFTPServer.java:418)
at 
org.openthinclient.tftp.tftpd.TFTPServer$TFTPSend.run(TFTPServer.java:352)

--
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
___
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] dhcp

2013-05-20 Thread Stecher, Alexander
Did you check, if all required ports are available?
Use e.g. the openthinclient advisor.

--
Alexander Stecher
Dipl.-Ing. (BA)
Telefon: +49 711 1378636-0
Handy: +49 151 2761 2961
mailto:a.stec...@openthinclient.com

openthinclient gmbh, Heilbronner Straße 150, 70191 Stuttgart, Deutschland
Amtsgericht Stuttgart: HRB 245 177; USt-ID: DE216017092
Geschäftsführer: Alexander Stecher
http://openthinclient.com
Am 20.05.2013 12:07 schrieb "Mohan Kumar" :

> **
> Dear friends
>
> i tried the above solutions,
>
> but no luck!
>
> i need to know how can i make sure that
>
> OTC TFTP IS WORKING ?
>
> because i need to specify in DHCP.
>
> TFTP DIR, BOOT FILE ETC..
>
> WHEN I TURN ON THE CLIENT CLIENT COMMUNICATES WITH DHCP, BUT DHCP IS NOT
> COMUNNICATED WITH TFTP TO PASS THE BOOT FILE.
>
> I GET TFTP.
>
> ERROR
>
> Thanks.
>
> - Original Message -
> *From:* Stecher, Alexander 
> *To:* openthinclient-user@lists.sourceforge.net
> *Sent:* Saturday, May 18, 2013 5:28 AM
> *Subject:* Re: [openthinclient-user] dhcp
>
> Usually you don't have to set the option 66 and 67 on the DHCP Server. The
> DHCPproxy functionality from the openthinclient server can handle this -
> like describted above.
> However, please try to change/set in the -> environment -> start option ->
> PXE service
>
> It is usually set to auto, but you can change it manually.
> Restart the openthinclient-service and try it.
>
> --
> Alexander Stecher
> Dipl.-Ing. (BA)
> Telefon: +49 711 1378636-0
> Handy: +49 151 2761 2961
> mailto:a.stec...@openthinclient.com
>
> openthinclient gmbh, Heilbronner Straße 150, 70191 Stuttgart, Deutschland
> Amtsgericht Stuttgart: HRB 245 177; USt-ID: DE216017092
> Geschäftsführer: Alexander Stecher
> http://openthinclient.com
> Am 18.05.2013 14:17 schrieb "Mark D-B" :
>
>>  Dear Mohan et al,
>>
>>   This seems to be something which depends a lot on the DHCP server in
>> use. I run OTC in a VM with the network adaptor in bridged mode. With a
>> TP-Link router doing DHCP, PXE works with no issues. The same is true if I
>> am using named and dhcpd. However, if I use dnsmasq instead then I need to
>> specify both the the OTC server IP address and the boot file name in the
>> configuration file, or PXE fails. Whether OTC would see the new client in
>> these circumstances, I don't know, as the clients had already been added
>> before I changed the network topology.
>>   Mohan - are you in a position where you can use Wireshark on the
>> network? This will allow you to determine which step is failing.
>>
>>   Also, just to be clear, this is a machine which is new to the server
>> which is being PXE'd, yes? When you say that the PXE machine is not
>> recognised, you mean that the machine's IP address is not appearing in the
>> PXE section of the OTC manager display? OTC won't let you actually PXE boot
>> a client until you have authorised it.
>>
>> All the best,
>>
>> Mark
>>
>> On 18/05/13 10:55, Mohan Kumar wrote:
>>
>> Hi
>>
>> Exactly
>>
>> my dhcp server is tfpd32 ver 4..0 with  - ip 192.168.xx.200
>> ip pool---10
>>
>> dns --192.168.xx.1
>>
>> here there is field for boot file --- ?
>>
>>
>> my otc machine ip 192.168.xx.201
>>
>> i just installed and joined default realm.
>>
>> i am trying to boot the third machine via pxe it is not showing any thing.
>>
>> any help is appreciated.
>>
>> i wonder how it works curiosity 1000 %.
>>
>> Thank you
>>
>>
>>
>> - Original Message -
>> *From:* Julian Ohm 
>> *To:* openthinclient-user@lists.sourceforge.net
>> *Sent:* Friday, May 17, 2013 11:48 PM
>> *Subject:* Re: [openthinclient-user] dhcp
>>
>> Hi
>>
>> As i remember you should not set anything. Just configure your dhcp
>> server to provide ip settings. OTC will handle pxe request by his self.
>>
>> Try to deactivate every kind of firewall. And OTC and dhcp must not be on
>> the same Server.
>>
>> Greets
>> Julian
>>
>> Von meinem iPad gesendet
>>
>> Am 18.05.2013 um 06:43 schrieb "Luis R. Barahona" <
>> luis.r.barah...@gmail.com>:
>>
>>  I think you are confused about which option you need to set in dhcp.
>>
>>
>> Option 66 will contain the ip or FQDN of your OTC Server
>>
>>
>> Option 67 will contain the name of your bootfile
>>
>>
>> For OTC you only need to set option 66. Have you done this?
>>
>>
>>
>>
>> --
>> AlienVault Unified Security Management (USM) platform delivers complete
>> security visibility with the essential security capabilities. Easily and
>> efficiently configure, manage, and operate all of your security controls
>> from a single console and one unified framework. Download a free trial.
>> http://p.sf.net/sfu/alienvault_d2d
>>
>>  ___
>> 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] dhcp

2013-05-20 Thread Julian Ohm
I don't know the tftpd32. But perhaps for you it's better to try another dhcp 
server to check where the problem is, dhcp or OTC. or use the vm appliance to 
get everything working without to much work.

Greets
Julian

Von meinem iPad gesendet

Am 20.05.2013 um 11:57 schrieb "Mohan Kumar" :

> Dear friends
>  
> i tried the above solutions,
>  
> but no luck!
>  
> i need to know how can i make sure that
>  
> OTC TFTP IS WORKING ?
>  
> because i need to specify in DHCP.
>  
> TFTP DIR, BOOT FILE ETC..
>  
> WHEN I TURN ON THE CLIENT CLIENT COMMUNICATES WITH DHCP, BUT DHCP IS NOT 
> COMUNNICATED WITH TFTP TO PASS THE BOOT FILE.
>  
> I GET TFTP.
>  
> ERROR
>  
> Thanks.
> - Original Message -
> From: Stecher, Alexander
> To: openthinclient-user@lists.sourceforge.net
> Sent: Saturday, May 18, 2013 5:28 AM
> Subject: Re: [openthinclient-user] dhcp
> 
> Usually you don't have to set the option 66 and 67 on the DHCP Server. The 
> DHCPproxy functionality from the openthinclient server can handle this - like 
> describted above.  
> However, please try to change/set in the -> environment -> start option -> 
> PXE service
> 
> It is usually set to auto, but you can change it manually.
> Restart the openthinclient-service and try it.
> 
> --
> Alexander Stecher
> Dipl.-Ing. (BA)
> Telefon: +49 711 1378636-0
> Handy: +49 151 2761 2961
> mailto:a.stec...@openthinclient.com
> 
> openthinclient gmbh, Heilbronner Straße 150, 70191 Stuttgart, Deutschland
> Amtsgericht Stuttgart: HRB 245 177; USt-ID: DE216017092
> Geschäftsführer: Alexander Stecher
> http://openthinclient.com
> 
> Am 18.05.2013 14:17 schrieb "Mark D-B" :
>> Dear Mohan et al,
>> 
>>   This seems to be something which depends a lot on the DHCP server in use. 
>> I run OTC in a VM with the network adaptor in bridged mode. With a TP-Link 
>> router doing DHCP, PXE works with no issues. The same is true if I am using 
>> named and dhcpd. However, if I use dnsmasq instead then I need to specify 
>> both the the OTC server IP address and the boot file name in the 
>> configuration file, or PXE fails. Whether OTC would see the new client in 
>> these circumstances, I don't know, as the clients had already been added 
>> before I changed the network topology.
>>   Mohan - are you in a position where you can use Wireshark on the network? 
>> This will allow you to determine which step is failing.
>> 
>>   Also, just to be clear, this is a machine which is new to the server which 
>> is being PXE'd, yes? When you say that the PXE machine is not recognised, 
>> you mean that the machine's IP address is not appearing in the PXE section 
>> of the OTC manager display? OTC won't let you actually PXE boot a client 
>> until you have authorised it.
>> 
>> All the best,
>> 
>> Mark
>> 
>> On 18/05/13 10:55, Mohan Kumar wrote:
>>> Hi
>>>  
>>> Exactly
>>>  
>>> my dhcp server is tfpd32 ver 4..0 with  - ip 192.168.xx.200
>>> ip pool---10
>>>  
>>> dns --192.168.xx.1
>>>  
>>> here there is field for boot file --- ?
>>>  
>>>  
>>> my otc machine ip 192.168.xx.201
>>>  
>>> i just installed and joined default realm.
>>>  
>>> i am trying to boot the third machine via pxe it is not showing any thing.
>>>  
>>> any help is appreciated.
>>>  
>>> i wonder how it works curiosity 1000 %.
>>>  
>>> Thank you
>>>  
>>>  
>>> - Original Message -
>>> From: Julian Ohm
>>> To: openthinclient-user@lists.sourceforge.net
>>> Sent: Friday, May 17, 2013 11:48 PM
>>> Subject: Re: [openthinclient-user] dhcp
>>> 
>>> Hi
>>> 
>>> As i remember you should not set anything. Just configure your dhcp server 
>>> to provide ip settings. OTC will handle pxe request by his self.
>>> 
>>> Try to deactivate every kind of firewall. And OTC and dhcp must not be on 
>>> the same Server.
>>> 
>>> Greets
>>> Julian
>>> 
>>> Von meinem iPad gesendet
>>> 
>>> Am 18.05.2013 um 06:43 schrieb "Luis R. Barahona" 
>>> :
>>> 
 I think you are confused about which option you need to set in dhcp.
 
 
 
 Option 66 will contain the ip or FQDN of your OTC Server
 
 
 
 Option 67 will contain the name of your bootfile
 
 
 
 For OTC you only need to set option 66. Have you done this?
 
 --
 AlienVault Unified Security Management (USM) platform delivers complete
 security visibility with the essential security capabilities. Easily and
 efficiently configure, manage, and operate all of your security controls
 from a single console and one unified framework. Download a free trial.
 http://p.sf.net/sfu/alienvault_d2d
 ___
 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] dhcp

2013-05-20 Thread Mohan Kumar
Dear friends 

i tried the above solutions,

but no luck!

i need to know how can i make sure that 

OTC TFTP IS WORKING ?

because i need to specify in DHCP.

TFTP DIR, BOOT FILE ETC..

WHEN I TURN ON THE CLIENT CLIENT COMMUNICATES WITH DHCP, BUT DHCP IS NOT 
COMUNNICATED WITH TFTP TO PASS THE BOOT FILE.

I GET TFTP.

ERROR

Thanks.
  - Original Message - 
  From: Stecher, Alexander 
  To: openthinclient-user@lists.sourceforge.net 
  Sent: Saturday, May 18, 2013 5:28 AM
  Subject: Re: [openthinclient-user] dhcp


  Usually you don't have to set the option 66 and 67 on the DHCP Server. The 
DHCPproxy functionality from the openthinclient server can handle this - like 
describted above.  
  However, please try to change/set in the -> environment -> start option -> 
PXE service

  It is usually set to auto, but you can change it manually.
  Restart the openthinclient-service and try it. 

  --
  Alexander Stecher
  Dipl.-Ing. (BA)
  Telefon: +49 711 1378636-0
  Handy: +49 151 2761 2961
  mailto:a.stec...@openthinclient.com

  openthinclient gmbh, Heilbronner Straße 150, 70191 Stuttgart, Deutschland
  Amtsgericht Stuttgart: HRB 245 177; USt-ID: DE216017092
  Geschäftsführer: Alexander Stecher
  http://openthinclient.com

  Am 18.05.2013 14:17 schrieb "Mark D-B" :

Dear Mohan et al,

  This seems to be something which depends a lot on the DHCP server in use. 
I run OTC in a VM with the network adaptor in bridged mode. With a TP-Link 
router doing DHCP, PXE works with no issues. The same is true if I am using 
named and dhcpd. However, if I use dnsmasq instead then I need to specify both 
the the OTC server IP address and the boot file name in the configuration file, 
or PXE fails. Whether OTC would see the new client in these circumstances, I 
don't know, as the clients had already been added before I changed the network 
topology.
  Mohan - are you in a position where you can use Wireshark on the network? 
This will allow you to determine which step is failing.

  Also, just to be clear, this is a machine which is new to the server 
which is being PXE'd, yes? When you say that the PXE machine is not recognised, 
you mean that the machine's IP address is not appearing in the PXE section of 
the OTC manager display? OTC won't let you actually PXE boot a client until you 
have authorised it.

All the best,

Mark

On 18/05/13 10:55, Mohan Kumar wrote:

  Hi

  Exactly

  my dhcp server is tfpd32 ver 4..0 with  - ip 192.168.xx.200
  ip pool---10

  dns --192.168.xx.1

  here there is field for boot file --- ?


  my otc machine ip 192.168.xx.201

  i just installed and joined default realm.

  i am trying to boot the third machine via pxe it is not showing any thing.

  any help is appreciated.

  i wonder how it works curiosity 1000 %.

  Thank you


- Original Message - 
From: Julian Ohm 
To: openthinclient-user@lists.sourceforge.net 
Sent: Friday, May 17, 2013 11:48 PM
Subject: Re: [openthinclient-user] dhcp


Hi


As i remember you should not set anything. Just configure your dhcp 
server to provide ip settings. OTC will handle pxe request by his self.


Try to deactivate every kind of firewall. And OTC and dhcp must not be 
on the same Server.


Greets
Julian

Von meinem iPad gesendet

Am 18.05.2013 um 06:43 schrieb "Luis R. Barahona" 
:


  I think you are confused about which option you need to set in dhcp. 





  Option 66 will contain the ip or FQDN of your OTC Server




  Option 67 will contain the name of your bootfile




  For OTC you only need to set option 66. Have you done this?



  
--
  AlienVault Unified Security Management (USM) platform delivers 
complete
  security visibility with the essential security capabilities. Easily 
and
  efficiently configure, manage, and operate all of your security 
controls
  from a single console and one unified framework. Download a free 
trial.
  http://p.sf.net/sfu/alienvault_d2d
  ___
  The Open Source Thin Client Solution http://openthinclient.org
  openthinclient-user@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/openthinclient-user





--
AlienVault Unified Security Management (USM) platform delivers complete
security visibility with the essential security capabilities. Easily and
efficiently configure, manage, and operate all of your security controls
from a single console and one unified framework. Down