Messages

I 'll take it as not possible  

It's possible, just not something I ever enjoy seeing on the corporate network. Makes me all when I see it. Again, it's my job that makes me this way...

I do NAC. My initial response was this:

Upgrading hosting to a virtual private server, since I was starting to max resources available on current hosting plan. Moves will take place behind the scenes during the day today, and should not be noticeable.

Basically, 118 times in the last month, we hit a max resources condition and could either not serve up a page in time or had to kill a process to get a page up. Going with the VPS option will get me dedicated resources and that will get us closer to our "23 nines" uptime goal.

The title of this is so vague, it might as well be "DAAAAMMMNN! THERE BE HAXXORZ!!!"

Yeah, don't be that guy AT ALL. People will start putting you on projects with the worst PMs if you're that guy...

So, basically, the announcement is saying, "IT IS 2018! TURN OFF YOUR TELNET *NOW*!!!"

Man, I wish all HR people were like the guest writer this week...

Also need an application that will randomly block SIP packets leaving my PC when I want to get off a call and can try to claim a bad connection as an excuse.

[HR People We Love]

HR People We Love

In the March 6, 2018 Ask The Headhunter Newsletter, a reader who works in HR makes an impact and a great impression. Sometimes I fear readers think I hate HR. What I hate is what HR has become in a broad sense – highly bureaucratic; overly, counter-productively and inexcusably automated; and too distant from hiring managers and job applicants. (See 6 things HR should stop doing right now in the PBS NewsHour Ask The Headhunter feature.) But I also see some shining lights in HR and I'm tickled to show you one in this week's edition. While it's a rare

The post HR People We Love appeared first on Ask The Headhunter®.

Source: HR People We Love

https://www.peerlyst.com/posts/cybersecurity-journalism-podcast-dean-webb

[one mistake...]

For DHCP boxes, not an issue. Reboot, bounce the port, ipconfig release and renew, all the same. Get a new IP on the flip side.

For network devices, toooooooooooootally different issue.



And for devices that interoperate with the network and client devices (Why hello there, NAC!), you make one mistake... one mistake... and you got a huge mess on your hands.



Sticking with the networking stuff, ask yourself, if an IP address of a management appliance changed or if the IP of a core router/switch changed, where would you have to replicate all those changes to?

I pretty much go with the button on the phone/headset, as it's one that blocks at the device level, so I don't worry about accidentally unmuting with a keyboard combination as I work on email during the call.

And, yes, there are times I do email during a call...   

If you have a mute button, use it.

If you're saying things and everyone ignores you, don't get mad, get off mute.

If you call in with your PC in the same room as a conference room phone that's connected, mute the microphone on your PC.

If you have a headset, use it.

If your headset batteries are low, charge them so that you can use your headset.

Aren't we using loadbalancers in the perimeter?

Yes, but management is concerned about not overloading the loadbalancers... so they put all they loadbalancers behind other loadbalancers.

project funding must have dried up.

That happens, but good news is that we just got our Q1 budget approved. And some server guy has an idea about using NAT for the data center so that the servers keep their public IP addresses, but we do one-to-one static NAT to an RFC 1918 address... What's a nice way of saying