14 replies
by curlergirl
Could you give us a rundown of what your current DHCP scope looks like and what the scope options are? Also, what are the TCP/IP properties of your server (IP address, subnet mask, gateway and DNS settings)? Knowing these things might help. Also, did you change anything else related to DHCP or the server's IP address when you upgraded?
Sorry - I don't have any answers yet, just questions!
by mike
by mike
by mike
by curlergirl
You can try deactivating the original DHCP scope and creating a new one. AD and SBS have some pretty deep claws into DHCP and DNS, so I'm not sure this will solve your problem. It's worth a try, though. Also, make sure your server's correct IP address is registered in DNS and that the other one (the one you tried to change to) isn't there, or if it is, delete it.
In SBS 2003, there is a special wizard for changing the server IP address. I made the mistake of manually changing a server IP address once on an SBS 2003 server and ended up with a lot of problems. So, maybe what you want to do is to run the Change Server IP address wizard to change your server IP address again, within the same subnet, and see if that fixes things.
In the end, you may have to do some things manually (like set up your Internet connection) rather than using the wizards if the wizards won't respond correctly.
Hope this helps!
by sgt_shultz
do you have a 'configure your server' option in your sbs console? (Start menu) if so, just uncheck dhcp server to 'start over'
but if you want to t-shoot this, check out this article from the microsoft knowledgebase (it was the first link hit googling 'the wizard cannot set the dhcp'
"The wizard cannot set the DHCP scope options" error message when you run the Configure E-mail and Internet Connection Wizard in Windows Small Business Server 2003
http://support.microsoft.com/kb/875422/en-us
by cg it
Curlergirl has the appropriate suggestion. Use the wizard. SBS is not the same as a standard Windows O/S. There are a lot of wizards that do the actual configuration of it and unless you really really know DNS, DHCP and AD, trying to configure it will just cause more problems than you already have.
I can say this, on the SBS box you can disable DHCP as a service and run a completely static LAN network provided that you run the Connect to the Internet Wizard on the SBS box. If you try to muck with it within DHCP you'll end up with DHCP not starting or responding.
With only 5 computers, why have DHCP in the first place? DHCP is so with a LOT of clients, the chore of tracking addresses doesn't become its own kingdom.
by cg it
by cg it
well I'm not going to say that you probably shouldn't be messing around with the SBS server if you know so little about it but.......if DHCP is disabled, you've got 90% of the battle on the problem won. Now all you have to do is set static addressing for everything.
instead of automatic detection, you have to assign the server and every computer an address. In SBS 2003 when you run the wizard the LAN default addressing is the 192.168.16.2 address for the server. subnet mask 255.255.255.0. DNS is itself. So you have to fill in the blanks [I'm assuming that your running the SBS box with a WAN interface and a LAN interface. All clients would then be on that subnet. with 5 the addressing could be 192.168.16.3 and so on. Subnet mask 255.255.255.0 and DNS is 192.168.16.2 [the SBS box]. you also have to set the default gatway which is the router's address so whatever address the router is, that's the default gateway. DHCP usually does this with options [the wizard does all the configuration for you] but you have to do it.
by cg it
by mike
So I tried to run the wizard for connect to the internet from the to do list, and all I get is a message saying "the wizard can no set the DHCP scope options....
Also, I don't know how to configure client computer IP adresses properties. All of the computers connect to the server via one firewall. thanks again for help
by mike
by curlergirl
I think at this point I'd have to agree with others that leaving DHCP turned off would be easiest. You will need to set the IP addys on your server and workstations and router manually. You can ignore the wizards for now, as they probably won't work properly anyway. If you know how to set IPs manually, what you need to do is set all of the LAN IP addresses (server, workstation and router LAN) to the same private subnet, using the router LAN IP as the default gateway and the server's IP as the DNS server for everything.
Question - do you really have the workstations going *through* the router to the server, or are they all connected to the same hub or switch on the back of the router? Just because they are all connected to the router doesn't mean that the workstations are going through the router to get to the server. They may be going through the hub/switch, but unless they are on different subnets, they are not going *through* the router.
Mike, since you seem to be pretty new at this, I think you may need more help than is reasonable via newsgroup posts. I'd be glad to go into the details with you if you want to email me directly. Basically, I will need to know your exact setup - firewall/router model, current settings on the firewall, current IP settings on the server, current IP settings on the workstations, how physically the server and workstations are connected to each other and to the Internet; i.e., using the switch/hub on the router, or a different switch/hub, and/or using a DSL or cable modem, etc.
Hope this helps!
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending