Posts

Nat rules change after 8.3 upgrade breaks VPN

Normal Nat statment
access-list nonat extended permit ip
nat (inside) 0 access-list nonat-inside
New nat statment
object network vpnpool
subnet
exit
nat (inside,outside) source static any any destination static vpnpool vpnpool
This NAT rule says to keep the source address for anything coming from the internal interface going to the range designated by the vpnpool object while also keeping the destination address the same.
Seems like a strange way of going about this but this is all i have come across so far. Anyone else has a better way please leave a comment.

Microsoft Small Business Server 2008

Microsoft SBS Server 2008 is an excellent solution for small businesses.  However, migrating to SBS 2008 is not that simple.  First things first it is essential that you migrate to a new physical server.  Doing an in place upgrade is a nightmare and I would not attempt to do it.  If you don’t have another server and your current server is of x64 platform then you should create a virtual machine and use a physical to virtual utility to convert your existing machine to a virtual machine.  Once that is done install SBS 2008 from scratch then power up the virtual machine.  You can then migrate over to SBS 2008.
It should also be noted that x64 is becoming the new standard.  It gives you a bus twice as big as its predecessor x86 processing.  That being said Windows Server 2008 requires x64 hardware.  It will not install on x86.
You basically have two choices when it comes to SBS2008 standard or premium.  The main difference is with premium edition you can have 2 servers in the domain.  As where standard was intended to be a single server solution.
Microsoft decided that ISA server would not be included in SBS 2008.  This in my opinion was a good idea.  There are things certain companies are good at and they should stick to their core competencies of things that they can perfect.  Cisco owns Microsoft when it comes to networking/firewall’s and Microsoft has better server solutions.  Do yourself a favor and do not try to use a “software” firewall solution.  Use a Cisco ASA 5505 or model that fits your needs.
SBS 2008 also has a built in web interface for connecting to your PC at work.  I believe RDP is the way to go for employees accessing your network remotely.  The reason being is their PC acts as a dumb terminal and they can see and feel their desktop as if they were sitting at it.  VPN solutions also known as virutal private networks are over rated.  When a client VPN’s from home they basically connect their PC to your internal networking.  Meaning that if their PC is compromised their attacker basically has a door to your network.  Since it is almost impossible to control employees’ PC’s at home it is inevitable at some point they will get a virus or spyware.  If you remember this is how Microsoft’s network was compromised a few years back. 
Also with the premium edition you have the ability to install SQL 2008 standard.  This is not an option with standard.
The steps for migrating from SBS 2003 are as follows:
Always run backups on your existing server first before doing anything.  This is vital.
Next go to Windows Updates and make sure you upgraded and installed all service packs and updates.
You must now raise the function level of your SBS 2003 domain that can be done by first demoting any NT4 or Windows 2000 domain controllers(if you have any).  Once that is complete Go to active directory domains and trust.  Right click on your domain and select raise domain functional level to 2003.  You must also upgrade the forest functional level to 2003.  This can be done by staying in the console and right clicking on active directory domains and trusts select raise forest functional level.
I would recommend next that you have all of your users go into Outlook.  Tell them to go to tools and empty recycle bin.  This will free up tons of space worth of trash.  It will help make your migration faster.
Make sure your source server has the correct time as this is essential:  w32tm /config /syncfromflags:domhier /reliable:no /update
net stop w32time
net start w32time
Make sure your domain is in native mode and not mixed
Next prepare your server by inserting the 2008 SBS DVD.  Go to tools click sourcetool and run it.  You are going to need an answer file for this which can be created by running SBSAfg.exe on the SBS 2008 DVD.
Keep in mind you must remove the source server.  You have 21 days.
When you install the new server make sure your answer file is on a USB drive.  It will be auto detected as long as it is in the source of any drive.  If it successfully detected after you answer all the Windows server 2008 questions you will get a start the migration page. 
To migrate Exchange 2003 to Exchange 2008 I would recommend you have all your users create a backup PST from Outlook.  This way you have local copies of your data.  Once that is complete then on the migration wizard home page click migrate exchange mailboxes and settings.  Follow the steps outlined.

Backup and restore the config on an ASA/Pix using a TFTP server

First thing you need to do is find a free TFTP server there are piles of them out there as a simple google search for TFTP server will show.
First console, telnet, or ssh into your ASA device then issue the following commands
en
<enter your enable password>
conf t
<enter your configure terminal password>
copy startup-config tftp
A prompt will come up “Address or name of remote host []? 
Type in the ip address of the TFTP server you initially setup. 
Next prompt is “Destination filename [startup-config]?
Leave this field just hit <enter>
Congrats you’ve just backed up your config.
 
Now for the restore process:
en
<enter your enable password>
conf t
<enter your configure terminal password>
copy tftp startup-config
Address or name of remote host []?
Type in your IP here of your local computer where you installed the TFTP server
Source filename []?
In the first process we left the filename at default so it should be startup-config
You should see something like this
Accessing tftp://172.16.11.50/startup-config…!!
Writing system file…
!!
5277 bytes copied in 0.470 secs
That’s all there is to it now just issue the command reload and your ASA will reboot to the startup config which we just copied.  It should be noted you have not restored until you issue the reload command because you’re still running the running image not the startup one that we’ve copied over.