Logic_Bomb
asked on
Windows SBS 2003 DNS & DHCP
We're running a Windows 2003 SBS hosting DNS, however DHCP is being hosted by our Instigate firewall.
The problem we're having is that unless we hard code a static DNS entry on our workstations, it takes a minute or two for the computers to login to the network. Hard coding DNS on the workstations isn't a problem, however our laptop users are another story. Since the laptops are mobile and connecting to other networks, if we coded the DNS information, the end user would need to remove it when off site. (not a good plan).
From what I've found on the Internet, my problem is with the DHCP server (Instigate firewall) since it's not pushing the DNS server address, and that I need to move the DHCP server to the Windows
2003 SBS, but before I do anything I figured it would be a good idea to ask the pro's.
Thanks for your help!
The problem we're having is that unless we hard code a static DNS entry on our workstations, it takes a minute or two for the computers to login to the network. Hard coding DNS on the workstations isn't a problem, however our laptop users are another story. Since the laptops are mobile and connecting to other networks, if we coded the DNS information, the end user would need to remove it when off site. (not a good plan).
From what I've found on the Internet, my problem is with the DHCP server (Instigate firewall) since it's not pushing the DNS server address, and that I need to move the DHCP server to the Windows
2003 SBS, but before I do anything I figured it would be a good idea to ask the pro's.
Thanks for your help!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
flyjedi
by default sbs2003 sets itself as the default gateway and trys to do all routing for you.
Hi
Maybe is a good ideea to change the lease period on Investigate DHCP to 1 day few days before switching the DCHP servers. And pay attention to all parameters that you use in DHCP (gateway, DNS, WINS).
Also for begining you can raise the Conflict detection to 2 for first week. This will help reducing the IP allocation conflicts in the network.
Good luck
Dan
Maybe is a good ideea to change the lease period on Investigate DHCP to 1 day few days before switching the DCHP servers. And pay attention to all parameters that you use in DHCP (gateway, DNS, WINS).
Also for begining you can raise the Conflict detection to 2 for first week. This will help reducing the IP allocation conflicts in the network.
Good luck
Dan
If you cahnge the name servers on the firewall to primary = ip address of server and secondry = isp primanry dns (just in case).
Then rerun CIEW on the sbs box and ensure that the name servers are set to the primary and secondry of your ISP.
Then you get the DHCP server pointing DNS to the server unless there's a problem in which case it will send it to the ISP.
Hopefully that should work.
NeilParbrook
Then rerun CIEW on the sbs box and ensure that the name servers are set to the primary and secondry of your ISP.
Then you get the DHCP server pointing DNS to the server unless there's a problem in which case it will send it to the ISP.
Hopefully that should work.
NeilParbrook
To be honest you should probally move the DHCP over to the server but the above should work OK.
NeilParbrook
NeilParbrook
Why are you not running DHCP on the SBS? It's the recommended configuration anyhow, and would provide you the correct settings for all workstations. See the bottom half of http://sbsurl.com/dhcp for instructions on how to move it over to your SBS.
Jeff
TechSoEasy
Jeff
TechSoEasy