pxe boot

вобщем так.
стаяла не тужила мандрива 2008.0 и была там насторена загрузка тонкого клиента по сети.
со сменой винта решил постaвить 2009.1

и тут начались глюки.
клиент перестал грузиться.

собственно встает на моменте получения pxelinux.0 потом говарит timeout tftp.

хотя из под офтопика tftp 192.168.0.1 get pxelinux.0 прокатывает
но файлы почему то разной длинны!

собственно куда копать? уже моск в конвульсиях


cat /etc/dhcpd.conf
subnet 192.168.0.0 netmask 255.255.255.0 {
# default gateway
option routers 192.168.0.1;
option subnet-mask 255.255.255.0;
option domain-name "*****.**";
option domain-name-servers 192.168.0.1;
range dynamic-bootp 192.168.0.2 192.168.0.9;
default-lease-time 21600;
max-lease-time 43200;
}

host sleem {
next-server 192.168.0.1;
hardware ethernet 00:11:5b:e2:f8:41;
fixed-address 192.168.0.4;
filename "pxelinux.0";
option vendor-encapsulated-options 09:0f:80:00:0c:4e:65:74:77:6f:72:6b:20:62:6f:6f:74:0a:07:00:50:72:6f:6d:70:74:0 6:01:02:08:03:80:00:00:47:04:80:00:00:00:ff;
}


#tcpdump -i eth0 | grep 192.168.0.4
03:07:50.754177 IP 192.168.0.4.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:11:5b:e2:f8:41 (oui Unknown), length 548
03:07:51.795994 ARP, Request who-has server tell 192.168.0.4, length 46
03:07:51.796187 IP 192.168.0.4.2070 > server.tftp: 27 RRQ "pxelinux.0" octet tsize 0
03:07:51.797041 IP server.55342 > 192.168.0.4.2070: UDP, length 14
03:07:51.797225 IP 192.168.0.4.2070 > server.55342: UDP, length 17
03:07:51.797250 IP 192.168.0.4.2071 > server.tftp: 32 RRQ "pxelinux.0" octet blksize 1456
03:07:51.798092 IP server.37605 > 192.168.0.4.2071: UDP, length 15
03:07:51.798277 IP 192.168.0.4.2071 > server.37605: UDP, length 4
03:07:51.798357 IP server.37605 > 192.168.0.4.2071: UDP, length 1460
03:07:51.798363 IP server > 192.168.0.4: udp
03:07:52.799494 IP server.37605 > 192.168.0.4.2071: UDP, length 1460
03:07:52.799503 IP server > 192.168.0.4: udp
03:07:54.801543 IP server.37605 > 192.168.0.4.2071: UDP, length 1460
03:07:54.801547 IP server > 192.168.0.4: udp
03:07:56.796814 ARP, Request who-has 192.168.0.4 tell server, length 28
03:07:56.796998 ARP, Reply 192.168.0.4 is-at 00:11:5b:e2:f8:41 (oui Unknown), length 46
03:07:58.804833 IP server.37605 > 192.168.0.4.2071: UDP, length 1460
03:07:58.804838 IP server > 192.168.0.4: udp
03:08:06.812878 IP server.37605 > 192.168.0.4.2071: UDP, length 1460
03:08:06.812884 IP server > 192.168.0.4: udp
03:08:22.828924 IP server.37605 > 192.168.0.4.2071: UDP, length 1460
03:08:22.828930 IP server > 192.168.0.4: udp
03:08:23.065822 IP server.microsoft-ds > 192.168.0.4.1026: Flags [P.], ack 1, win 10720, length 4SMB-over-TCP packet:(raw data or continuation?)
03:08:27.828312 IP 192.168.0.4.2072 > server.tftp: 32 ACK block 0
03:08:27.828814 ARP, Request who-has 192.168.0.4 tell server, length 28
03:08:27.828990 ARP, Reply 192.168.0.4 is-at 00:11:5b:e2:f8:41 (oui Unknown), length 46
03:09:39.838634 IP 192.168.0.4.2073 > server.tftp: 32 ACK block 0
03:10:23.065822 IP server.microsoft-ds > 192.168.0.4.1026: Flags [P.], ack 1, win 10720, length 4SMB-over-TCP packet:(raw data or continuation?)
03:10:28.065812 ARP, Request who-has 192.168.0.4 tell server, length 28
03:10:28.065989 ARP, Reply 192.168.0.4 is-at 00:11:5b:e2:f8:41 (oui Unknown), length 46