Welcome to Omgili,
Omgili ( Oh My God I Love It ;) is a search engine for discussions. With Omgili you can find answers and solutions, debates, discussions, personal experiences, opinions and more... To learn more about Omgili click here.
This is a complete preview of the discussion as it was indexed by Omgili crawlers. Use this preview if the original discussion is unavailable.
Click here to view the original discussion.
 |
|
 |
|
Fixed IP addresses - Tiscali Forums
One small benefit that came out of my Uncooperative router thread was to realise that using a fixed IP address rather than automatic has noticeably reduced boot up times.
Try it
|
|
 |
|
 |
|
|
|
|
Out of curiosity, by how much ?
|
|
|
|
|
|
|
|
|
Quote: : Out of curiosity, by how much ?
That's a good one But you know what it's like with computers - any delay, even a few seconds, and you're cursing it.
I noticed it most on my wireless laptop, where I would say it's probably knocked over ten seconds off.
|
|
|
|
|
|
|
|
|
Cheers. I might try it on my PC then which also connects via WiFi.
10secs or more would be a useful saving.
Now to workout how to do it
|
|
|
|
|
|
|
|
|
Just a tip. When allocating a fixed IP address, make it a high one, such as 192.168.1.100.
If you subsequently connect something else which asks the router for an address, the router will allocate the first free address, such as 192.168.1.2.
Using high fixed addresses eliminates any risk of conflict.
I'm sure you'll sort the how, but ask if necessary
|
|
|
|
|
|
|
|
|
The proper way to do this is to set the DHCP server to use a sub-set of the available subnet.
Practically, your method may work, Bernard, but you're assuming the DHCP server will work systematically up the range and not pick at random.
By and large, this assumption does work.
The easy way (IMHO) is to use the router's ability to associate an IP address with a MAC address, so it's all handled at the router and you don't need to fiddle about on each connected device.
Unless it's a Linksys which either won't have this feature or won't do it properly.
|
|
|
|
|
|
|
|
|
Quote: : ....The easy way (IMHO) is to use the router's ability to associate an IP address with a MAC address, so it's all handled at the router and you don't need to fiddle about on each connected device this is the way i do it
|
|
|
|
|
|
|
|
|
You can do it however it grabs you.
I'm just saying it reduces boot time.
|
|
|
|
|
|
|
|
|
Quote: : The easy way (IMHO) is to use the router's ability to associate an IP address with a MAC address, so it's all handled at the router and you don't need to fiddle about on each connected device.
Unless it's a Linksys which either won't have this feature or won't do it properly.
That's the easy way for those familiar with their router Chris, but on a forum like this, where ppl are using every flavour of router, the only practical advice you can give is to do it via Windows TCP/IP.
I can't test whether your method improves boot times because, as you correctly surmise, my Linksys router doesn't have that facility, but there has been a substantial improvement of boot times on my network doing it via TCP/IP, particularly after hibernation.
|
|
|
|
|
|
|
|
|
But it's simply not practical so set up fixed IP addresses in Windows on a wireless machine, if you expect to be able to use it away from home.
There's usually a "static DHCP" option, and it usually shows connected clients, with checkboxes etc allowing you to nominate them for static IP addressing.
However, this method is unlikely to deliver your speed improvement, as, in fact, your computer is still entering into negotiation with the DHCP server, and all this achieves is forcing the DHCP server to award the same IP address.
I think you'd have to set it up in TCP/IP on the NIC, as you have done, to see your boot-up speed improvement.
The NIC uses the provided IP address and just gets on with it, rather than faffing about and entering into discussion with the DHCP server.
I have servers and shares and port forwarding, so I need static LAN addresses, but only on fixed, wire-connected machines (and because of the Linksys, this is actually being done currently at the NIC's TCP/IP settings.
With previous Netgear and D-Link routers, I could do this via static DHCP).
My wireless laptops use automatic addressing from the DHCP server and I have to let the DHCP do its own dynamic thing since Linksys haven't implemented static DHCP properly.
|
|
|
|
|
|
|
|
|
Quote: : But it's simply not practical to set up fixed IP addresses in Windows on a wireless machine, if you expect to be able to use it away from home.
Yes, I should certainly have made that clear, though it does only take a mo to switch between auto and fixed
|
|
|
|
|
|
|
|
|
For those of you that every second counts on the web
http://www.ehow.com/how_2283614_make...ox-faster.html
|
|
|
|
|
|
|
|
|
The thread is about faster bootup times, not faster browsing.
|
|
|
|
|
|
|
|