Re: is normal for a server to have 50 ports open
That reminds me of the other MCSE I always think of when I hear the cert mentioned. It was 2001 and the company I was working for had just consolidated offices into one building. The pinhead in charge decided it was a good opportunity to both eliminate the aging Novell servers and upgrade from NT4 to Server 2000, but we didn't have time to convert the 95B boxes for the migration so they'd move as is. I remember the date because after we fired everything up the Help Desk was living hell. People kept losing drive mappings after logging onto the network, usually in the afternoon. The bright non-certified tech on the network team dug through technet until he found an article that exactly described our problem and gave it to the MCSE. The solution was to edit a registry entry to increase the timeout on a parameter. It seems MS knew their solution was so chatty their work-around was to turn off part of the connection. Windows 2000 would re-establish the connection, but 95 didn't have reconnect built in. But the MSCE didn't want to edit the registry because that was bad juju. So things kept on the way they were. And then the planes hit the towers. So for the first time in days the Help Desk phone stopped ringing. We had time to catch up on the back log and eagerly attacked it, not knowing what was happening out in the real world. Someone finally got to the pin head with the technet article and he overruled the MCSE. And when we all came back to work the next day the lost drive mapping issue was gone. It's not the way most Americans remember 9/11. I only realized what had happened when I got home that night and watched the news. And by that time my brother had already called my parents to tell them he and his wife were alright, although he had had a long walk home.