Windows Server 2003 SBE, asking me to disable DHCP server so that it can install its own

[coolred]

I believe the DHCP server it is seeing, is from my linksys router. I am just wondering if I should leave it as it is, or go ahead and install the windows one?

 

[spyordie007]

Typically I would say use Windows for it. It's easier to ensure that clients are registered in DNS properly than with most routers.

-Erik

 

[coolred]

Will it require any setup or work to mantain? IF so I wouldn't mind playing with it later, but for now I just want to make sure my systems work. Specifically that my tivos don't lose thier connection to the net for updates.

 

[spyordie007]

It will require a little work to setup (though not very much). Once it is setup maintenance should be next to nothing.

 

[coolred]

I guess I will give it a try, thanks

 

[Chunkee]

yes, let the SBS box do its thing....if not, make sure the server is within the same subnet as the router and set the IP of the server as excluded on the router. SBS 2003 is a great product. I know a bit about it. Shoot me a pm if you need any other help

JC

 

[TG2]

I would set it up on the SBS box

- make sure that you set the routers IP in the SBS box's DHCP settings as the "gateway"

 

[stash]

It shouldn't require much of anything to setup. SBS does everything for you, including creating the scope, exclusions, options and activating the server in AD.

 

[RebateMonger]

Originally posted by: coolred
I believe the DHCP server it is seeing, is from my linksys router. I am just wondering if I should leave it as it is, or go ahead and install the windows one?

There are many reasons to use SBS's DHCP and no reasons not to. If you don't absolutely know what you are doing, all you will do is create problems by allowing another DHCP server.

 

[Brentx]

I would use SBS's DHCP server also, as many others have said. However, if you still wanted to use your router's DHCP server, you would have to manually add the SBS machines IP to the DNS list in the router's config. This way clientswill be directed to the SBS server for DNS resolution.

 

[RebateMonger]

Originally posted by: Brentx
I would use SBS's DHCP server also, as many others have said. However, if you still wanted to use your router's DHCP server, you would have to manually add the SBS machines IP to the DNS list in the router's config. This way clientswill be directed to the SBS server for DNS resolution.

Well, you always want to use SBS as the ONLY DNS server for your Domain. You set SBS to forward requests for external domain names to your ISP's DNS server for resolution.

 

[spyordie007]

Originally posted by: Brentx
I would use SBS's DHCP server also, as many others have said. However, if you still wanted to use your router's DHCP server... * ...This way clientswill be directed to the SBS server for DNS resolution.

Yes, if you were really set on using DHCP from the router you would just make sure that it was handing out the server's IP as the DNS server.

...you would have to manually add the SBS machines IP to the DNS list in the router's config...

Actually if they are all 2K or XP clients and domain members they are capable of self-registering in DNS even if the router is doing DHCP; the advantage (here) to having a Windows domain member DHCP server is that if the clients cannot register themselves in DNS the DHCP server can.

Well, you always want to use SBS as the ONLY DNS server for your Domain. You set SBS to forward requests for external domain names to your ISP's DNS server for resolution.

In the SBS world this is generally, however not always, true. In larger networks there are a lot of acceptable solutions. The important thing is only that the clients are going to the DNS server(s) where the active directory namespace is housed for internal name resolution.

Erik