Internal ip address will not stick
First of all Id like to thank everyone here for all the help ive recieved lately, thanks! On to my question, I have a linksys WRT54G router with a windows xp machine connected as well as my web server running Ubuntu DD, I have gone into the router and have successfully routed web and ftp traffic to the server, my problem is that the XP workstation is set to DHCP and the server is set to request an internal address of .103, but my router still treats it as its not requesting a static ip. I'll come home after work and every day it will have a new address, any reason why it would not give the server the ip address it asks for? Should every machine in the house be set to request a static ip?
|
Quote:
|
Great ill try it when i get off work! :D
|
Hmm that didnt seem to work, it just ignores that machine when i do that. Heres what i tried
"Starting ip address"= 192.168.1.10 "Linux server static ip"= 192.168.1.103 it didnt even assign it an address. Should i try disabling DHCP? Also i tried setting "Static DNS 1" to 192.168.1.103 after i set the starting up address back to 192.168.1.100 still didnt work |
I suggest you change your DHCP pool to be 192.168.1.10 - 192.168.1.100 on the router. The router shouldn't need to know about the server's IP unless it used in a firewall config somewhere. Then set your server up with a static IP, using whaever config tool you used to set it up with DHCP. You need to ensure that you get the netmask and default gateway correct.
Once you've done this, check that you can ping your default gateway (which should be your router). If this doesn't work, please post: - your router make and model - your distro - the output of the command (run as root) Code:
$ ifconfig eth0 |
Well that worked! I guess changing the dhcp pool and actually pinging the router from the server worked :newbie: Thanks alot!
|
All times are GMT -5. The time now is 07:50 AM. |