May. 15th, 2009
Oh No You Didn't.
May. 15th, 2009 04:14 pmDear Notworks Group:
We knew you were wrong, and that the fact that none of the West Building terminals could connect to, well, anything was actually a network problem. I did, the PFY did, the Windows Server admin did, the sysadmins did, and I'm pretty sure you did too. You lost any scrap of credibility you had in the first place when, an hour in, we found that indeed there was an entire switch turned off. After that was back in service, don't try and tell us that it's not you any more, when we can ping the gateway for the East Building terminals, but get 36 bytes from 10.95.0.131: Communication prohibited by filter when pinging West--and most especially do not try and say "It's your computer!" when I report the above. Neither should you try and claim it's because the IP address they're using as a primary name server went out of commission Monday, because a) they've been working betwixt then and now, and b) the East building terminals with the same configuration still work.
No love,
Me.
We knew you were wrong, and that the fact that none of the West Building terminals could connect to, well, anything was actually a network problem. I did, the PFY did, the Windows Server admin did, the sysadmins did, and I'm pretty sure you did too. You lost any scrap of credibility you had in the first place when, an hour in, we found that indeed there was an entire switch turned off. After that was back in service, don't try and tell us that it's not you any more, when we can ping the gateway for the East Building terminals, but get 36 bytes from 10.95.0.131: Communication prohibited by filter when pinging West--and most especially do not try and say "It's your computer!" when I report the above. Neither should you try and claim it's because the IP address they're using as a primary name server went out of commission Monday, because a) they've been working betwixt then and now, and b) the East building terminals with the same configuration still work.
No love,
Me.