Cool, I'm glad it worked. If the switch had shut them down or something if it saw a loop, fixing the server configuration and giving the switch time to clear the STP or whatever else it did was probably all it needed to get going again.
I've accidentally created network loops every now and then, and on a less intelligent switch (some old Linksys switches come to mind) it actually brought the whole office network down... no fun. Cisco switches usually handle it better by finding any loops and will handle things in a way that doesn't flood the whole network with traffic even if it means ignoring particular ports.
Especially if you've modified the switch to tell it certain ports are just computers so that it comes up faster (without doing the CDP phase, if I remember my terminology right... the part where it checks to see if a new connection is a server, router, another switch, etc). If you disabled that by assigning a specific role, but then it saw traffic from a router or switch, I'm not sure what would happen in that case, but probably nothing good... best case is it *would* shut down the ports until they got reconnected?
