Re: [Thinstation-portuguese] Thinclient boot PXE Ts 2008 R2
Brought to you by:
doncuppjr
From: Daian C. <da...@op...> - 2011-02-25 21:11:18
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Estes logs servem sim ............ vamos destrinchar um pouco :D Esta é a sequencia que o cliente busca no server 10.1.1.164 <10.1.1.3> pxelinux.0 10.1.1.164 <10.1.1.3> pxelinux.cfg/56424f58-0000-0000-0000-080027af0 10.1.1.164 <10.1.1.3> pxelinux.cfg/01-08-00-27-af-01-a5 10.1.1.164 <10.1.1.3> pxelinux.cfg/0A0101A4 10.1.1.164 <10.1.1.3> pxelinux.cfg/0A0101A 10.1.1.164 <10.1.1.3> pxelinux.cfg/0A0101 10.1.1.164 <10.1.1.3> pxelinux.cfg/0A010 10.1.1.164 <10.1.1.3> pxelinux.cfg/0A01 10.1.1.164 <10.1.1.3> pxelinux.cfg/0A0 10.1.1.164 <10.1.1.3> pxelinux.cfg/0A 10.1.1.164 <10.1.1.3> pxelinux.cfg/0 10.1.1.164 <10.1.1.3> pxelinux.cfg/default 10.1.1.164 <10.1.1.3> diag/vesamenu.c32 10.1.1.164 <10.1.1.3> pxelinux.cfg/default 10.1.1.164 <10.1.1.3> ts_bg.jpg 10.1.1.164 <10.1.1.3> vmlinuz 10.1.1.164 <10.1.1.3> initrd Aparentemente ele não esta passando do initrd, deve ter alguma coisa ainda na sua imagem que não esta legal, não consegui ver o modelo dos thinclients que esta usando, o link não abre :-( . . . pode ser tmb algum parâmetro que esta configurado em "pxelinux.cfg/default" , outro teste que pode fazer , é gerar uma imagem on-line e salvar o VMLINUZ e o INITRD sobrescrevendo os atuais. Tlvz resolva seu problema com a imagem ;-) Em 25-02-2011 14:23, Myke Lima escreveu: > não sei se serve de alguma coisa mas procurei na net e dei esse comando o > resultado ta abaixo > > > root@SRVDHCP:/etc# tcpdump port 69 -v > > tcpdump: listening on eth1, link-type EN10MB (Ethernet), capture size 96 > bytes > 13:22:04.115738 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto UDP > (17), length 60) > 10.1.1.164.2001 > 10.1.1.3.tftp: 32 RRQ "pxelinux.0" octet blksize 1432 > 13:22:04.232202 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto UDP > (17), length 107) > 10.1.1.164.57089 > 10.1.1.3.tftp: 79 RRQ > "pxelinux.cfg/56424f58-0000-0000-0000-080027af0" [|tftp] > 13:22:04.238420 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto UDP > (17), length 91) > 10.1.1.164.57090 > 10.1.1.3.tftp: 63 RRQ > "pxelinux.cfg/01-08-00-27-af-01-a5" octet tsize > 13:22:04.243420 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto UDP > (17), length 79) > 10.1.1.164.57091 > 10.1.1.3.tftp: 51 RRQ "pxelinux.cfg/0A0101A4" octet > tsize 0 blksize 14 > 13:22:04.248400 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto UDP > (17), length 78) > 10.1.1.164.57092 > 10.1.1.3.tftp: 50 RRQ "pxelinux.cfg/0A0101A" octet > tsize 0 blksize 140 > 13:22:04.253273 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto UDP > (17), length 77) > 10.1.1.164.57093 > 10.1.1.3.tftp: 49 RRQ "pxelinux.cfg/0A0101" octet > tsize 0 blksize 1408 > 13:22:04.258139 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto UDP > (17), length 76) > 10.1.1.164.57094 > 10.1.1.3.tftp: 48 RRQ "pxelinux.cfg/0A010" octet > tsize 0 blksize 1408 > 13:22:04.262880 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto UDP > (17), length 75) > 10.1.1.164.57095 > 10.1.1.3.tftp: 47 RRQ "pxelinux.cfg/0A01" octet > tsize 0 blksize 1408 > 13:22:04.267505 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto UDP > (17), length 74) > 10.1.1.164.57096 > 10.1.1.3.tftp: 46 RRQ "pxelinux.cfg/0A0" octet tsize > 0 blksize 1408 > 13:22:04.272007 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto UDP > (17), length 73) > 10.1.1.164.57097 > 10.1.1.3.tftp: 45 RRQ "pxelinux.cfg/0A" octet tsize > 0 blksize 1408 > 13:22:04.276514 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto UDP > (17), length 72) > 10.1.1.164.57098 > 10.1.1.3.tftp: 44 RRQ "pxelinux.cfg/0" octet tsize 0 > blksize 1408 > 13:22:04.281526 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto UDP > (17), length 78) > 10.1.1.164.57099 > 10.1.1.3.tftp: 50 RRQ "pxelinux.cfg/default" octet > tsize 0 blksize 140 > 13:22:04.293463 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto UDP > (17), length 75) > 10.1.1.164.57100 > 10.1.1.3.tftp: 47 RRQ "diag/vesamenu.c32" octet > tsize 0 blksize 1408 > 13:22:04.394604 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto UDP > (17), length 78) > 10.1.1.164.57101 > 10.1.1.3.tftp: 50 RRQ "pxelinux.cfg/default" octet > tsize 0 blksize 140 > 13:22:04.460384 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto UDP > (17), length 67) > 10.1.1.164.57102 > 10.1.1.3.tftp: 39 RRQ "ts_bg.jpg" octet tsize 0 > blksize 1408 > 13:22:07.410224 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto UDP > (17), length 65) > 10.1.1.164.57103 > 10.1.1.3.tftp: 37 RRQ "vmlinuz" octet tsize 0 > blksize 1408 > 13:22:08.174756 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto UDP > (17), length 64) > 10.1.1.164.57104 > 10.1.1.3.tftp: 36 RRQ "initrd" octet tsize 0 blksize > 1408 > > > Em 25 de fevereiro de 2011 14:11, Myke Lima <cm...@gm...> escreveu: > >> achei somente isso... não achei nada referente a tftp >> >> >> Feb 25 13:03:41 SRVDHCP dhcpd: DHCPREQUEST for 10.1.1.167 (10.1.1.2) from >> 00:40:ca:a8:cc:84 via eth1: lease 10.1.1.167 unavailable. >> Feb 25 13:03:41 SRVDHCP dhcpd: DHCPNAK on 10.1.1.167 to 00:40:ca:a8:cc:84 >> via eth1 >> Feb 25 13:05:30 SRVDHCP dhcpd: DHCPDISCOVER from 08:00:27:af:01:a5 via eth1 >> Feb 25 13:05:31 SRVDHCP dhcpd: DHCPOFFER on 10.1.1.164 to 08:00:27:af:01:a5 >> via eth1 >> Feb 25 13:05:33 SRVDHCP dhcpd: DHCPREQUEST for 10.1.1.150 (10.1.1.135) from >> 08:00:27:af:01:a5 via eth1: unknown lease 10.1.1.150. >> Feb 25 13:05:43 SRVDHCP dhcpd: DHCPDISCOVER from 08:00:27:af:01:a5 via eth1 >> Feb 25 13:05:43 SRVDHCP dhcpd: DHCPOFFER on 10.1.1.164 to 08:00:27:af:01:a5 >> via eth1 >> Feb 25 13:05:45 SRVDHCP dhcpd: DHCPREQUEST for 10.1.1.150 (10.1.1.135) from >> 08:00:27:af:01:a5 via eth1: unknown lease 10.1.1.150. >> Feb 25 13:06:00 SRVDHCP dhcpd: DHCPDISCOVER from 08:00:27:af:01:a5 via eth1 >> Feb 25 13:06:00 SRVDHCP dhcpd: DHCPOFFER on 10.1.1.164 to 08:00:27:af:01:a5 >> via eth1 >> Feb 25 13:06:02 SRVDHCP dhcpd: DHCPREQUEST for 10.1.1.164 (10.1.1.3) from >> 08:00:27:af:01:a5 via eth1 >> Feb 25 13:06:02 SRVDHCP dhcpd: DHCPACK on 10.1.1.164 to 08:00:27:af:01:a5 >> via eth1 >> Feb 25 13:06:45 SRVDHCP dhcpd: DHCPDISCOVER from 00:40:ca:a8:d8:4c via eth1 >> Feb 25 13:06:45 SRVDHCP dhcpd: ICMP Echo reply while lease 10.1.1.163 >> valid. >> Feb 25 13:06:45 SRVDHCP dhcpd: Abandoning IP address 10.1.1.163: pinged >> before offer >> Feb 25 13:06:47 SRVDHCP dhcpd: DHCPREQUEST for 10.1.1.234 (10.1.1.2) from >> 00:40:ca:a8:d8:4c via eth1: unknown lease 10.1.1.234. >> Feb 25 13:07:02 SRVDHCP dhcpd: DHCPDISCOVER from 00:40:ca:a8:d8:4c via eth1 >> Feb 25 13:07:02 SRVDHCP dhcpd: DHCPREQUEST for 10.1.1.234 (10.1.1.2) from >> 00:40:ca:a8:d8:4c via eth1: unknown lease 10.1.1.234. >> Feb 25 13:07:03 SRVDHCP dhcpd: DHCPOFFER on 10.1.1.169 to 00:40:ca:a8:d8:4c >> via eth1 >> Feb 25 13:07:09 SRVDHCP dhcpd: DHCPDISCOVER from 00:40:ca:a8:cf:f5 via eth1 >> Feb 25 13:07:09 SRVDHCP dhcpd: ICMP Echo reply while lease 10.1.1.168 >> valid. >> Feb 25 13:07:09 SRVDHCP dhcpd: Abandoning IP address 10.1.1.168: pinged >> before offer >> Feb 25 13:07:12 SRVDHCP dhcpd: DHCPREQUEST for 10.1.1.166 (10.1.1.2) from >> 00:40:ca:a8:cf:f5 via eth1: lease 10.1.1.166 unavailable. >> Feb 25 13:07:12 SRVDHCP dhcpd: DHCPNAK on 10.1.1.166 to 00:40:ca:a8:cf:f5 >> via eth1 >> Feb 25 13:07:27 SRVDHCP dhcpd: DHCPDISCOVER from 00:40:ca:a8:cf:f5 via eth1 >> Feb 25 13:07:27 SRVDHCP dhcpd: DHCPREQUEST for 10.1.1.166 (10.1.1.2) from >> 00:40:ca:a8:cf:f5 via eth1: lease 10.1.1.166 unavailable. >> Feb 25 13:07:27 SRVDHCP dhcpd: DHCPNAK on 10.1.1.166 to 00:40:ca:a8:cf:f5 >> via eth1 >> Feb 25 13:07:28 SRVDHCP dhcpd: DHCPOFFER on 10.1.1.165 to 00:40:ca:a8:cf:f5 >> via eth1 >> root@SRVDHCP:/var/log# >> >> >> >> Em 25 de fevereiro de 2011 12:15, Daian Conrad <da...@op...>escreveu: >> >> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>> todos os logs, em LSB, ficam em /var/log/(syslog,daemon.log,messages) >>> >>> []s >>> >>> >>> Em 25-02-2011 12:07, Myke Lima escreveu: >>>> desculpe a ignorancia, mas onde ficam os logs do tftp? >>>> >>>> >>>> >>>> >>>> >>>> Em 25 de fevereiro de 2011 11:02, Daian Conrad <da...@op... >>>> escreveu: >>>> >>>> Myke, >>>> >>>> Voce consegue verificar nos logs do tftp alguma informação quando a >>>> maquina cliente inicia ??? >>>> >>>> Tem alguma informação que ainda esta faltando, ficar simplesmente parado >>>> no boot, não explica muita coisa . . . >>>> >>>> Look inside the logs dude ;-) >>>> >>>> >>>> []s >>>> >>>> >>>> Em 25-02-2011 09:51, Myke Lima escreveu: >>>>>>> alguém mais tem idéia do que pode estar acontecendo??? >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> Em 24 de fevereiro de 2011 15:26, Myke Lima <cm...@gm...> >>>> escreveu: >>>>>>> >>>>>>>> alterei recriei a imagem e mesma coisa >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Em 24 de fevereiro de 2011 15:23, Daian Conrad <da...@op... >>>>>>> escreveu: >>>>>>>> >>>>>>>> -----BEGIN PGP SIGNED MESSAGE----- >>>>>>>>> Hash: SHA1 >>>>>>>>> >>>>>>>>> pode ser sim, tem que estar igual >>>>>>>>> >>>>>>>>> >>>>>>>>> Se esta diferente fui eu que errei :) >>>>>>>>> >>>>>>>>> []s >>>>>>>>> >>>>>>>>> >>>>>>>>> Em 24-02-2011 14:41, Myke Lima escreveu: >>>>>>>>>> fiz o procedimento mas esta do mesmo jeito fica parada no >>>>>>>>> pinguinzinhu.... >>>>>>>>>> >>>>>>>>>> uma coisa q eu achei estranha e dei uma olhada no >>>>>>>>> thinstation.conf.buildtime >>>>>>>>>> >>>>>>>>>> esta como sessao rdesktop e no build.conf esta seleciona o >>> rdesktopsvn >>>>>>>>>> >>>>>>>>>> esta certo isso é a mesma coisa? >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Em 24 de fevereiro de 2011 13:00, Myke Lima <cm...@gm...> >>>>>>>>> escreveu: >>>>>>>>>> >>>>>>>>>>> ok, vou testar e posto aqui a principio eu não sei qual a placa >>> de >>>> rede >>>>>>>>> e >>>>>>>>>>> video, mas no servidor antigo de ltsp estava tudo como vesa por >>> isso >>>>>>>>> ate >>>>>>>>>>> deixei o vesa habilitado mas o modelo do thinclient é esse >>>>>>>>>>> http://www.connec.com.br/site/p01b1.asp >>>>>>>>>>> >>>>>>>>>>> <http://www.connec.com.br/site/p01b1.asp> >>>>>>>>>>> >>>>>>>>>>> Em 24 de fevereiro de 2011 11:56, Daian Conrad < >>> da...@op... >>>>>>>>>> escreveu: >>>>>>>>>>> >>>>>>>>>>> -----BEGIN PGP SIGNED MESSAGE----- >>>>>>>>>>>> Hash: SHA1 >>>>>>>>>>>> >>>>>>>>>>>> è possivel que tenha algum problema na configuração da sua >>> imagem de >>>>>>>>>>>> boot(initrd), faltando algum modulo e coisas do tipo. >>>>>>>>>>>> >>>>>>>>>>>> os problemas com modulos são comuns em thinclient's muito novos, >>>> pois >>>>>>>>>>>> ainda estão atualizando o core para versões de kernel mais novos >>> e >>>>>>>>> etc. >>>>>>>>>>>> >>>>>>>>>>>> Qual o modelo do thinclient ou maquina(rede e video) . . . >>>>>>>>>>>> >>>>>>>>>>>> Por via das duvidas dei uma revisada nos seus arquivos e acho >>> que >>>>>>>>> seria >>>>>>>>>>>> interessante testar o RDP com o rdesktop. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Deixei a principio prontosó copiar para a pasta , renomear e >>>>>>>>>>>> compilar(./build) . >>>>>>>>>>>> >>>>>>>>>>>> []s >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Em 24-02-2011 11:39, Myke Lima escreveu: >>>>>>>>>>>>> Ele fica parado na tela toda preta com a seguinte mensagem: >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Loading vmlinuz...................... >>>>>>>>>>>>> Loading initrd..........ready >>>>>>>>>>>>> Uncompressing Linux... Ok, booting the kernel. >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> e não sai disso... >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> sera que tem algo errado na minha imagem meu arquivo build.conf >>> ta >>>>>>>>>>>> certo? >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Em 24 de fevereiro de 2011 11:25, Daian Conrad < >>> da...@op... >>>>>>>>>>>>> escreveu: >>>>>>>>>>>>> >>>>>>>>>>>>> Parece que ele não achou o kernel indicado (vmlinuz ou o >>> initrd), >>>> nos >>>>>>>>>>>>> logs do tftp, não aparece o caminho ou arquivos que a estação >>> esta >>>>>>>>>>>>> procurando ?? >>>>>>>>>>>>> >>>>>>>>>>>>> []s >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Em 24-02-2011 08:54, Myke Lima escreveu: >>>>>>>>>>>>>>>> Bom dia, tenho alguma novidades.. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> consegui fazer o boot mas ainda to com um errinho fiz o >>>> seguinte: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> criei um diretorio na raiz chamado /tftpboot >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> copiei todo conteudo de >>>>>>>>>>>>> /var/lib/tftpboot/Thinstation-2.2.2f/boot-images/pxe >>>>>>>>>>>>>>>> para dentro de /tftpboot >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> depois dei o seguinte comando chmod 777 /tftpboot >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> alterei o dhcpd.conf para seguintes configurações >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> option root-path "/tftpboot"; >>>>>>>>>>>>>>>> filename "pxelinux.0"; >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> certo fui testar ele encontrou o arquivo e começou a dar o >>> boot >>>>>>>>> mas >>>>>>>>>>>> parou >>>>>>>>>>>>> na >>>>>>>>>>>>>>>> seguinte mensagem >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Could not find kernel image: diag/vesamenu.c32 >>>>>>>>>>>>>>>> boot: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> essa mensagem fica aparecendo mais ou menos de uns 5 em 5 >>>> segundos >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> eu olhei e esse arquivo existe na pasta >>>>>>>>>>>>>>>> /tftpboot/pxelinux.cfg/diag/vesamenu.c32 >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> será que eu teria que mover essa pasta diag para >>> /tftpboot/diag >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> alguém tem idéia??? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> 2011/2/23 Daian Conrad <da...@op...> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> o arquivo que precisa ser pego pelo cliente PXE é o >>> pxelinux.0, >>>>>>>>> deve >>>>>>>>>>>>>>>> colocar o caminho pra esse arquivo >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> []s >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Em 23-02-2011 17:23, Myke Lima escreveu: >>>>>>>>>>>>>>>>>>> Em 23 de fevereiro de 2011 17:21, Myke Lima < >>>> cm...@gm... >>>>>>>>>> >>>>>>>>>>>>>>>> escreveu: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> correto entendi, meu arquivo pxelinux.0 esta no seguinte >>>>>>>>>>>> diretorio >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>> /var/lib/tftpboot/Thinstation-2.2.2f/boot-images/pxe/pxelinux.0 >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> então minha config ficou: >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> option root-path "/var/lib/tftpboot"; >>>>>>>>>>>>>>>>>>>> filename >>> "Thinstation-2.2.2f/boot-images/pxe/pxelinux.0"; >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> mas continua com o mesmo erro não encontra o arquivo >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> o que mais poderia estar errado? >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> 2011/2/23 Daian Conrad <da...@op...> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Foi mal cara, não percebi a linha do PXE, tem um caminho >>>> errado >>>>>>>>>>>> ali no >>>>>>>>>>>>>>>>>>> dhcp mesmo. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> filename "boot-images/pxe/pxelinux.0"; >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> esse caminho é para o binario do PXE, voce deve colocar o >>>>>>>>> caminho >>>>>>>>>>>> onde >>>>>>>>>>>>>>>>>>> se encontra o seu, partindo do /var/lib/tftpboot. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> EX.: se o arquivo estiver em >>>>>>>>>>>> /var/lib/tftpboot/pxelinuc.cfg/pxelinux.0 >>>>>>>>>>>>> o >>>>>>>>>>>>>>>>>>> caminho correto seria . . . >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> filename "pxelinux.cfg/pxelinux.0"; >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> []s >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Em 23-02-2011 17:07, Myke Lima escreveu: >>>>>>>>>>>>>>>>>>>>>>> *se for o arquivo esse arquivo >>> /etc/default/tftpd-hpa* >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> a conf dele ta do seguinte maneira: >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> RUN_DAEMON= yes >>>>>>>>>>>>>>>>>>>>>>> TFTP_USERNAME= tftp >>>>>>>>>>>>>>>>>>>>>>> TFTP_DIRECTORY= /var/lib/tftpboot >>>>>>>>>>>>>>>>>>>>>>> TFTP_ADDRESS= 10.1.1.3:69 >>>>>>>>>>>>>>>>>>>>>>> TFTP_OPTION= secure >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> se não for esse arquivo qual seria? >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> 2011/2/23 Daian Conrad <da...@op...> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> provavelmente as configurações do seu tftp devem >>> estar >>>>>>>>>>>> apontando >>>>>>>>>>>>> para >>>>>>>>>>>>>>>>>>>>>>> outro diretorio, jah conferiu isso ? >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> []s >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> Em 23-02-2011 16:34, Myke Lima escreveu: >>>>>>>>>>>>>>>>>>>>>>>>>> hum.. estranho fiz isso e não deu certo >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> ele achou o servidor dhcp atribuiu ip achou o >>> servidor >>>>>>>>> tftp >>>>>>>>>>>> mas >>>>>>>>>>>>>>>> não >>>>>>>>>>>>>>>>>>> achou >>>>>>>>>>>>>>>>>>>>>>> o >>>>>>>>>>>>>>>>>>>>>>>>>> arquivo >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> apareceu as seguintes mensagens: >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> file not foun >>>>>>>>>>>>>>>>>>>>>>>>>> tftp error - file not found >>>>>>>>>>>>>>>>>>>>>>>>>> exiting bootmanage pxe rom >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> e agora? >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> 2011/2/23 Daian Conrad <da...@op...> >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> Só mude a linha abaixo para o diretório correto . >>> . . >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> option root-path "/tftpboot"; >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> para >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> option root-path "/var/lib/tftpboot"; >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> e reiniciar o serviço do dhcp3-server . . . >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> e testar é claro :) >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> []s >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> Em 23-02-2011 15:41, Myke Lima escreveu: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> option root-path "/tftpboot"; >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> - >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>> >>>> >>> ------------------------------------------------------------------------------ >>>>>>>>>>>>>>>>>>>>>>> Free Software Download: Index, Search & Analyze Logs >>> and >>>>>>>>> other >>>>>>>>>>>> IT >>>>>>>>>>>>>>>> data >>>>>>>>>>>>>>>>>>> in >>>>>>>>>>>>>>>>>>>>>>> Real-Time with Splunk. Collect, index and harness all >>> the >>>>>>>>> fast >>>>>>>>>>>>> moving >>>>>>>>>>>>>>>> IT >>>>>>>>>>>>>>>>>>>>>>> data >>>>>>>>>>>>>>>>>>>>>>> generated by your applications, servers and devices >>>> whether >>>>>>>>>>>>> physical, >>>>>>>>>>>>>>>>>>>>>>> virtual >>>>>>>>>>>>>>>>>>>>>>> or in the cloud. Deliver compliance at lower cost and >>>> gain >>>>>>>>> new >>>>>>>>>>>>>>>> business >>>>>>>>>>>>>>>>>>>>>>> insights. http://p.sf.net/sfu/splunk-dev2dev >>>>>>>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>>>>>>> Thinstation-portuguese mailing list >>>>>>>>>>>>>>>>>>>>>>> Thi...@li... >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>> >>>> https://lists.sourceforge.net/lists/listinfo/thinstation-portuguese >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> - >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>> >>>> >>> ------------------------------------------------------------------------------ >>>>>>>>>>>>>>>>>>> Free Software Download: Index, Search & Analyze Logs and >>>> other >>>>>>>>> IT >>>>>>>>>>>> data >>>>>>>>>>>>> in >>>>>>>>>>>>>>>>>>> Real-Time with Splunk. Collect, index and harness all the >>>> fast >>>>>>>>>>>> moving >>>>>>>>>>>>> IT >>>>>>>>>>>>>>>>>>> data >>>>>>>>>>>>>>>>>>> generated by your applications, servers and devices >>> whether >>>>>>>>>>>> physical, >>>>>>>>>>>>>>>>>>> virtual >>>>>>>>>>>>>>>>>>> or in the cloud. Deliver compliance at lower cost and >>> gain >>>> new >>>>>>>>>>>>> business >>>>>>>>>>>>>>>>>>> insights. http://p.sf.net/sfu/splunk-dev2dev >>>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>>> Thinstation-portuguese mailing list >>>>>>>>>>>>>>>>>>> Thi...@li... >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>> >>> https://lists.sourceforge.net/lists/listinfo/thinstation-portuguese >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> - >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>> >>>> >>> ------------------------------------------------------------------------------ >>>>>>>>>>>>>>>> Free Software Download: Index, Search & Analyze Logs and >>> other >>>> IT >>>>>>>>>>>> data in >>>>>>>>>>>>>>>> Real-Time with Splunk. Collect, index and harness all the >>> fast >>>>>>>>> moving >>>>>>>>>>>> IT >>>>>>>>>>>>>>>> data >>>>>>>>>>>>>>>> generated by your applications, servers and devices whether >>>>>>>>> physical, >>>>>>>>>>>>>>>> virtual >>>>>>>>>>>>>>>> or in the cloud. Deliver compliance at lower cost and gain >>> new >>>>>>>>>>>> business >>>>>>>>>>>>>>>> insights. http://p.sf.net/sfu/splunk-dev2dev >>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>> Thinstation-portuguese mailing list >>>>>>>>>>>>>>>> Thi...@li... >>>>>>>>>>>>>>>> >>>>>>>>> >>> https://lists.sourceforge.net/lists/listinfo/thinstation-portuguese >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>> - >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>> >>>> >>> ------------------------------------------------------------------------------ >>>>>>>>>>>>> Free Software Download: Index, Search & Analyze Logs and other >>> IT >>>>>>>>> data >>>>>>>>>>>> in >>>>>>>>>>>>> Real-Time with Splunk. Collect, index and harness all the fast >>>> moving >>>>>>>>> IT >>>>>>>>>>>>> data >>>>>>>>>>>>> generated by your applications, servers and devices whether >>>> physical, >>>>>>>>>>>>> virtual >>>>>>>>>>>>> or in the cloud. Deliver compliance at lower cost and gain new >>>>>>>>> business >>>>>>>>>>>>> insights. http://p.sf.net/sfu/splunk-dev2dev >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> Thinstation-portuguese mailing list >>>>>>>>>>>>> Thi...@li... >>>>>>>>>>>>> >>>> https://lists.sourceforge.net/lists/listinfo/thinstation-portuguese >>>>>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>> - - >>>>>>>>>>>> - >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>> >>>> >>> ------------------------------------------------------------------------------ >>>>>>>>>>>> Free Software Download: Index, Search & Analyze Logs and other >>> IT >>>> data >>>>>>>>> in >>>>>>>>>>>> Real-Time with Splunk. Collect, index and harness all the fast >>>> moving >>>>>>>>> IT >>>>>>>>>>>> data >>>>>>>>>>>> generated by your applications, servers and devices whether >>>> physical, >>>>>>>>>>>> virtual >>>>>>>>>>>> or in the cloud. Deliver compliance at lower cost and gain new >>>>>>>>> business >>>>>>>>>>>> insights. http://p.sf.net/sfu/splunk-dev2dev >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> Thinstation-portuguese mailing list >>>>>>>>>>>> Thi...@li... >>>>>>>>>>>> >>> https://lists.sourceforge.net/lists/listinfo/thinstation-portuguese >>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> - -- >>>>>>>>>>>> ======================= >>>>>>>>>>>> *** Daian Conrad >>>>>>>>>>>> >>>>>>>>>>>> Linux user: #248912 >>>>>>>>>>>> PGP/GPG: 0x7E25E948 >>>>>>>>>>>> >>>>>>>>>>>> ** OpenS Team (DaCoD) >>>>>>>>>>>> E-mail: da...@op... >>>>>>>>>>>> Fone: +55 48 3954-8000 >>>>>>>>>>>> >>>>>>>>>>>> >>> >>>>> >>> >>> - -- >>> ======================= >>> *** Daian Conrad >>> >>> Linux user: #248912 >>> PGP/GPG: 0x7E25E948 >>> >>> ** OpenS Team (DaCoD) >>> E-mail: da...@op... >>> Fone: +55 48 3954-8000 >>> >>> -----BEGIN PGP SIGNATURE----- >>> Version: GnuPG v1.4.10 (GNU/Linux) >>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ >>> >>> iQEcBAEBAgAGBQJNZ8eTAAoJEKPh7Uh+JelIQacH/jLX7pVSLXe06gJamgmEN7Bp >>> QKXaJJqBlkdnfJu+GuiNt+f/AL/Ihl8xtvaknk+Lxdx28ia8PPprQHaUyjUP61vK >>> jmPTgFDH1UxlFKWEf6A0HnNI/RcqjbH77a17GGBzR5rbzIzEyxk7/YpMDyqZLdvo >>> LVqej1gNbcaCIeDQoTSkgiVSzzqEG+lGU7V4SPd4jKteif5I5G2gAhjTHzI1iAcn >>> Lg6mrrorf5gLjMOH7oUUzESGiQCg29NYCtwVy0GzPknM6xM7yaANFa+9OqZM4lVj >>> VBiw5biL4u66ulocFooHsMb1GSZsz+uKpBQXXo6tKHoSeOAX70nQvzmhDR1Id8o= >>> =9z8j >>> -----END PGP SIGNATURE----- >>> >> >> > - -- ======================= *** Daian Conrad Linux user: #248912 PGP/GPG: 0x7E25E948 ** OpenS Team (DaCoD) E-mail: da...@op... Fone: +55 48 3954-8000 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJNaBuoAAoJEKPh7Uh+JelI42cIAJbTQpXt4RVzqsGj+9giybxd Wobl8g7m0K7yB6VbFbqFC0+FOtdhIeR0P6URQt4rko0WXYSOhOpCZOzts1LICAlD LZ/62mxXhlmpW9XzuMDpxQhDvCM4maGjERnSzUVMhrzG+90MxBzkdp3OisxXzht+ Th+uI21zXtA9RJU30td9KXzBJP9hDMbNFetczKDoUCcg7fVBbtQnk9Vj2ObRQ+Wr P8eaQGEc7I3OtUgoJq0XyL1bU9aJeX88VsFPePq+Phh8ugmJr1M70Eoew1Z19Cbb lYWg6NZzGrzjtt/bkLI8qR4bggzLBKhsAsoF87Mu6Giu1Vpp1EgsTEYU/RKM+WI= =k/DC -----END PGP SIGNATURE----- |