I agree with the other contributors that this is not to be done lightly, if one wishes to maintain connectivity. And do tell, WHY do you want to do this?!?
That said, please take note that when Will J said: "Many routers reject static IP address, unless told otherwise"
that's absolutely false.
Routers have no knowledge of where a host derives its IP address. If you statically assign an IP that's part of the valid DHCP block for that segment, it will work (assuming, of course, that you retain all other working parameters such as gateway, DNS, etc).
If a router is configured to only allow routing of packets sourced from a certain address block, say the one allocated by the DHCP server, then it will route the packet regardless of how that IP was allocated. It cannot reject the packet because that host configured its IP statically.
A valid risk in such static assignments is that you can cause an IP address conflict if the DHCP server itself tries to lease out that same address. However, a well-behaved DHCP server (or on-segment DHCP relay) will do a gratuitous ARP to check if any host is using that address before it makes its DHCPOFFER and "stand down" (rather than cause an actual problem by adopting a duplicate). It will then log a warning and/or issue an error dialog.
As far as your wireless still working after you change IP, yes it will as long as you're still associated to the same AP. (Wireless is layer 2 whereas IP is layer 3 ... if you don't get the "layer" thing, just ignore this statement.)
Let me know if you want any of the foregoing explained further.
· 1 decade ago