Skip to content


Cisco 831 DMZ Port

I discovered something interesting last week while trying to enable communications between two networks.  The Cisco 830 series routers can be configured to have an additional LAN port, allowing you to configure two separate networks instead of the default limitation of 1.  This is done by turning the physical interface fa0/4 into logical interface Ethernet2.

This is an extremely easy configuration:
Router# configure terminal

Router# interface ethernet 2
no shutdown

Your running config will now show a shiny new interface, “Ethernet2″, that can be configured like any other router interface with ip address, etc.

interface Ethernet2           ————–> New port

ip address 1.1.1.1 255.255.255.0

no cdp enable

There are some things to keep in mind though. Since this option was originally only for use as a DMZ port, the speed is limited to 10mbps. Additionally, since this is a logical interface tied to a physical port, if you shut down fa0/4 in your config, then Ethernet2 dies as well.

In a pinch, this is a great way to stretch the functionality of the 830 series.

Posted in Networking.


MCSA: Complete

Finished the last step in my MCSA 2003 track this week.  I opted to use CompTIA’s Security+ as my fourth exam, instead of one of Microsoft’s electives.  The cost was twice as much, but I figured it was a 2 for 1 on certs, and I just couldn’t take any more Microsoft tests.

I definitely came away from the Security+ with a higher opinion of the exam than I had expected going in.  It covered more actual tech than I expected, and I honestly learned a good deal.  I find myself much more interested in security than I have been in the past.  There does seem to be a general theme with CompTIA exams though.  Cisco wants you to know 20 things, but know them better than anything you’ve ever known.  CompTIA prefers that you know 200 things enough to pass the test.

Anyway, MCSA is done, and I’m onto the CCDA exam.

note: CompTIA actually got their CareerID online databases back up after a 4 month downtime (ridiculous).  I can only assume they saw that I scheduled my exam, so the clock was ticking.

Posted in Certs.


Warchalking

I’ve been studying for the Security+ (last step in my MCSA 2003 journey) and came across something interesting.  It’s not new, been around since 2002 apparently, but is a new term for me.  I had long since known about wardialing, and wardriving, but warchalking puts a new spin on things.

In essence, its a way of marking unsecured (and secured, but cracked) WAPs for all the world to see.  They aren’t marked in such a way that just anyone would recognize however.  There’s not a yellow sign saying “free wifi here”.  Instead, it’s based on hobo symbols which have been around since the depression era.  The warchalking signs are rather simplistic, and have never really caught on.  Nevertheless, I find the idea intriguing, and will keep my eyes peeled just in case.WarChalking

Posted in wireless.


MCSA nearing completion: Thoughts so far…

I just finished my third MCSA 2003 exam on Friday morning and I thought I would put down my impressions so far.

  • 70-270 Installing, Configuring, and Administering Windows XP Professional
    • Going into the MCSA I assumed this would be the easiest of the three.  After all, I had been using XP for years now, this should be a cake-walk.  Turns out, this was by far the most difficult of the three.  This test covered topics and techniques for doing things that I would never have dreamed of  (and still don’t really see myself using.)  This turned out to be both the most difficult, and in my opinion, the most useless of the three exams.
  • 70-290 Managing and Maintaining a Windows Server 2003 Environment
    • This exam covered the basics of AD maintenance: OUs, GPOs, basic scripting, etc.  In addition, backup/recovery procedures and RAID were covered.   I felt this was the easiest of the three, but that may be due to my experience playing around in AD on a daily basis.
  • 70-291 Implementing, Managing, and Maintaining a Windows Server 2003 Network Infrastructure
    • I found this test to be middle of the road, but still rather easy.  It covered DNS, DHCP, and Microsoft’s attempts at teaching network subnetting and routing (hehe.)  A large part of the test was also in regards to network troubleshooting (Which the CCNA prepared me for in much greater detail), as well as WSUS.  I have spent more hours than I care to mention on WSUS as of late, so I skipped that chapter altogether and breezed through that section.

What’s next:

I have one more test remaining on the MCSA track.  From the start I had planned for this to be the CompTIA Security+, figured I could get a 2 for 1 deal on certs with this method.   I’m beginning to have seconds thoughts though, as CompTIA’s databases have been down for near two months now.  That’s right….an IT company specializing in IT training has it’s grading, reporting, and information databases OFFLINE for TWO MONTHS.  They are even now requesting that you fax in your results to them to have your results sent to Microsoft for verification.  That’s correct, in the year 2009, my IT cert provider wants me to use a fax machine.  Needless to say, it makes me a bit hesitant to dish out $250 for their exam until they get their act together.  In addition, CompTIA is taking a serious pounding on the IT forums for this, which is only serving to hurt their reputation an lessen the value of the cert.

Posted in Certs.


WSUS Reporters

WSUS 3.0 offers up a solution for those of us looking to hand off some of the administrative duties that accompany administration of Windows Updates, but were hesitant to hand over the reigns to a junior member of the IT team.  The install for WSUS brings with it a local server group named “WSUS Reporters.”  Members of this reporting group are able to open the WSUS console, check on update status, and generate reports for computer/server auditing.  The real beauty of this account is no privileges are granted that would allow the “WSUS Reporter” to approve any updates, or make any changes to machine groups and settings.  This account is exclusively a read-only situation, but will allow the user to view most any setting or configuration that you have previously configured.  This also serves to keep your Desktop Support team in the loop for any patches/updates they should be expecting to be rolled out.

This is an excellent opportunity to hand off some of the more mundane duties of patching. At the same time, you can live without fear that you will wake up the next morning to find your productions servers have a bevy of new untested updates applied, and that the user-community is running the latest build of IE8 and chatting away on Windows Live Messenger.

It is best policy to create a global security group, such as “WSUS_Reporting”, then add this security group to the local “WSUS Reporters” group.  You can then populate this group as needed from your Active Directory Users and Computers snap-in.

Posted in Patching/Updates.