DCHP question

[leon phelps]

Hello,

If I assign a static IP to a computer on a network, will I be able to see if it is on a network in the router admin page? I can see the other PC's on the network but not the one with the static IP.

I have a DVR system that is working fine on a network, I can see it from the outside through the internet. I have some ports open to use the DVR and thus use a static IP and open the ports in the applications and gaming section of router admin. I would like to know for sure when it goes down what the probable culprit is. If I could tell if it is on the network, it would help with troubleshooting.

Thanks for any replies.

[naira]

We might need more information about this. What IP address have you set statically and what is the IP address of your router? What is the starting IP address for your DHCP. There might be an IP address conflict.

[YeOldeStonecat]

Hello,

If I assign a static IP to a computer on a network, will I be able to see if it is on a network in the router admin page? I can see the other PC's on the network but not the one with the static IP.

It depends on the router, but most of them...no. If the router supports "reservations through DHCP"...yes you would. Some other models, like some 2Wires, will show netbios names that broadcast on the network.

[leon phelps]

Router is set as 192.168.1.1 . The available IP's are 192.168.1.100 to 192.168.1.149 (50 clients). Router model is Linksys WRT54G. I have the factory firware on it(the newest version).

The PC in question has IP set at 192.168.1.110.

Thanks.

[YeOldeStonecat]

If you have version 1 through 4 of the wrt54g...you can run third party firmware which gives additional features, such as increased power, and....static DHCP through reservations. Hyper-wrt is one which supports that, and is quite identicle to stock Linksys firmware in appearance and management.

Else, when manually assigning LAN IPs..you want to keep them outside your normal DHCP handout range (meaning, use .2 - .99 instead of putting them up above 100 where..if you have more than 10 computers on your network..you could end up with a conflict there)

[leon phelps]

I always thought you needed them in the range or the router would not properly switch them.

Thanks for the information.

[YeOldeStonecat]

I always thought you needed them in the range or the router would not properly switch them.

Thanks for the information.

192.168.1.2 to 192.168.1.99 is still in the range. If the 3rd octet were different...like 192.168.3.99...then it would not work.

The logic is..you keep static IPs outside of your DHCP handout range...because, say you make your IP 192.168.1.110...and you have..oh...12 computers on your network. DHCP hands out IP starting at 192.168.1.100 on up...and say the static IP happens to be "off" at the time the 10th machine logs on...DHCP would have handed 192.168.1.110 out to another workstation..and when you power up your manually assigned .110..you now have a conflict.

Better DHCP services have "exclusion" ranges to help guard against this...but not most consumer grade broadband routers.

So if you work with .2 to .99...you'll have no issues.