Skip to main content

New firewall setup

We've moved our firewall duties over to a Cisco router with security features from our old ISA2006 server. It was getting clunky, buggy, and ridiculous. While this new method of ACLs is slightly more complex, it definitely won't have the issues the ISA server had. We're still maintaining our use of ISA for internal stuff, like the web proxy, and we'll be setting it up for DMZ usage as well, eventually. Silly Cisco router can only have 3 FA ports...even though it has the physical capability to run 6 (2 onboard & 2 twin-port cards). Odd that Cisco would do that...I guess force people into the higher-end routers. (yeesh...base 2801 is $3500...then add on some WICs...up around $4500 or more!)

While it'd be great to run it all off the router, we've already gone over our budget with the SAN purchase, so it'd be best not to press our luck.

It's actually quite nice, this setup. I'm looking forward to getting some info from our Cisco guy on proper ACL setup. I learned it back in college, but that was over three years ago, and I haven't touched any of it since then...gets rusty after a while.

It's a shame Terago was awful about all this. They eventually helped us out, but their level 1 techs are expert stonewallers, and not-so-expert networking professionals. Thank goodness our Cisco guy has dealt with these situations before - he was a real champ! What should have been a 1-2 hour job turned into a 3-4-5 hour job, mostly waiting on Terago to call us back. And then, once they had performed the fix we needed, a typo set us back again! 248 mask is different than a 240 mask.... took us a few to figure out why our VPN on 26 wasn't working, but everything below 24 was working. Sheesh!


Popular posts from this blog

DFSR - eventid 4312 - replication just won't work

This warning isn't documented that well on the googles, so here's some google fodder:

You are trying to set up replication for a DFS folder (no existing replication)Source server is 2008R2, 'branch office' server is 2012R2 (I'm moving all our infra to 2012R2)You have no issues getting replication configuredYou see the DFSR folders get created on the other end, but nothing stagesFinally you get EventID 4312:
The DFS Replication service failed to get folder information when walking the file system on a journal wrap or loss recovery due to repeated sharing violations encountered on a folder. The service cannot replicate the folder and files in that folder until the sharing violation is resolved.  Additional Information:  Folder: F:\Users$\\Desktop\Random Folder Name\  Replicated Folder Root: F:\Users$  File ID: {00000000-0000-0000-0000-000000000000}-v0  Replicated Folder Name: Users  Replicated Folder ID: 33F0449D-5E67-4DA1-99AC-681B5BACC7E5  Replication Group…

Fixing duplicate SPNs (service principal name)

This is a pretty handy thing to know:

SPNs are used when a specific service/daemon uses Kerberos to authenticate against AD. They map a specific service, port, and object together with this convention: class/host:port/name

If you use a computer object to auth (such as local service):

If you use a user object to auth (such as a service account, or admin account):

Why do we care about duplicate SPNs? If you have two entries trying to auth using the same Kerberos ticket (I think that's right...), they will conflict, and cause errors and service failures.

To check for duplicate SPNs:
The command "setspn.exe -X

C:\Windows\system32>setspn -X
Processing entry 7
MSSQLSvc/ is registered on these accounts:
CN=SQL Admin,OU=service accounts,OU=resources,DC=company,DC=local

found 1 groups of duplicate SPNs. (truncated/sanitized)

Note that y…

Logstash to Nagios - alerting based on Windows Event ID

This took way longer than it should have to get here's a config and brain dump...

You want to have a central place to analyze Windows Event/IIS/local application logs, alert off specific events, alert off specific situations.  You don't have the budget for a boxed solution.  You want pretty graphs.  You don't particularly care about individual server states.  (see rationale below - although you certainly have all the tools here to care, I haven't provided that configuration)

ELK stack, OMD, NXlog agent, and Rsyslog.  The premise here is as follows:

Event generated on server into EventLogNXlog ships to Logstash inputLogstash filter adds fields and tags to specified eventsLogstash output sends to a passive Nagios service via the Nagios NSCA outputThe passive service on Nagios (Check_MK c/o OMD) does its thing w. alerting
Open Monitoring Distribution, but the real point here is Check_MK (IIRC Icinga uses this...).  It makes Nagios easy to use and main…