This sounds like a networking issue where the flex can't get an ip address. I believe I have heard others with the same problem and its possible a timing issue with flex networking interface. But honestly because its not affecting others I suspect its cabling or router.
It's complicated but basically the router is timing out before it can determine the physical address of the Flex.
It would take some spelunking into your router and don't know if you are a network guy or not but if you can look up the MAC address for the flex, some routers let you assign an IP to that MAC address. That way there would be no delay and your Flex would get the sam IP ever time.
What model Netgear router are you using ?
See if this link makes any sense to you. It demonstrates how to assign an IP address to a physical MAC address. I think this would solve your problem.
Sounds remotely similar to a problem I had for quite some time, where I constantly had to go in and futz with the network settings after every boot to get the connections going for me. I did a search and found this: (it worked for me... maybe for you too. Nice little Windows esoterica...)
I found this on another website and it worked for me:
"When more than one network connection is available, Windows uses the one with the lowest metric value. By default, it automatically assigns a metric value based on the network connection's rated speed. See An explanation of the Automatic Metric feature for Internet Protocol routes .
To force Windows to use a specific network connection, assign a metric value to each one, giving the lowest value to the desired connection:
- Open the Network Connections folder (Start > Run > ncpa.cpl)
- Right click the desired connection.
- Click Properties > Internet Protocol Version 4.
- Click Properties > Advanced.
- Un-check "Automatic metric".
- Enter a number between 1 and 9999 for the "Interface metric"."