Mar 7 2009 9:41PM GMT
Posted by: Roger Crawford
SBS 2008,
ISA 2004,
ISA 2006
I know I have lagged on finishing this up but it will be coming sorry for the delay but it has been a crazy week and I have not got much done outside of work. One of my clients was adding a new store to their growing list of locations and also they had a main terminal Server go down on Wednesday so that has been part of my crazy week. As they said to Neo in the Matrix you need to unplug man. Well that is what I have done this weekend, was kick back and not do much. My wife left today to visit her dad in AZ with her sister and left me in charge of the boys but who really is in charge.
Til later just Roger
Feb 21 2009 1:59AM GMT
Posted by: Roger Crawford
SBS,
SBS 2008,
ISA 2004,
ISA 2006
In this post we are going to talk about setting up the device sitting in front of your ISA Server either your Basic Router of choice or in this instance I will be using a Sonic Wall device. What you must decide is the IP Range you are going to use for your space between the SonicWall Lan link and the ISA Servers External NIC. Lets use 10.10.1.1 for your ISA Servers External Nics IP and 10.10.1.2 for your Sonic Wall Lan IP and a Subnet of 255.255.255.0
On your ISA Server on the External Nic properties you would define it’s IP as 10.10.1.1 Subnet of 255.255.255.0 and it’s gateway would be 10.10.1.2 this is your Sonic Walls LAN IP. On the Sonic Wall when you have set this up when you go through the setup Wizard the LAN and the WAN IP’s are defined which makes the whole process pretty darn easy. Once this is completed you would login to your SW and go to the Firewall Rules. I am using a Sonic Wall with the Basic Firmware on it and not the Enhanced OS that is a few more steps but for you that are familiar with the OS this will be a snap. You go to the Firewall Rules and Create the Rules for 443 and set it to allow and then from all on the WAN and point this to 10.10.1.1 on the LAN and do the same for Port 25 and Port 987. That is all you have to do on the Sonic Wall now to the ISA Server but the same logic will hold true for whatever type of device you have setting in front of the ISA Server if that is the choice you make. Or if you have nothing in front of this and you can ignore all of this and now on to setting up the ISA Server.
Til later just Roger
Feb 21 2009 1:45AM GMT
Posted by: Roger Crawford
SBS,
SBS 2008,
ISA 2004,
ISA 2006
I know many of you have SBS 2003 Premium with ISA 2004 Server. I know there are those of us that like to use ISA to protect the domain either by itself or in a 2 Layer aapproach. I myself have my clients running a Sonic Wall firewalls out in front of the ISA Server. I will be walking you though the setting up the ISA Server for publishing the pieces of the SBS 2008 Server that you will want to access from the outside world. This is just basic Publishing with ISA Server.
The RWW is basically using the Terminal Server Gateway piece of 2008 Server for the connections into your network clients or servers. One thing you will have to do is export out your SSL cert off the SBS 2008 Server for your remote.domainname.com or whatever you are using for the outside world and then import that into the Server Certificates Personal Store on the ISA Server. This will be applied to your Web Listner on the External NIC of the ISA Server. Also on some you will need to import this into the Intermediate Trusts also as I have had some sites that I have had to do this on.
You can use the Exchange Wizard on the ISA Server to Publish the OWA and Mobile Access and your Exchange Server. I will go into this all in greater detail in more posts on this subject as I walk you through the setting up of the ISA Server to work with the SBS 2008 Server and also your Sonic Wall of like device in front of it all.
Til Later just Roger
Jan 27 2009 1:30PM GMT
Posted by: Roger Crawford
SBS,
SBS 2003,
ISA 2004,
VPN Clients,
Windows Server 2003,
Microsoft Windows
I had a customer who has a SBS 2003 SP1 Server with ISA 2004 who uses a VPN off their client machines to a site that they submit claims too using the ATT Global Dialer. Well I got the sheet from them on Ports and IP’s that needed to be allowed to do there certain parts and got them all added but the workstations still would not connect. They keep getting error 223 VPN port in use. I finally tracked it down to on the SBS Server I had to go to the registry and add Port 4500 to HKey_Local_Machine\system\CurrentControlSet\Service\Tcpip\Parameters in the Reserved Ports and I had to add 4500-4500 and then I could allow a VPN to initiate from the inside out. It seems to be the problem that a certain Windows Update allowed something else to take over this port. Once I defined this as reserved then the Clients was good. When I get the exact article I will post that info also.
Til later just Roger