Booting wds without wimboot

[chmeyer]

Since I had other problems with this computer I tried a different one (shows the same symptom - like all iPXE tested machines, too).

This one has an intel chipset, too - but it has problems in detecting an disconnected cable with link state as Down.

Anyway:
dhcp works (IP:172.16.0.66)
iPXE> imgfetch tfpt://172.16.0.123/512mb
tftp://172.16.0.123/512mb... 38%

Thats it. Now the download hangs. Sometimes with 61%, sometimes with 9% or 18%.
Seems that download gets stuck or really slow.
1% - 3% - ... 38% took a minute or so and now (it is at 39%) 20 or 30 minutes are gone.
The longest test reached 61% after two hours or so and on the next morning it still got stuck at 61%.

TFTP Server works fine even accessing the internet.
Pinging the tftp client is fine, too:
172.16.0.123$ ping 172.16.0.66
PING 172.16.0.66 (172.16.0.66) 56(84) bytes of data.
64 bytes from 172.16.0.66: icmp_seq=1 ttl=64 time=0.096 ms
64 bytes from 172.16.0.66: icmp_seq=2 ttl=64 time=0.074 ms
64 bytes from 172.16.0.66: icmp_seq=3 ttl=64 time=0.470 ms
64 bytes from 172.16.0.66: icmp_seq=4 ttl=64 time=0.106 ms
64 bytes from 172.16.0.66: icmp_seq=5 ttl=64 time=0.098 ms
64 bytes from 172.16.0.66: icmp_seq=6 ttl=64 time=0.101 ms
64 bytes from 172.16.0.66: icmp_seq=7 ttl=64 time=0.097 ms
64 bytes from 172.16.0.66: icmp_seq=8 ttl=64 time=0.100 ms
64 bytes from 172.16.0.66: icmp_seq=9 ttl=64 time=0.106 ms
64 bytes from 172.16.0.66: icmp_seq=10 ttl=64 time=0.480 ms
64 bytes from 172.16.0.66: icmp_seq=11 ttl=64 time=0.105 ms
64 bytes from 172.16.0.66: icmp_seq=12 ttl=64 time=0.107 ms
^C
--- 172.16.0.66 ping statistics ---
12 packets transmitted, 12 received, 0% packet loss, time 10998ms
rtt min/avg/max/mdev = 0.074/0.161/0.480/0.141 ms

172.16.0.123$ netstat -n | grep 0.66
udp 0 0 172.16.0.123:43796 172.16.0.66:50361 CONNECTED

I thought it could be an issue withe the switch (Level One, showing 1000fdx for the relevant ports - cable test: ok) and replaced it with a smaller TP-Link switch: same issue.

Christian