Questions on DHCP
-
Does running a DHCP server on the router while connecting to it using a static IP makes the connection any less stable? And is it necessary to disable the DHCP client service in Windows if I'm using a static IP address?
I'm using DMZ to direct all traffic from the modem (it's acting like a router, though) to this computer which require a static IP address. But somehow, after setting up a static IP, if I disable DHCP on the router, the computer can't surf the net despite the router page showing that a internet connection has been established. So I left it enabled on the router instead. Now, when I tried to switch back to the option of obtaining the IP address automatically, it ends up with a "limited or no connectivity" error. Any idea what is actually going on behind all these networking issues?
Modem: Linksys AM300 -
Not that I know of.Originally posted by LatecomerX:Does running a DHCP server on the router while connecting to it using a static IP makes the connection any less stable?
You can leave it on, so if you want to use Dynamic IP addresses, it can automatically detect it.Originally posted by LatecomerX:And is it necessary to disable the DHCP client service in Windows if I'm using a static IP address?
No idea why this is happening. Did you set the DNS servers?Originally posted by LatecomerX:I'm using DMZ to direct all traffic from the modem (it's acting like a router, though) to this computer which require a static IP address. But somehow, after setting up a static IP, if I disable DHCP on the router, the computer can't surf the net despite the router page showing that a internet connection has been established.
This one, haha. Some queer feature of Windows.Originally posted by LatecomerX:So I left it enabled on the router instead. Now, when I tried to switch back to the option of obtaining the IP address automatically, it ends up with a "limited or no connectivity" error. Any idea what is actually going on behind all these networking issues?
Remove all your static IP addresses settings, from Windows as well as the router.
Then set it to automatically obtain IP addresses from the router. -
Thanks for the reply, mayi.
Everything's quite stable now, though I'm still curious over the issues occured during that hours of tweaking.
Currently I have DHCP enabled on the router, so is it possible that it will assign another client the same IP address as mine when it is connecting to a DHCP-enabled computer since mine is not in the DHCP list, resulting in some clashing there? Or will DHCP prevent that?
Will there be issues if I leave both DHCP enabled on the router and the computer while using a static IP address to connect to the router? Wouldn't there be some sort of race condition to assign an IP address to the computer? Or does DHCP prevent this from happening as well?
And yea, I have set the DNS servers correctly then. It's 165.21.83.88 and 165.21.100.88 for SingNet. (I have typed in this so many times during that no-connection period that I can recall this from memory.)
And I have to remove the configuration that I have inputted for a static IP address before selecting the other option eh? ...damn Windows.
-
The solution is to use a static IP outside of the DHCP range. For example, if your DHCP server is configured to issue 192.168.1.100-192.168.1.253, use 192.168.1.99 as your static IP.Originally posted by LatecomerX:Currently I have DHCP enabled on the router, so is it possible that it will assign another client the same IP address as mine when it is connecting to a DHCP-enabled computer since mine is not in the DHCP list, resulting in some clashing there? Or will DHCP prevent that?
Let's say if you have a static IP that's within the DHCP range. If you are already plugged into the network, the DHCP server will not issue your static IP as it already exists on the network. However, say you turn off your PC and another PC joins the network and obtains that IP. Once you rejoin the network with your static IP, there will be an IP address conflict.
However, it's best to avoid this issue completely by using an address outside the DHCP range.
Will there be issues if I leave both DHCP enabled on the router and the computer while using a static IP address to connect to the router? Wouldn't there be some sort of race condition to assign an IP address to the computer? Or does DHCP prevent this from happening as well?
No. If you have a static IP, your laptop will not send a DHCP request. There should be no problem leaving the DHCP server enabled on the router. -
Unlikely, though it has occurred before.Originally posted by LatecomerX:Currently I have DHCP enabled on the router, so is it possible that it will assign another client the same IP address as mine when it is connecting to a DHCP-enabled computer since mine is not in the DHCP list, resulting in some clashing there? Or will DHCP prevent that?
One way I do to avoid this program is to use extreme ends of the IP address range.
Say I set the range from 192.168.1.2 to 192.168.1.100
For static IP addreses, I start from 192.168.1.100 and move backwards.
There shouldn't be issues, although if you want to switch back to DHCP assigned addresses, you need to clear the previous static IP addresses and DNS servers settings, otherwise Windows will just be confused and give you network problems.Originally posted by LatecomerX:Will there be issues if I leave both DHCP enabled on the router and the computer while using a static IP address to connect to the router? Wouldn't there be some sort of race condition to assign an IP address to the computer? Or does DHCP prevent this from happening as well?
How about trying without the DNS servers? It's kind of crazy at times.Originally posted by LatecomerX:And yea, I have set the DNS servers correctly then. It's 165.21.83.88 and 165.21.100.88 for SingNet. (I have typed in this so many times during that no-connection period that I can recall this from memory.)
And I have to remove the configuration that I have inputted for a static IP address before selecting the other option eh? ...damn Windows.
-
One way I do to avoid this program is to use extreme ends of the IP address range.
Say I set the range from 192.168.1.2 to 192.168.1.100
For static IP addreses, I start from 192.168.1.100 and move backwards.
No. This is bad advice. What you are doing is taking the chance that your DHCP server won't issue up to the end of the range. It will probably work for him in this example because it's unlikely he will have 90+ laptops connecting to his router but it's still better to do it properly and use an IP address that OUTSIDE of the DHCP range. Then there's NO chance of conflict.
How about trying without the DNS servers? It's kind of crazy at times.
You MUST have DNS set in your laptop. if you do not, your laptop will not be able to resolve domain names. It's up to you whether you want to enable the DNS relay server in your router. This usually just acts as a DNS proxy for your ISP DNS server (unless you have a really advanced router). Personally, I prefer to manually configure the ISP DNS like he has done.
If you think you have problems with your DNS, try flushing the DNS cache on your laptop.
ipconfig /flushdns -
No. This is bad advice. What you are doing is taking the chance that your DHCP server won't issue up to the end of the range. It will probably work for him in this example because it's unlikely he will have 90+ laptops connecting to his router but it's still better to do it properly and use an IP address that OUTSIDE of the DHCP range. Then there's NO chance of conflict.
Ya, taking chance. No users would have so many PCs anyway.
As for outside DHCP range... not all routers will recognize that... so he may have to take chance. 3Com is one of those. You assign out of it, no network connections. -
Oh... that's very strange.Originally posted by ndmmxiaomayi:Ya, taking chance. No users would have so many PCs anyway.
As for outside DHCP range... not all routers will recognize that... so he may have to take chance. 3Com is one of those. You assign out of it, no network connections.
Perhaps the 3COM only routes the DHCP range? There should be a way to manually add routes then.
In any case, I'm not familiar enough with 3COM products that I can comment on this. However, most routers will route the entire LAN subnet which is usually a /24.
Linksys should support it though. I'm not really familiar with the AM300 though I am familiar with linksys in general.
Well okay then. First try OUTSIDE the DHCP range. If that doesn't work, try the END of the DHCP range.
-
Thanks again, mayi, and Phaze. If you need help in web programming someday, just let me know; I will be glad to provide assistance.
The connection is stable now, and here's the current configuration that I'm using for the modem.
http://dl.latecomerx.com/images/Screenshot_2007-11-07_16-12-45.jpeg
http://dl.latecomerx.com/images/Screenshot_2007-11-07_16-10-45.jpeg -
The static IP address I'm using which is outside the DHCP range works fine. The other method would have worked as well, since there is only an ethernet port and an USB port on the modem, so there is virtually zero chance of an IP address collision even with a /30 subnet.Originally posted by Phaze:Oh... that's very strange.
Perhaps the 3COM only routes the DHCP range? There should be a way to manually add routes then.
In any case, I'm not familiar enough with 3COM products that I can comment on this. However, most routers will route the entire LAN subnet which is usually a /24.
Linksys should support it though. I'm not really familiar with the AM300 though I am familiar with linksys in general.
Well okay then. First try OUTSIDE the DHCP range. If that doesn't work, try the END of the DHCP range.
Edit:
Erm. I forgot about the gateway itself. It should be a /29.
-
Perhaps. 3Com is mainly for enterprise users... so that may be some security feature of it not to route outside of the range set.Originally posted by Phaze:Oh... that's very strange.
Perhaps the 3COM only routes the DHCP range? There should be a way to manually add routes then.
In any case, I'm not familiar enough with 3COM products that I can comment on this. However, most routers will route the entire LAN subnet which is usually a /24.
Linksys should support it though. I'm not really familiar with the AM300 though I am familiar with linksys in general.
Well okay then. First try OUTSIDE the DHCP range. If that doesn't work, try the END of the DHCP range. -
Looks good.Originally posted by LatecomerX:Thanks again, mayi, and Phaze. If you need help in web programming someday, just let me know; I will be glad to provide assistance.
The connection is stable now, and here's the current configuration that I'm using for the modem.
http://dl.latecomerx.com/images/Screenshot_2007-11-07_16-12-45.jpeg
http://dl.latecomerx.com/images/Screenshot_2007-11-07_16-10-45.jpeg
