DHCP Issue

[northgoose]

Hello, I have a small network of 5-6 machines, win2003 file server and naked dsl speedstream router. I recently had to change ISP, unfortunately they don't have good technical support. I currently have internet but the clients leases are not being automatically renewed. I am aware that DHCP is down but can't get it working. I can rectify the client ips by rebooting the router every 3 days or so.
My old TCP binding on the server was IP 192.168.2.2
Sub 255.255.255.0
Default Gateway 192.168.2.1
DNS 192.168.2.2
The new ISP has given me these details but I am not sure how to proceed.
Subnet 64.235.209.64/29 I'm really curious about the 29
IPs 64.235.209.65 thru 71
Mask 255.255.255.248

Any help in implementing would be appreciated.
Thanks

[wimiadmin]

Easy stuff first... The /29 is basically saying you have 8 IPs.

The 64.235.209.64 is the gateway/primary IP for the other IPs that are assigned to you. The remaining 7 are assignable to devices.

I'm guessing your router is 192.168.1.1. If I were you, I'd assign a static internal IP of 192.168.1.2 to the Win2k3 server and make it your DHCP server. It will allow you WAY more options in assigning IPs to the client computers.

If this is an option, let me know and I can provide further information for you.

[wimiadmin]

Brian, Thank you for your quick response. Unfortunately when I try to reply to your post I get a message that says I do not have permission to access the page and that may be a problem at this end. I tried to email you but apparently that function is not working.
In any case, yes I can use the Win2k3 server for DHCP. In fact it was set up that way when it was initially installed by the technician with the previous ISP. The settings are still active but there is something I'm missing.
Thanks

[wimiadmin]

I've changed your permissions in the forum so you should be able to reply now....not sure why you couldn't reply....thanks for letting me know, I've got something set incorrectly and need to get that fixed.

As for the dhcp server in 2k3, you'll have to disable dhcp in the router so the network pc's will go to the server to get their IP. It might be best to assign a static IP to one of the workstations with the gateway and the dns as the 2k3 server and make sure you can surf, etc.

[northgoose]

I think DHCP is working on the server as it has a green light. I disabled dhcp on the router but now I am not sure how to assign a static IP to one of the workstations with the gateway and the dns as the 2k3 server etc.
But I do think the network is responding well.
Thanks

[wimiadmin]

Whatever the DHCP Scope is in the 2k3 server, just assign one of the workstations an IP from that scope....as long as that IP is not in use on another machine. Ping it and if you don't get a response, chances are, it's not in use.

To assign a static IP, see our How To Change Your IP Address article and follow the instructions for your OS. In step 9 or 10 depending on your OS, is where you'll plug in the static IP.

The network will probably continue to run with DHCP turned off on the router until it's time for a new lease. When the workstations then try to renew their IP, the router won't respond and they'll drop the IP they have. This is why it would be best to assign a static IP to a workstation that points to the server first to make sure the server is working with DNS, etc. before shutting off the DHCP in the router....unless the other workstations aren't being used...then you're free to do as you please.

[AboveTheLogic]

Originally Posted by wimiadmin

Whatever the DHCP Scope is in the 2k3 server, just assign one of the workstations an IP from that scope....as long as that IP is not in use on another machine. Ping it and if you don't get a response, chances are, it's not in use.

Brian, I disagree with this advice.

If you have your scope set to (for example) 192.168.1.100-192.168.1.150, if you are manually setting an IP on a machine, it SHOULD be something in the 192.168.1.151-192.168.1.254 range... or 192.168.1.3 - 192.168.1.99 (assuming the 2k3 server machine is 192.168.1.2 and the router is 192.168.1.1).

Although the chances are slim that you will have enough PCs to cause an IP conflict if you set a machine static at 192.168.1.139... it is still very possible (especially if you are running RRAS on that server). The chances of a conflict are even greater (almost certain) if you are using 192.168.1.101 as a static IP in this scenario.

The best practice, in my opinion, is to set a DHCP reservation in the DHCP settings on the server (this is what I do). This can be done by MAC address. No configuration on the other machines are necessary, the server will simply just assign the reserved IP every time. And, if DHCP is going to be handled by another device in the future, those machines won't need to be reconfigured to get back online.

If you must set a static IP on the machine that is within the DHCP range, then an exclusion should be made on the server so it does not try to assign that same IP to another host.

[wimiadmin]

Yes....Steve's advice is better.....OUTSIDE the scope. Sorry...brain melt.

I also agree as well with setting a reservation in DHCP...but....we don't know at this point if DHCP is working and able to assign/reserve IPs on the LAN.

Northgoose, can you let us know where you are in the process and if everything is working.

[AboveTheLogic]

Oh yeah, my initial advice assumes that DHCP is working properly

[northgoose]

All my machines are working well. However, although the ip supplied by the isp is 64.235.209.64/29, what is my ip is showing ip of 72.0.210.56 but sometimes revert back to 64.235 etc.
DHCP on the router has been disabled and DHCP on the win 2k3 has a green light and the scope is 192.168.2.1 to 192.168.2.254.
The people at the 3rd party server who host our websites are not happy with this arrangement.
Thank You