Windows Server 2008 Configuration
in [Windows Servers]
|
From: PorBar on 13 May 2010 06:24 On May 12, 6:39 pm, Leythos <spam999f...(a)rrohio.com> wrote: > In article <80b49491-44e5-4aad-bd37-e82602216175 > @e1g2000yqe.googlegroups.com>, compsos...(a)gmail.com says... > > > > > > > On May 12, 4:33 pm, "Danny Sanders" <dsand...(a)NOSPAMbrakesplus.com> > > wrote: > > > Use Windows for DHCP and DNS. > > > > hth > > > DDS > > > > "PorBar" <compsos...(a)gmail.com> wrote in message > > > >news:c583023f-c48e-4aeb-8b02-2c3d037fa1c3(a)h9g2000yqm.googlegroups.com.... > > > > > We are setting up a network that currently uses WindowsNT Server (yes, > > > > you read that correctly). We are going to use Windows 2008 R2 > > > > Standard. This network only has 6 clients. Should we use the router as > > > > the DHCP server or should we use the Server for both DNS and DHCP? > > > > > The clients are XP Pro and WIndows7 > > > > > Thanks > > > I thought if the Server is a Domain Controller with Active Directory & > > DNS, it is best to use the router for DHCP? > > NEVER, the DHCP, if properly configured on the server, will provide data > that your router won't provide to the workstations. > > Since you're doing a domain, it's not too late to consider SBS 2008 > instead of Server 2008 standard. > > -- > You can't trust your best friends, your five senses, only the little > voice inside you that most civilians don't even hear -- Listen to that. > Trust yourself. > spam999f...(a)rrohio.com (remove 999 for proper email address) The Server has already been purchased with 2008 Server. I was thinking if the Server went down, they could still use the Internet if the router was handling DHCP. Their primary business requires the Internet more than any files on the Server.
From: Leythos on 13 May 2010 06:43 In article <c3635d04-505b-4869-bd6e-4e5566acd354 @k2g2000yqe.googlegroups.com>, compsosinc(a)gmail.com says... > > On May 12, 6:39 pm, Leythos <spam999f...(a)rrohio.com> wrote: > > In article <80b49491-44e5-4aad-bd37-e82602216175 > > @e1g2000yqe.googlegroups.com>, compsos...(a)gmail.com says... > > > > > > > > > > > > > On May 12, 4:33 pm, "Danny Sanders" <dsand...(a)NOSPAMbrakesplus.com> > > > wrote: > > > > Use Windows for DHCP and DNS. > > > > > > hth > > > > DDS > > > > > > "PorBar" <compsos...(a)gmail.com> wrote in message > > > > > >news:c583023f-c48e-4aeb-8b02-2c3d037fa1c3(a)h9g2000yqm.googlegroups.com... > > > > > > > We are setting up a network that currently uses WindowsNT Server (yes, > > > > > you read that correctly). We are going to use Windows 2008 R2 > > > > > Standard. This network only has 6 clients. Should we use the router as > > > > > the DHCP server or should we use the Server for both DNS and DHCP? > > > > > > > The clients are XP Pro and WIndows7 > > > > > > > Thanks > > > > > I thought if the Server is a Domain Controller with Active Directory & > > > DNS, it is best to use the router for DHCP? > > > > NEVER, the DHCP, if properly configured on the server, will provide data > > that your router won't provide to the workstations. > > > > Since you're doing a domain, it's not too late to consider SBS 2008 > > instead of Server 2008 standard. > > > > The Server has already been purchased with 2008 Server. I was thinking > if the Server went down, they could still use the Internet if the > router was handling DHCP. Their primary business requires the Internet > more than any files on the Server. If you put the router first or even second, or at all, you will have problems with authentication at some point, it always happens. If the server is not reliable then consider a different server - I have servers that have more than 1 full year of up-time on them. -- You can't trust your best friends, your five senses, only the little voice inside you that most civilians don't even hear -- Listen to that. Trust yourself. spam999free(a)rrohio.com (remove 999 for proper email address)
From: PorBar on 13 May 2010 08:05 On May 13, 6:43 am, Leythos <spam999f...(a)rrohio.com> wrote: > In article <c3635d04-505b-4869-bd6e-4e5566acd354 > @k2g2000yqe.googlegroups.com>, compsos...(a)gmail.com says... > > > > > > > On May 12, 6:39 pm, Leythos <spam999f...(a)rrohio.com> wrote: > > > In article <80b49491-44e5-4aad-bd37-e82602216175 > > > @e1g2000yqe.googlegroups.com>, compsos...(a)gmail.com says... > > > > > On May 12, 4:33 pm, "Danny Sanders" <dsand...(a)NOSPAMbrakesplus.com> > > > > wrote: > > > > > Use Windows for DHCP and DNS. > > > > > > hth > > > > > DDS > > > > > > "PorBar" <compsos...(a)gmail.com> wrote in message > > > > > >news:c583023f-c48e-4aeb-8b02-2c3d037fa1c3(a)h9g2000yqm.googlegroups.com... > > > > > > > We are setting up a network that currently uses WindowsNT Server (yes, > > > > > > you read that correctly). We are going to use Windows 2008 R2 > > > > > > Standard. This network only has 6 clients. Should we use the router as > > > > > > the DHCP server or should we use the Server for both DNS and DHCP? > > > > > > > The clients are XP Pro and WIndows7 > > > > > > > Thanks > > > > > I thought if the Server is a Domain Controller with Active Directory & > > > > DNS, it is best to use the router for DHCP? > > > > NEVER, the DHCP, if properly configured on the server, will provide data > > > that your router won't provide to the workstations. > > > > Since you're doing a domain, it's not too late to consider SBS 2008 > > > instead of Server 2008 standard. > > > The Server has already been purchased with 2008 Server. I was thinking > > if the Server went down, they could still use the Internet if the > > router was handling DHCP. Their primary business requires the Internet > > more than any files on the Server. > > If you put the router first or even second, or at all, you will have > problems with authentication at some point, it always happens. If the > server is not reliable then consider a different server - I have servers > that have more than 1 full year of up-time on them. > > -- > You can't trust your best friends, your five senses, only the little > voice inside you that most civilians don't even hear -- Listen to that. > Trust yourself. > spam999f...(a)rrohio.com (remove 999 for proper email address) The Server is brand new (still in the box) so I guess it is as reliable as most at this point. So what is the best way to configure the network IPs, etc? I will give the Server a static IP, eg. (10.10.10.160) and the router (10.10.10.170). It would look like this: On the Server: IP: 10.10.10.160 Sub: 255.255.255.0 Gateway: 10.10.10.170 (Router) Primary DNS: 10.10.10.160 (I have also seen people use 127.0.0.1) On the Clients: IP: Obtain automatically DNS: 10.10.10.160 (I have seen it manually added like this, but I thought the Server should handle it?) Do these settings look correct to you for a Server providing both DNS & DHCP?
From: Danny Sanders on 13 May 2010 10:43 >On the Server: >IP: 10.10.10.160 Sub: 255.255.255.0 >Gateway: 10.10.10.170 (Router) >Primary DNS: 10.10.10.160 (I have also seen people use 127.0.0.1) Do not use 127.0.0.1 that leads to a whole other set of problems. >On the Clients: >IP: Obtain automatically >DNS: 10.10.10.160 (I have seen it manually added like this, but I >thought the Server should handle it?) >Do these settings look correct to you for a Server providing both DNS >& DHCP? I would have the DHCP server hand out the DNS info. makes it easier if you ever have to change your DNS server. hth DDS "PorBar" <compsosinc(a)gmail.com> wrote in message news:96eece58-2c57-4343-9a16-c27f18007439(a)o14g2000yqb.googlegroups.com... On May 13, 6:43 am, Leythos <spam999f...(a)rrohio.com> wrote: > In article <c3635d04-505b-4869-bd6e-4e5566acd354 > @k2g2000yqe.googlegroups.com>, compsos...(a)gmail.com says... > > > > > > > On May 12, 6:39 pm, Leythos <spam999f...(a)rrohio.com> wrote: > > > In article <80b49491-44e5-4aad-bd37-e82602216175 > > > @e1g2000yqe.googlegroups.com>, compsos...(a)gmail.com says... > > > > > On May 12, 4:33 pm, "Danny Sanders" <dsand...(a)NOSPAMbrakesplus.com> > > > > wrote: > > > > > Use Windows for DHCP and DNS. > > > > > > hth > > > > > DDS > > > > > > "PorBar" <compsos...(a)gmail.com> wrote in message > > > > > >news:c583023f-c48e-4aeb-8b02-2c3d037fa1c3(a)h9g2000yqm.googlegroups.com... > > > > > > > We are setting up a network that currently uses WindowsNT Server > > > > > > (yes, > > > > > > you read that correctly). We are going to use Windows 2008 R2 > > > > > > Standard. This network only has 6 clients. Should we use the > > > > > > router as > > > > > > the DHCP server or should we use the Server for both DNS and > > > > > > DHCP? > > > > > > > The clients are XP Pro and WIndows7 > > > > > > > Thanks > > > > > I thought if the Server is a Domain Controller with Active Directory > > > > & > > > > DNS, it is best to use the router for DHCP? > > > > NEVER, the DHCP, if properly configured on the server, will provide > > > data > > > that your router won't provide to the workstations. > > > > Since you're doing a domain, it's not too late to consider SBS 2008 > > > instead of Server 2008 standard. > > > The Server has already been purchased with 2008 Server. I was thinking > > if the Server went down, they could still use the Internet if the > > router was handling DHCP. Their primary business requires the Internet > > more than any files on the Server. > > If you put the router first or even second, or at all, you will have > problems with authentication at some point, it always happens. If the > server is not reliable then consider a different server - I have servers > that have more than 1 full year of up-time on them. > > -- > You can't trust your best friends, your five senses, only the little > voice inside you that most civilians don't even hear -- Listen to that. > Trust yourself. > spam999f...(a)rrohio.com (remove 999 for proper email address) The Server is brand new (still in the box) so I guess it is as reliable as most at this point. So what is the best way to configure the network IPs, etc? I will give the Server a static IP, eg. (10.10.10.160) and the router (10.10.10.170). It would look like this: On the Server: IP: 10.10.10.160 Sub: 255.255.255.0 Gateway: 10.10.10.170 (Router) Primary DNS: 10.10.10.160 (I have also seen people use 127.0.0.1) On the Clients: IP: Obtain automatically DNS: 10.10.10.160 (I have seen it manually added like this, but I thought the Server should handle it?) Do these settings look correct to you for a Server providing both DNS & DHCP?
From: Leythos on 13 May 2010 15:54 In article <96eece58-2c57-4343-9a16-c27f18007439 @o14g2000yqb.googlegroups.com>, compsosinc(a)gmail.com says... > > On May 13, 6:43 am, Leythos <spam999f...(a)rrohio.com> wrote: > > In article <c3635d04-505b-4869-bd6e-4e5566acd354 > > @k2g2000yqe.googlegroups.com>, compsos...(a)gmail.com says... > > > > > > > > > > > > > On May 12, 6:39 pm, Leythos <spam999f...(a)rrohio.com> wrote: > > > > In article <80b49491-44e5-4aad-bd37-e82602216175 > > > > @e1g2000yqe.googlegroups.com>, compsos...(a)gmail.com says... > > > > > > > On May 12, 4:33 pm, "Danny Sanders" <dsand...(a)NOSPAMbrakesplus.com> > > > > > wrote: > > > > > > Use Windows for DHCP and DNS. > > > > > > > > hth > > > > > > DDS > > > > > > > > "PorBar" <compsos...(a)gmail.com> wrote in message > > > > > > > >news:c583023f-c48e-4aeb-8b02-2c3d037fa1c3(a)h9g2000yqm.googlegroups.com... > > > > > > > > > We are setting up a network that currently uses WindowsNT Server (yes, > > > > > > > you read that correctly). We are going to use Windows 2008 R2 > > > > > > > Standard. This network only has 6 clients. Should we use the router as > > > > > > > the DHCP server or should we use the Server for both DNS and DHCP? > > > > > > > > > The clients are XP Pro and WIndows7 > > > > > > > > > Thanks > > > > > > > I thought if the Server is a Domain Controller with Active Directory & > > > > > DNS, it is best to use the router for DHCP? > > > > > > NEVER, the DHCP, if properly configured on the server, will provide data > > > > that your router won't provide to the workstations. > > > > > > Since you're doing a domain, it's not too late to consider SBS 2008 > > > > instead of Server 2008 standard. > > > > > The Server has already been purchased with 2008 Server. I was thinking > > > if the Server went down, they could still use the Internet if the > > > router was handling DHCP. Their primary business requires the Internet > > > more than any files on the Server. > > > > If you put the router first or even second, or at all, you will have > > problems with authentication at some point, it always happens. If the > > server is not reliable then consider a different server - I have servers > > that have more than 1 full year of up-time on them. > > > > -- > > You can't trust your best friends, your five senses, only the little > > voice inside you that most civilians don't even hear -- Listen to that. > > Trust yourself. > > spam999f...(a)rrohio.com (remove 999 for proper email address) > > The Server is brand new (still in the box) so I guess it is as > reliable as most at this point. So what is the best way to configure > the network IPs, etc? I will give the Server a static IP, eg. > (10.10.10.160) and the router (10.10.10.170). It would look like this: > > On the Server: > > IP: 10.10.10.160 > Sub: 255.255.255.0 > Gateway: 10.10.10.170 (Router) > Primary DNS: 10.10.10.160 (I have also seen people use 127.0.0.1) > > On the Clients: > > IP: Obtain automatically > DNS: 10.10.10.160 (I have seen it manually added like this, but I > thought the Server should handle it?) > > Do these settings look correct to you for a Server providing both DNS > & DHCP? Why would you use .160? If you have a network of 255.255.255.0 then set your server(s) in .10 through .19, printers in .60-.79, workstation DHCP scope of .100 though ..199, and the router gateway at .1 The server should ping to it's own IP for DNS and the DNS service should be properly configured on the server. -- You can't trust your best friends, your five senses, only the little voice inside you that most civilians don't even hear -- Listen to that. Trust yourself. spam999free(a)rrohio.com (remove 999 for proper email address)
First
|
Prev
|
Next
|
Last
Pages: 1 2 3 Prev: permissions on a share Next: windows server 2008 wbadmin not remove old backup |