Is there a "norm" when assigning fixed IP addresses

  • Thread starter Thread starter Page
  • Start date Start date
P

Page

By which I mean it is a sort of standard practise to assign fixed IP in certain bands - say for printers

Or do I just go up from 1.1
 
It all depends on your network?

I assume you are talking about an internal network?]

Typically for a small internal lan, it is best to use static addresses and keep a note on a spreadsheet.

For a small lan, It may be best to assign the first 50 to servers, printers etc..
Ie:
10.0.0.0 through to 10.0.0.50 use for servers, printers, switch management adrresses etc.
then use 10.0.0.51 to 10.0.0.255 for clients / laptops etc.

If you are using DHCP to assign addresses to computers. just exclude the first 50 from the address pool.
 
Upvote 0
It is all down to personal preference. I tend to put the router (a.k.a default gateway) on .254 (i.e. 192.168.10.254); servers from .253 and below; then I leave a bit of a gap for future expansion. I tend to start printers around .240; after which, I usually create a DHCP pool from .1 to .200 -ish.

I assign printers with fixed addresses (reserved from the DHCP pool) so that any changes to DNS/WINS/etc are easy to push-out from one location (i.e., after a server swap/addition). If it's a small organisation, I may also assign fixed addresses (from the DHCP pool) to PCs and some laptops to make remote control a bit easier.

That is assuming you are using class-C addresses in the 192.168 pool and you only need 254 addresses...
 
Last edited by a moderator:
Upvote 0
It's easier for long term maintenance and trouble shooting if it is organised. There is no standard, but we usually do something like:

.1 gateway
.2 -10 servers
.11-20 printers and print servers
.50-100 DHCP pool
.200-220 IP telephones

But you are free to invent your own!
 
Upvote 0
What the previous posters have failed to mention is that there are only certain address spaces that are allowed to be used for internal networks. Every computer connected to the internet must have a unique IP address, and there are only so many addresses available.

To prevent clashes, public IP addresses for use on the internet cannot just be picked randomly, and must be assigned, normally from your ISP or some other authority.

However, certain IP address ranges are reserved for use on internal networks, these can be used by anyone without registering them, provided the machine is not directly connected to the internet (i.e it is behind a router).

Those address spaces are:
10.0.0.0 - 10.255.255.255
172.16.0.0 - 172.31.255.255
192.168.0.0 - 192.168.255.255

Within these blocks of addresses, you may allocate devices as you wish.

Every corporation will have their own numbering conventions. Where I work we use:
10.0.0.1-10.0.0.20 for routers and printers,
10.0.0.21-10.0.0.99 for computers (Dynamically assigned)
10.0.0.100-10.0.0.110 for servers.
 
Last edited:
Upvote 0
I want to set up fixed IP addresses for the laptops

Do I have to do this for each connection type - wired and wireless - or if I set it for one is it then set for both ?

(Windows 7 if it makes any difference)
 
Upvote 0
I want to set up fixed IP addresses for the laptops

Do I have to do this for each connection type - wired and wireless - or if I set it for one is it then set for both ?

(Windows 7 if it makes any difference)

You will need to record the Media Access Control (MAC) details for each adapter - and there will be two for a laptop as the wired and wireless adapters will have their own [MAC addresses]. You can then assign fixed-addresses against those MAC addresses such that a laptop always receives the same address(es).

Windows tends to go a little bonkers if you assign the same IP address to both the wired and wireless adapter, so it is best to list each adapter (for the laptop) and assign a separate address. That way, if a user plugs in, and the Wi-Fi is still connected, the laptop should continue to work without throwing weird errors. Linux systems running NetworkManager are able to cope with the same IP address for both adapters, as it switches to the faster connection and ignores the other.

To find the adapter's MAC, open a command prompt and issue the command "ipconfig /all". There will be a tonne of stuff scrolling up the command window. Look for the MAC strings for the wires and wireless adapters.

Microsoft likes to ignore common-protocol, so they list their MAC details with hypens in between the hexadecimal numbers, whereas proper systems use the colon (and upper-case). So a MAC address of 1C:6F:65:AD:98:5D will appear as 1C-6F-65-AD-98-5D under Windows; and if you are using the DHCP server under Windows Server, it takes the MAC address as a continuous string with no separators, e.g. 1C6F65AD985D

Once you have assigned the fixed address, you can test your DHCP config is working by opening and command prompt (as Admin) and issuing the following commands:

ipconfig /release
ipconfig /renew

After that, "ipconfig /all" will list the IP addresses of the adapters and you should be able to see if your config is working.
 
  • Like
Reactions: Page
Upvote 0

Latest Articles