1

https://serverfault.com/questions/584605/dhcp-troubleshooting-client-timeouts/584634#584634

This post was moved to server fault, but the issue was definitely in the switch config. This issue occurs very commonly with Cisco devices and DHCP/PXE.

Does this really not belong on networkengineering?

1
  • 1
    You've assumed that things must be either on-topic for SF or NE. It's possible that questions are on-topic for both sites... indeed, it took me about 20 seconds to find a similar problem on Server Fault. While we might have been able to answer it, consider that we get a fair amount of "please debug my server / computer" questions, and honestly this looked like yet another one of them when I migrated. The safest thing is migrating to Server Fault, because both networking & servers are on-topic
    – Mike Pennington Mod
    Commented Mar 27, 2014 at 15:29

1 Answer 1

Reset to default
1

I think it's in the right place over on Server Fault.

The root cause is the interaction between two features (DHCP and loop-detection/portfast-feature.) Troubleshooting and figuring out what was wrong required much more "server" knowledge than "net eng" knowledge.

Most importantly: SF answered it immediately, and the OP has their solution.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .