techrecovery | And the Fiery Saga Continues (Reply)

Someone is going to get their arse chewed, and its not me nor is it M. I Copied A on all this.
So, remember that NT box with the null password? My fiery... Well, well, well.

I get a phone message on our message system to call JD (not the J from the intial scenario) to call him concerning our 3 firewalls. Yes, we have 3. I thought we only had 2, but we have three. One for the main system, and 2 designed for us. 1 for my Fiery (which SHOULD have still been there) and 1 strickly for our Ring since we are a remote site. Mind you, I can do AD stuff, set up computers, network computers etc. I am not a sys admin nor a network admin or security expert, other people do that job. I train people, do graphics, and basic tech support with just enough knowledge about other stuff to get me into trouble. (Actually, if they need me to do something, they just send me directions and a direct line to call if I get stuck. I am the here, do this, person at our remote location.)

So, I called him back. Conversations sorta went like this. ( I can't log calls)

JD:Did you guys get any equipment replaced, like a new gateway?
Me: No
JD:Okay, did I ever give you access to the firewalls?
Me: No. We decided since I was not responsible for network security it really wasn't necessary. I can set up computers, add them to the AD, etc.
JD: Have you all had any problems lately?
Me: Well J, from security was bitching about the Fiery again.
JD: Well, that's because the extra firewall I tossed it behind so only you could see it, or anyone at PJ for that matter is gone. You didn't put it in the AD did you?
Me: No. I am the only one who uses it.
JD: Okay, I'll call you right back.

20 mins later

JD: Well, J is a moron.
Me: Why?
JD: Well, he saw all these extra firewalls in your area of the woods, and reconfigured them to match the main campus. What an idiot.
Me: Let me guess, he thought we were on the same ring as you guys. But I thought that wasn't his department?
JD: Yep. He doesn't look at the hierarchy, and forgot you were over 30 miles away, AND it isn't his department necessarily, but he can change stuff, mostly to ADD extra firewalls where needed, not REMOVE them. He may not even realize he removed them.

Me: Let me guess, when he removed (whether accidentally or not) our extra two firewalls, because we are a remote site, he removed the one designed for my Fiery between you guys and M, so M can do their work without having to enter passwords every freaking step AND to keep if from showing blatantly to the outside world.

JD: Yep
Me: Oh, and let me guess, he tried to add it to the AD, so it would automatically get all the updates etc. Even though it is NOT a windows machine per say.
JD: Yep
JD: It'll be fixed by tomorrow.
Me: Well M is calling J.
JD: Ohhh, this is going to be fun. What the hell is a color copier doing with an NT module anywho. Oh, nevermind, its got a box attached to it for print managment and printer file storage and networking doesn't it.

Me: Yep.
JD: The NT module is just so it can network and have a base system for diagnostics.
Me: Yep.
JD: Don't you have 3 networked printers?
Me: Yep
JD: Don't they all use an NT base?
Me: Yep
JD: And he doesn't complain about the other two?
Me: Nope, but the networking part is physcially IN the machine. I invited him up to see it.
JD: You didn't.
Me: Yep, he called while I was waiting for you to return. He said, "Well, I kind of remember something about a copier, but this is a file server. I see all sorts of documents."
JD: Of course he's going to see documents, he's seeing the printer file names.
Me: I know that, you know that, would someone please explain that to him.
JD: Oh, I think both M and I will have a sit down. He's in trouble for removing the firewalls in the first place.
Me: Keep me posted.
JD: Will do.

Now, I am not sure, how they configured the 2 additional firewalls. I do know for some time, my direct IRM person was bitching that they didn't have us up under an additional one for remote sites. At the same time. I did NOT know that's how they solved the fiery box issue nor how they did it. I had an idea, but again, its not my department. There may be more to it. You security knowledgeable people may know differenty, but J was an idiot for reconfiguring what was already there. I mean, it was quiet for close to 8 months this time. But, it would make sense. I am the only one who needs to see it. It is not in the Active Directory. But, apparently, this J guy caused part of his own problem. This is getting interesting.

I love JD, I have been working with him for years. He makes sure I get up to date info. So this is going to be very interesting to see what happens.

The saga continues.