This patch fixes a problem I had with a client who was getting DHCP request retries with our network device and their DHCP server.

It turns out that their Windows Server 2003 DHCP server couldn't handle fast DHCP transactions and it just "forgets" some of them. I verified this with my own Windows Server 2003 install and a network analyser (Ethereal/Wireshark). It seems that a small, lean 200MHz embedded system is too fast for a Windows Server 2003 system running on a 2GHz+ machine. Go figure.

Adding a small (50ms) delay fixes this problem nicely and it only adds a small amount of overhead in comparison to the DHCP request timeouts and retries.

NOTE: This patch is ported from my old 1.1.3 U-Boot system. I have not retested it with 1.3.2 U-Boot against Windows Server 2003. The patch is very small and simple, so I don't think should be necessary.

I can retest this functionality if you wish, but it will require me to reinstall Windows Server and set everything up again.

Aras

______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________

* added option CONFIG_BOOTP_DHCP_REQUEST_DELAY. This provides an optional delay before sending "DHCP Request" in net/bootp.c. Required to overcome interoperability problems with Windows Server 200x DHCP server when U-Boot client responds too fast for server to handle.