subject:"\[openthinclient\-user\] dhcp"

[openthinclient-user] DHCP Error Thinclients

2021-07-20 Thread Benjamin Wilk

Hallo,

seit dem Upgrade auf die Version 2020.2 bekommen wir im DHCP Server folgende 
Meldungen. Mehrmals sekündlich von verschiedensten Thinclients. Kann damit 
jemand etwas anfangen?

Jul 20 11:57:47  dhcpd   dhcp.c:4023: Failed to send 312 byte 
long packet over fallback interface.
Jul 20 11:57:47  dhcpd   send_packet: Host is down
Jul 20 11:57:47  dhcpd   DHCPACK on 192.168.xx.xx to 
00:e0:c5:30:0b:77 (tamarin) via lagg0.805
Jul 20 11:57:47  dhcpd   DHCPREQUEST for 192.168.xx.xx from 
00:e0:c5:30:0b:77 (tamarin) via lagg0.805
Jul 20 11:57:47  dhcpd   reuse_lease: lease age 1593 (secs) 
under 25% threshold, reply with unaltered, existing lease for 192.168.xx.xx

Mit freundlichen Grüßen

Benjamin Wilk
Systemadministrator

--
Taschenkaufhaus GmbH
Karl-Heine-Straße 92
04229 Leipzig

Tel: 0341 - 350 55 77 23
Fax: 0341 - 350 55 77 20
E-Mail: 
benjamin.w...@taschenkaufhaus.de
Internet: www.taschenkaufhaus.de

Geschäftsführer: Steffen Kilian
Ust-IdNr.: DE261045761
Amtsgericht Leipzig, HRB 24287

___
The Open Source Thin Client Solution http://openthinclient.org
openthinclient-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openthinclient-user

[openthinclient-user] dhcp send hostname

2014-06-30 Thread Massimo Balestrieri

  I modified the initrd.imgnbsp;
In the file init i've removed the line HOSTNAME=
and in the ExtraOptions of otcnbsp;HOSTNAME=testthin

and now it works correctly:
Jun 30 10:45:41 dns-dhcp dhcpd: DHCPREQUEST for 192.168.100.142 from
dc:2b:61:2b:32:a2 (testthin) via enp2s5

  Jun 30 10:45:41 dns-dhcp dhcpd: DHCPACK on 192.168.100.142 to
dc:2b:61:2b:32:a2 (testthin) via enp2s5 nbsp;

It's correct way? there is a simple way? It's a bug?
nbsp;
-- 
Responsabile EDP
Massimo Balestrieri
Tel. +39 0521 525311
Fax +39 0521 525369
E-Mail: massimo.balestri...@mag-data.com
Web: www.mag-data.com

--
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
___
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 send hostname

2014-06-30 Thread Hönig , Steffen

Hi Massimo,

it's really funny to read your mails :) What you found is partly a bug ,
partly unfinished business. Originally we intended to test [ -z $HOSTNAME
] whether the variable is set or not, As you experienced, you may force the
Hostname via commandline parameters. But as of yet we didn't complete the
part of the work. If you and the mailinglist like we may open a debate on
 you think it should be done.



2014-06-30 10:59 GMT+02:00 Massimo Balestrieri balestri...@mag-data.com:

   I modified the initrd.imgnbsp;
 In the file init i've removed the line HOSTNAME=
 and in the ExtraOptions of otcnbsp;HOSTNAME=testthin

 and now it works correctly:
 Jun 30 10:45:41 dns-dhcp dhcpd: DHCPREQUEST for 192.168.100.142 from
 dc:2b:61:2b:32:a2 (testthin) via enp2s5

   Jun 30 10:45:41 dns-dhcp dhcpd: DHCPACK on 192.168.100.142 to
 dc:2b:61:2b:32:a2 (testthin) via enp2s5 nbsp;

 It's correct way? there is a simple way? It's a bug?
 nbsp;
 --
 Responsabile EDP
 Massimo Balestrieri
 Tel. +39 0521 525311
 Fax +39 0521 525369
 E-Mail: massimo.balestri...@mag-data.com
 Web: www.mag-data.com


 --
 Open source business process management suite built on Java and Eclipse
 Turn processes into business applications with Bonita BPM Community Edition
 Quickly connect people, data, and systems into organized workflows
 Winner of BOSSIE, CODIE, OW2 and Gartner awards
 http://p.sf.net/sfu/Bonitasoft
 ___
 The Open Source Thin Client Solution http://openthinclient.org
 openthinclient-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/openthinclient-user




-- 
Mit freundlichen Grüßen

Steffen Hönig
--
Development  Support

openthinclient gmbh, Büro Dresden
Frühlingstr. 11, 01099 Dresden, Deutschland
Telefon: +49 35141886215-1
Mobil:   +49 176 99635238
mailto: s.hoe...@openthinclient.com j.fren...@openthinclient.com


openthinclient gmbh
Heilbronner Str. 150, 70191 Stuttgart, Deutschland
Telefon: +49 711 1378636-0
Telefax: +49 711 1378636-9
Amtsgericht Stuttgart: HRB 245 177; USt-ID: DE216017092
Geschäftsführer: Alexander Stecher
http://openthinclient.com
--
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft___
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 Server 2003 and registration of new pxe clients

2013-08-22 Thread Julian Ohm

Hi Nils,

 

i’m still not sure, that i know what you want.

 

You told about clients an server in different (v)lans. If this is really what 
you have, then client and server are not connected. You have to realize a 
connection.

But now I think you mean different subnets, right? If yes, then you also have 
to realize that the client ant server can connect. I think you have to think 
about the right routing. 

As I remember, then you need to set the 060 and 066 option in the dhcp. And 
please check: I think there was an special needed routing option to route the 
pxe signal through different subnets.

 

Mit freundlichem Gruß

 

Julian Ohm

 

--

Ohm  Meyer Immobilien e. K.

Inh. Gabor Sarkany

Schiffbrücke 66

24939 Flensburg

 

Tel.: 0461 / 840 31 0

Fax.: 0461 / 840 31 11

 

HRA 2190 FL

 

Haftungsbeschränkungen/Disclaimer

 

Diese Nachricht enthält vertrauliche Informationen und ist ausschließlich 

für den Adressaten bestimmt. Der Gebrauch durch Dritte ist verboten. Das 

Unternehmen ist nicht verantwortlich für die ordnungsgemäße, vollständige 

oder verzögerungsfreie Übertragung dieser Nachricht. Diese Hinweise gelten 

auch für zukünftige Nachrichten.

This message may contain confidential information and is intended solely 

for the use by the addressee. Use of this communication by others is 

prohibited. The Company is neither liable for the proper and complete 

transmission of the message nor for the delay in its receipt.

 

Von: Bott, Nils [mailto:nb...@doduco.net] 
Gesendet: Donnerstag, 22. August 2013 07:21
An: openthinclient-user@lists.sourceforge.net
Betreff: Re: [openthinclient-user] DHCP Server 2003 and registration of new pxe 
clients

 

Hi,

 

thanks for answer, but thats not the problem. I Know that i need a server 
connection every time, if the client is in the manager evrything also works 
fine. 

 

I try to explain my problem better:

We got a DHCP 2003n Server with 5 Vlans.

We want our IT infrastructur convert from normal pc network to a thin client  
network.

The OTSServer is in VLAN e.g 301.

The DHCP Server also in 301.

 

If i start a PC with PXE the first time in vlan 301, the boot fail of cousre. 
In the managment console of OTCServer now appears the new Client and i can 
configure it. Next boot and it works.

 

My problem is that when i start a other PC with PXE the first time, boot also 
fails but nothing in the managment Console of OTCServer appears.

So what i have to configure on my DHCP Server or Core Switch or waht else that 
the OTCServer discover every try of a PXE Boot in all Vlans. I don’t want to go 
arround the company and write 500 MAC-Address down ;-).

 

Why my Client not known after the first boot by OTCServer. If i added a Client 
manuel it boots, also in different Vlans. Hope you understand my problem.

 

Nils

 

 

Von: Julian Ohm [mailto:j...@ohm-meyer.de] 
Gesendet: Mittwoch, 21. August 2013 19:44
An: openthinclient-user@lists.sourceforge.net
Betreff: Re: [openthinclient-user] DHCP Server 2003 and registration of new pxe 
clients

 

Hi Nils,

 

I'm not sure that i really understand what you want.

 

The Way OTC works (as far as i understood that).

With the first boot the client becomes known by the OTC Server. Heer you decide 
whether the client should use OTC or not. If yes, then you have to configure 
the client weithin the Manager. After that the client becomes the bootfile, his 
operating System, configuration, etc from the otc Server.

 

Thats why the client need the connection to the server everytime it boots. Even 
if you use the install on hard disk as far as i know. Then the Operation System 
is installed, but the configuration still comes from the server.

 

Excuse me for my Bad english. 

 

Julian

Von meinem iPad gesendet


Am 21.08.2013 um 19:10 schrieb Bott, Nils nb...@doduco.net:

Hello,

 

i installed the OTC-Server. If i added manuel a thin client everything works 
fine, even in different vlans.

 

Now my Problem:

If i start a pxe client in the same subnet as the OTC first time, the client 
appear in the pxe-client card of  the managment console, but if i start a pxe 
client in an other vlan nothing appear in the pxe-client card. So how i have to 
configere my dhcp server that every pxe start will registerd by the OTCServer ?

My current configuration at the DHCP 2003 Windows Server:

043 Vendor Specific Info, 01 04 00 00 00 00

060 Client Identefier, PXEClient

066, Boot Server Host Name, my OTC-Server IP

067 Bootfile name pxelinux.0

 

So what i have to fix that every try of pxe boot, special in different vlan as 
the OTC-Server, so that every client after the first boot-try appear in the 
managment console of the OTC-Server.

 

 

Sorry for my bad english, i hope you can understand my problem and it sounds 
friendly.

 

Many thanks for your support in advance

 

With best regards

 

Nils

Re: [openthinclient-user] DHCP Server 2003 and registration of new pxe clients

2013-08-22 Thread Bott, Nils

Hi,

wie ich an der Signatur erkenne ebenfalls deutschsprachig. Das dürfte die Sache 
etwas vereinfachen.

Also, wenn ich einen PC manuell in OTCServer eintrage funktioniert alles 
wunderbar.

Ist nun ein PC dem OTC Server noch völlig unbekannt, so erscheint dieser nach 
dem ersten Start in dem Reiter PXE-Clients auf dem OTC-Server. Dort kann ich 
dann den Client konfigurieren. Diese erste Erkennung funktioniert jedoch nur 
wenn ich die neuen PC im gleichen Netz wie den OTC starte.

Will ich einen PC aus einem anderen Subnet (VLAN) hinzufügen, so stelle ich 
diesen auf PXE. Auf dem Bildschirm erscheint sogar die IP vom OTC-Server, dann 
kommt der Client nicht weiter und gibt mit der Meldung Could not found kernel 
image : linux auf.
Das Problem ist nun das dieser PXE-Boot versuch nicht vom OTCServer registriert 
wird, also der PC nicht im Reiter PXE-Client auf dem OTCServer erscheint. Die 
einzige Möglichkeit bisher ist dann im OTC den Client mit MAC manuell 
einzutragen.
Wie bekomme ich es nun hin das der OTCServer auch die PXE start versuche in 
anderen subnetzten mitbekommt ?

Zur Infrastruktur:

DHCP Server  Netz 10.10.10.5 /24VLAN 01
OTCServer  Netz 10.10.10.15 / 24 VLAN 01

Dann gibt es einen Core Switch der alle Netze miteinander verbindet ( Master 
Router )
Client Netz 1 10.10.11.0 /24VLAN02
Client Netz 2 10.10.12.0 /24VLAN03 ………. Und so weiter.

Wenn ich einen PXE boot versuche wird dieser nur im VLAN 01 erkannt.
Wenn ich einen Client manuell dem OTCServer hinzufügen kann ich aus allen 
Netzen booten.
DHCP Einstellungen:

043 Vendor Specific Info, 01 04 00 00 00 00
060 Client Identefier, PXEClient
066, Boot Server Host Name, my OTC-Server IP
067 Bootfile name pxelinux.0

Ich denke einmal das ich irgendwie einen Relay Agent oder ip-helperAddress 
benötige um den broadcast der beim ersten boot versuch gesendet wird bis zum 
OTCServer geleitet zu bekommen.

Mit freundlichen Grüßen

Nils

Von: Julian Ohm [mailto:j...@ohm-meyer.de]
Gesendet: Donnerstag, 22. August 2013 08:18
An: openthinclient-user@lists.sourceforge.net
Betreff: Re: [openthinclient-user] DHCP Server 2003 and registration of new pxe 
clients

I found an older mail from Jörn Frenzel. Here what he wrote for the dhcp 
settings:


# DHCP options 66/67

option tftp-server-name MailScanner Warnung: nummerische Links sind 
 oftmals arglistig: http://192.168.1.130:80http://192.168.1.130:80;

option bootfile-name ./pxelinux.0;

Mit freundlichem Gruß

Julian Ohm

--
Ohm  Meyer Immobilien e. K.
Inh. Gabor Sarkany
Schiffbrücke 66
24939 Flensburg

Tel.: 0461 / 840 31 0
Fax.: 0461 / 840 31 11

HRA 2190 FL

Haftungsbeschränkungen/Disclaimer

Diese Nachricht enthält vertrauliche Informationen und ist ausschließlich
für den Adressaten bestimmt. Der Gebrauch durch Dritte ist verboten. Das
Unternehmen ist nicht verantwortlich für die ordnungsgemäße, vollständige
oder verzögerungsfreie Übertragung dieser Nachricht. Diese Hinweise gelten
auch für zukünftige Nachrichten.
This message may contain confidential information and is intended solely
for the use by the addressee. Use of this communication by others is
prohibited. The Company is neither liable for the proper and complete
transmission of the message nor for the delay in its receipt.

Von: Bott, Nils [mailto:nb...@doduco.net]
Gesendet: Donnerstag, 22. August 2013 07:21
An: 
openthinclient-user@lists.sourceforge.netmailto:openthinclient-user@lists.sourceforge.net
Betreff: Re: [openthinclient-user] DHCP Server 2003 and registration of new pxe 
clients

Hi,

thanks for answer, but thats not the problem. I Know that i need a server 
connection every time, if the client is in the manager evrything also works 
fine.

I try to explain my problem better:
We got a DHCP 2003n Server with 5 Vlans.
We want our IT infrastructur convert from normal pc network to a thin client  
network.
The OTSServer is in VLAN e.g 301.
The DHCP Server also in 301.

If i start a PC with PXE the first time in vlan 301, the boot fail of cousre. 
In the managment console of OTCServer now appears the new Client and i can 
configure it. Next boot and it works.

My problem is that when i start a other PC with PXE the first time, boot also 
fails but nothing in the managment Console of OTCServer appears.
So what i have to configure on my DHCP Server or Core Switch or waht else that 
the OTCServer discover every try of a PXE Boot in all Vlans. I don’t want to go 
arround the company and write 500 MAC-Address down ;-).

Why my Client not known after the first boot by OTCServer. If i added a Client 
manuel it boots, also in different Vlans. Hope you understand my problem.

Nils


Von: Julian Ohm [mailto:j...@ohm-meyer.de]
Gesendet: Mittwoch, 21. August 2013 19:44
An: 
openthinclient-user@lists.sourceforge.netmailto:openthinclient-user@lists.sourceforge.net
Betreff: Re: [openthinclient-user] DHCP Server 2003 and registration of new pxe 
clients

Hi

Re: [openthinclient-user] DHCP Server 2003 and registration of new pxe clients

2013-08-22 Thread Julian Ohm

Hallo Nils,

 

typischerweise ist die Sprache der Mailinglist englisch. Aber um hier einmal 
Klarheit zu schaffen ist deutsch vielleicht auch ok.

 

Das Problem scheint im pxe/dhcp Datenverkehr zu liegen. Diese Informationen 
sind Broadcast verkehr und dieser wird normal nicht gerouted. Du musst deinen 
Router explizit anweisen dies zu tun.

 

http://support.microsoft.com/kb/257579/en#mtDisclaimer

 

Such mal speziell nach diesem Thema. Du findest sehr viele Beiträge im Netz 
dazu. Es handelt sich um ein ganz normales „Problem“, das aber durchaus lösbar 
ist.

 

Mit freundlichem Gruß

 

Julian Ohm

 

--

Ohm  Meyer Immobilien e. K.

Inh. Gabor Sarkany

Schiffbrücke 66

24939 Flensburg

 

Tel.: 0461 / 840 31 0

Fax.: 0461 / 840 31 11

 

HRA 2190 FL

 

Haftungsbeschränkungen/Disclaimer

 

Diese Nachricht enthält vertrauliche Informationen und ist ausschließlich 

für den Adressaten bestimmt. Der Gebrauch durch Dritte ist verboten. Das 

Unternehmen ist nicht verantwortlich für die ordnungsgemäße, vollständige 

oder verzögerungsfreie Übertragung dieser Nachricht. Diese Hinweise gelten 

auch für zukünftige Nachrichten.

This message may contain confidential information and is intended solely 

for the use by the addressee. Use of this communication by others is 

prohibited. The Company is neither liable for the proper and complete 

transmission of the message nor for the delay in its receipt.

 

Von: Bott, Nils [mailto:nb...@doduco.net] 
Gesendet: Donnerstag, 22. August 2013 08:55
An: openthinclient-user@lists.sourceforge.net
Betreff: Re: [openthinclient-user] DHCP Server 2003 and registration of new pxe 
clients

 

Hi,

 

wie ich an der Signatur erkenne ebenfalls deutschsprachig. Das dürfte die Sache 
etwas vereinfachen.

 

Also, wenn ich einen PC manuell in OTCServer eintrage funktioniert alles 
wunderbar.

 

Ist nun ein PC dem OTC Server noch völlig unbekannt, so erscheint dieser nach 
dem ersten Start in dem Reiter PXE-Clients auf dem OTC-Server. Dort kann ich 
dann den Client konfigurieren. Diese erste Erkennung funktioniert jedoch nur 
wenn ich die neuen PC im gleichen Netz wie den OTC starte.

 

Will ich einen PC aus einem anderen Subnet (VLAN) hinzufügen, so stelle ich 
diesen auf PXE. Auf dem Bildschirm erscheint sogar die IP vom OTC-Server, dann 
kommt der Client nicht weiter und gibt mit der Meldung Could not found kernel 
image : linux auf.

Das Problem ist nun das dieser PXE-Boot versuch nicht vom OTCServer registriert 
wird, also der PC nicht im Reiter PXE-Client auf dem OTCServer erscheint. Die 
einzige Möglichkeit bisher ist dann im OTC den Client mit MAC manuell 
einzutragen.

Wie bekomme ich es nun hin das der OTCServer auch die PXE start versuche in 
anderen subnetzten mitbekommt ?

 

Zur Infrastruktur:

 

DHCP Server  Netz 10.10.10.5 /24VLAN 01

OTCServer  Netz 10.10.10.15 / 24 VLAN 01

 

Dann gibt es einen Core Switch der alle Netze miteinander verbindet ( Master 
Router )

Client Netz 1 10.10.11.0 /24VLAN02

Client Netz 2 10.10.12.0 /24VLAN03 ………. Und so weiter.

 

Wenn ich einen PXE boot versuche wird dieser nur im VLAN 01 erkannt.

Wenn ich einen Client manuell dem OTCServer hinzufügen kann ich aus allen 
Netzen booten.

DHCP Einstellungen:

 

043 Vendor Specific Info, 01 04 00 00 00 00

060 Client Identefier, PXEClient

066, Boot Server Host Name, my OTC-Server IP

067 Bootfile name pxelinux.0

 

Ich denke einmal das ich irgendwie einen Relay Agent oder ip-helperAddress 
benötige um den broadcast der beim ersten boot versuch gesendet wird bis zum 
OTCServer geleitet zu bekommen.

 

Mit freundlichen Grüßen

 

Nils

 

Von: Julian Ohm [mailto:j...@ohm-meyer.de] 
Gesendet: Donnerstag, 22. August 2013 08:18
An: openthinclient-user@lists.sourceforge.net
Betreff: Re: [openthinclient-user] DHCP Server 2003 and registration of new pxe 
clients

 

I found an older mail from Jörn Frenzel. Here what he wrote for the dhcp 
settings:

 

# DHCP options 66/67

option tftp-server-name  http://192.168.1.130:80 MailScanner 
 Warnung: nummerische Links sind oftmals arglistig: http://192.168.1.130:80;;

option bootfile-name ./pxelinux.0;

 

Mit freundlichem Gruß

 

Julian Ohm

 

--

Ohm  Meyer Immobilien e. K.

Inh. Gabor Sarkany

Schiffbrücke 66

24939 Flensburg

 

Tel.: 0461 / 840 31 0

Fax.: 0461 / 840 31 11

 

HRA 2190 FL

 

Haftungsbeschränkungen/Disclaimer

 

Diese Nachricht enthält vertrauliche Informationen und ist ausschließlich 

für den Adressaten bestimmt. Der Gebrauch durch Dritte ist verboten. Das 

Unternehmen ist nicht verantwortlich für die ordnungsgemäße, vollständige 

oder verzögerungsfreie Übertragung dieser Nachricht. Diese Hinweise gelten 

auch für zukünftige Nachrichten.

This message may contain confidential information and is intended solely 

for the use by the addressee. Use of this communication

[openthinclient-user] DHCP Server 2003 and registration of new pxe clients

2013-08-21 Thread Bott, Nils

Hello,

i installed the OTC-Server. If i added manuel a thin client everything works 
fine, even in different vlans.

Now my Problem:
If i start a pxe client in the same subnet as the OTC first time, the client 
appear in the pxe-client card of  the managment console, but if i start a pxe 
client in an other vlan nothing appear in the pxe-client card. So how i have to 
configere my dhcp server that every pxe start will registerd by the OTCServer ?
My current configuration at the DHCP 2003 Windows Server:
043 Vendor Specific Info, 01 04 00 00 00 00
060 Client Identefier, PXEClient
066, Boot Server Host Name, my OTC-Server IP
067 Bootfile name pxelinux.0

So what i have to fix that every try of pxe boot, special in different vlan as 
the OTC-Server, so that every client after the first boot-try appear in the 
managment console of the OTC-Server.


Sorry for my bad english, i hope you can understand my problem and it sounds 
friendly.

Many thanks for your support in advance

With best regards

Nils
--
Introducing Performance Central, a new site from SourceForge and 
AppDynamics. Performance Central is your source for news, insights, 
analysis and resources for efficient Application Performance Management. 
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk___
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 Server 2003 and registration of new pxe clients

2013-08-21 Thread Julian Ohm

Hi Nils,

I'm not sure that i really understand what you want.

The Way OTC works (as far as i understood that).
With the first boot the client becomes known by the OTC Server. Heer you decide 
whether the client should use OTC or not. If yes, then you have to configure 
the client weithin the Manager. After that the client becomes the bootfile, his 
operating System, configuration, etc from the otc Server.

Thats why the client need the connection to the server everytime it boots. Even 
if you use the install on hard disk as far as i know. Then the Operation System 
is installed, but the configuration still comes from the server.

Excuse me for my Bad english. 

Julian

Von meinem iPad gesendet

Am 21.08.2013 um 19:10 schrieb Bott, Nils nb...@doduco.net:

 Hello,
  
 i installed the OTC-Server. If i added manuel a thin client everything works 
 fine, even in different vlans.
  
 Now my Problem:
 If i start a pxe client in the same subnet as the OTC first time, the client 
 appear in the pxe-client card of  the managment console, but if i start a pxe 
 client in an other vlan nothing appear in the pxe-client card. So how i have 
 to configere my dhcp server that every pxe start will registerd by the 
 OTCServer ?
 My current configuration at the DHCP 2003 Windows Server:
 043 Vendor Specific Info, 01 04 00 00 00 00
 060 Client Identefier, PXEClient
 066, Boot Server Host Name, my OTC-Server IP
 067 Bootfile name pxelinux.0
  
 So what i have to fix that every try of pxe boot, special in different vlan 
 as the OTC-Server, so that every client after the first boot-try appear in 
 the managment console of the OTC-Server.
  
  
 Sorry for my bad english, i hope you can understand my problem and it sounds 
 friendly.
  
 Many thanks for your support in advance
  
 With best regards
  
 Nils
 --
 Introducing Performance Central, a new site from SourceForge and 
 AppDynamics. Performance Central is your source for news, insights, 
 analysis and resources for efficient Application Performance Management. 
 Visit us today!
 http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
 ___
 The Open Source Thin Client Solution http://openthinclient.org
 openthinclient-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/openthinclient-user
--
Introducing Performance Central, a new site from SourceForge and 
AppDynamics. Performance Central is your source for news, insights, 
analysis and resources for efficient Application Performance Management. 
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk___
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 newsgroup@virginmedia.com:

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





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

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 mohank@gmail.com:

 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 newsgroup@virginmedia.com:
 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
 --
 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

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 mohank@gmail.com:

 **
 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 a.stec...@openthinclient.com
 *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 newsgroup@virginmedia.com:

  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 j...@ohm-meyer.de
 *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

  --

 --
 AlienVault Unified Security Management (USM) platform delivers complete
 security

Re: [openthinclient-user] dhcp

2013-05-18 Thread Julian Ohm

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
--
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-18 Thread Mohan Kumar

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



--


  --
  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. 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-18 Thread Julian Ohm

After Boot a machine the First time ist looks like nothing happened. But you 
should See an entry in the OTC Manager under 'pxe clients'. If you found this, 
you have to configure that Client (right Click on the Client)

Von meinem iPad gesendet

Am 18.05.2013 um 11:55 schrieb Mohan Kumar mohank@gmail.com:

 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
 
 --
 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. 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. 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-18 Thread 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 mailto:j...@ohm-meyer.de
*To:* openthinclient-user@lists.sourceforge.net
mailto: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 mailto: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
mailto: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. 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. 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

Re: [openthinclient-user] dhcp

2013-05-18 Thread Stecher, Alexander

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 newsgroup@virginmedia.com:

  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 j...@ohm-meyer.de
 *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

  --

 --
 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. Download a free 
 trial.http://p.sf.net/sfu/alienvault_d2d



 ___
 The Open Source Thin Client Solution 
 http://openthinclient.orgopenthinclient-user

Re: [openthinclient-user] dhcp

2013-05-18 Thread Luis R. Barahona

Check your dhcp log , let's see if that computer is evenn communicating
with the server.
On May 18, 2013 2:57 AM, Mohan Kumar mohank@gmail.com 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 j...@ohm-meyer.de
 *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

  --


 --
 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. 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. 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-14 Thread Luis R. Barahona

What device is running DHCP?

You need to let it know with option 60 where to your otc server is.

blogs.technet.com/b/dominikheinz/archive/2011/03/18/dhcp-amp-pxe-basics.aspx
**
Dear sir,

as per

http://openthinclient.org/Quick+Start?bl

just start the manager

connect to the default relm

and boot the pxe machine

openthiclient manager should recognise the pxe machine.

but for me it ownt recognise why?

i have a question where are the other nodes like clients, etcc..?

your help is appreciated.


Thank you.

Mohan

--
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. 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-14 Thread Mohan Kumar

Dear sir,

i have a tftpd32 dhcp server on other pc.

but idon't see the congif for otc

thank you

Mohan
  - Original Message - 
  From: Luis R. Barahona 
  To: openthinclient-user@lists.sourceforge.net 
  Sent: Tuesday, May 14, 2013 7:12 AM
  Subject: Re: [openthinclient-user] dhcp


  What device is running DHCP?

  You need to let it know with option 60 where to your otc server is.

  blogs.technet.com/b/dominikheinz/archive/2011/03/18/dhcp-amp-pxe-basics.aspx


  Dear sir,

  as per 

  http://openthinclient.org/Quick+Start?bl

  just start the manager

  connect to the default relm 

  and boot the pxe machine 

  openthiclient manager should recognise the pxe machine.

  but for me it ownt recognise why?

  i have a question where are the other nodes like clients, etcc..?

  your help is appreciated. 


  Thank you.

  Mohan

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

[openthinclient-user] DHCP problem?

2011-12-28 Thread symbhu

Hello all,
I am new to this mailing list.
We have few old thin clinets (IBM Netvista) and I was configuring
openthinclient for those.
Information:
--
1) I followed the documents from http://openthinclient.org/admin%27s%20guide
2) I have one DHCP server (only assign IP)
3) openthinclient  software on another server. (no firewall)
4) There is an alternative configuration available in Thin client BIOS, to
specify Boot file source and its profile location (presently not using it,
as i was not sure which path to specify)
Problem:
-
1) After receiving IP form DHCP, thinclients are not able to get PXE
information.
2) openthinclient  server does not get any PXE request from thin client.
3) No log information about the error in openthinclient  server.

Error Message:
-
Boot file server protocol not specified (displayed in verbose screen of
thin client)

Is any information about TFTP server need to be specified in DHCP server.

Regards,
--
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create 
new or port existing apps to sell to consumers worldwide. Explore the 
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev___
The Open Source Thin Client Solution http://openthinclient.org
openthinclient-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openthinclient-user

[openthinclient-user] DHCP Error Thinclients

[openthinclient-user] dhcp send hostname

Re: [openthinclient-user] dhcp send hostname

Re: [openthinclient-user] DHCP Server 2003 and registration of new pxe clients

Re: [openthinclient-user] DHCP Server 2003 and registration of new pxe clients

Re: [openthinclient-user] DHCP Server 2003 and registration of new pxe clients

[openthinclient-user] DHCP Server 2003 and registration of new pxe clients

Re: [openthinclient-user] DHCP Server 2003 and registration of new pxe clients

Re: [openthinclient-user] dhcp

Re: [openthinclient-user] dhcp

Re: [openthinclient-user] dhcp

Re: [openthinclient-user] dhcp

Re: [openthinclient-user] dhcp

Re: [openthinclient-user] dhcp

Re: [openthinclient-user] dhcp

Re: [openthinclient-user] dhcp

Re: [openthinclient-user] dhcp

Re: [openthinclient-user] dhcp

Re: [openthinclient-user] dhcp

[openthinclient-user] DHCP problem?

20 matches

Site Navigation

Mail list logo

Footer information