falconmark

Ok, so if I don't enable DHCP on the netgear, can both servers run DHCP or would that cause a conflict? We also have a Dell PowerConnect 6248p managed switch that they were using previously before I came into the company. I think its not configured properly as our network seems to run very sluggish, even over gigabit connectivity. I checked all the client workstations and they all report 1GB connections. So i'm not sure if its the managed switch, router, cabling, or what. I also want to be able to give priority to Peachtree traffic so that the accounting team has better response time with using the application, because right now its very slow to process transactions. A lot of employees stream music so i'm sure its killing a good amount of bandwidth. Basically my goal is to avoid a single point of failure, unless the power goes out in the building.

stored in the AD as in locally (the client) and then knows which servers to connect to? For the client computers, should I set static IP's for them as well and have the DNS entries point to both servers. Or should I let them obtain that (IP and DNS) information from DHCP? I was going to run DHCP from the Netgear UTM25 VPN device. Is it better to run DHCP from the server instead? I'm worried like you had mentioned if the server dies, then we have no IP's. I'm not familiar with Hyper-V and hosting services virtually. I get the concept of running a virtual OS on top of the physical OS. I do that with my Mac at home running XP via VmWare Fusion.

Not really familiar with Hyper-V. Data storage is on a DroboPro device via iSCSI. Its going to be connected to the network switch. It should appear on the servers as a local drive I believe. Since i've never set up AD or DC, i'm not sure if what i'm saying is true or not. Just going by what I read about. If server 2 is a DC and ADDS replicate, how does the client know which server to access if one or the other goes down? Does that information get passed when the client logs into the domain? Information as in which servers are currently available.

Does Standard R2 support failover clustering? If not, what options do I have when running two servers to ensure that if server 1 fails server 2 will be in use. Server 1 will be setup as a primary DNS, primary DC, and AD-DS Master Server 2 will be setup as a secondary DNS, secondary DC, and AD-DS Replicator All user data is stored on a SAN. So basically if either server fails, data will be available so long as SAN is functioning. Now if server 1 fails, server 2 needs to let clients login via Domain and ensure enforcement of user/group policies. How do I set this up?