Jeste me napadlo: WDS (RIS) sice nedela DHCP, ale sedi na stejnem portu (67) jako DHCP. A oba reaguji na DHCP broadcasty i kdyz kazdy posila klientum neco jineho. Je mozne, ze to VPN klientum (ISA serveru) vadi. Da se to obejit vypnutim "poslouchani" WDS na portu 67 a nastavenim spravnych hodnot do options 66 a 67 v DHCP. Mechanismus komunikace DHCP a PXE: http://technet.microsoft.com/en
Kdyz uz se to tu resi.. Muzete mi prosim nekdo rict, kde co mam ve WDS nastavit, aby mi korektne fungoval DHCP server? Jsou dva servery: Server1: ISA2006 + VPN, DB a WDS Server2: AD, DHCP, DNS atd. Problem je, ze pokud mam aktivni WDS sluzbu, tak mi nejakym zpusobem blokuje DHCP pro VPN klienty. Proste neziskaji IP adresu. Mam podezreni, ze WDS ma nejaky "vlastni" DHCP server a tak
He, he... Si to predstavujete prilis jednoduse :) Vetsina dnesnich sitovych karet podporuje PXE. Pro jeho fungovani potrebujete spravne nastaveny DHCP, ktery PXE podporuje, TFTP server a nejaky image, ktery budete bootovat. Pokud chcete instalovat Windows PC ze site, muzete pouzit RIS, nebo noveji WDS, ktere jsou soucasti instalace Windows Serveru. Pokud si chcete bootovat "jen tak neco"
Package: sympa Severity: wishlist Tags: l10n, patch Hi, in attachement there is updated Czech (cs.po) translation of sympa debconf messages. Please include it with the package. Thanks -- Miroslav Kure # # Translators, if you are not familiar with the PO format, gettext # documentation is worth reading, especially sections dedicated to # this format, e.g. by running:
Package: dtc Severity: wishlist Tags: l10n, patch Hi, in attachement there is updated Czech (cs.po) translation of dtc debconf messages. Please include it with the package. Thanks -- Miroslav Kure # Czech translation of dtc debconf messages. # Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER # This file is distributed under the same license as the dtc package. # Miroslav Kure
