The manufacturer of your computer does not assign IP addresses at all, as the IP address depends on the network to which the computer is attached. A MAC address is assigned to the adapter, but that is for the local physical network (Ethernet or Wifi) and exists purely for layers lower than IP networking.

The ISP assigns an IP address that is (usually) publicly routable and reachable by unsolicited incoming traffic. There are some exceptions- some cell phone networks, for example, assign addresses within the defined “private” ranges (e.g. 10.x.x.x) and use NAT for traffic outbound to the internet.

The address assigned by your router is almost guaranteed to be a private address, most commonly in 192.168.x.x, so that the public address provided by the ISP can be shared among all devices managed by the router, again using NAT (network address translation.)

There could be several reasons why you are unable to get an IP address from your router/DHCP server:

1. Network configuration issue: There could be an issue with the configuration of your network that is preventing your device from obtaining an IP address. This could be a problem with the router, the DHCP server, or the network settings on your device.
2. Hardware issue: There could be a problem with the hardware on your device or the router/DHCP server that is preventing your device from obtaining an IP address. This could be a problem with the network adapter on your device, the router, or the DHCP server.
3. Firmware issue: There could be an issue with the firmware on your router or DHCP server that is preventing your device from obtaining an IP address.
4. Insufficient resources: If there are not enough available IP addresses on the network, your device may not be able to obtain an IP address.

To troubleshoot this issue, you can try restarting your router/DHCP server and your device, and checking the network configuration and settings on both. You can also try checking for any firmware updates and ensuring that there are sufficient resources available on the network. If the issue persists, you may need to seek further assistance from your network administrator or a technical support specialist.

Your manufacturer dose not assign an IP address. Though, there is an IP address that your computer will assume if one is not assigned. This address is called a Zero-Conf IP address and is created by the Network interface card (NIC) driver.

Every NIC has a unique physical address. This address is assigned to the network card by the manufacturer. When the driver can not get an address for the NIC, it will perform an logarithm using the MAC address to create the last two octets and prepend 169.254 as the first two octets. Once the driver has created the address, it will perform an ARP to verify that no one else on the Network is using the same address. If someone else has that address the driver will create another address.

You always have an external IP address. Otherwise you can not communicate with the world. How you get that IP address configured, depends on the technology used. It can be set static, negotiated over DHCP, allocated during setup of PPPoE etc. This is all independent on what you use as “internal addresses”. It’s not mandatory to use DHCP internally, nor is it mandatory to do NAT. It all depends on what the ISP has in store for you.

In mobile networks sometimes your external IP is 10.x.x.x but in reality you only use a private IP inside the mobile operator and you get internet through a big carrier network address translation box at the edge. So the IP is allocated temporarly for your connection there and it can change per tcp session.

Solution for your TP-Link router no internet when connected to the tablet :

You have successfully connected your router, but still, there is no internet. If you are having this issue, then this is the place where you could find the solution to that. Follow the steps below:

1. First of all, check for the connections, if they are made properly.
2. You should visit other websites; the one you are visiting might not be working.
3. Check if other devices are connected properly if it's only your tablet, then it could be the configuration problem.
4. You need to restart your tablet, to clear the temporary glitches and then try to connect again.
5. Now, check that your Wi-Fi connection is turned ON and make sure that airplane mode is disabled.
6. Make sure you are using the correct router name and password. You could also try repositioning your router or device.
7. Now, try deleting the Network from the device entirely. For that click on the network name and then click on “Forget the Network”.
8. Now, find the network again and enter the correct password. This will solve your problem.

I presume that you mean to disable the DHCP-server function that normally provides IP addresses to devices connected to your LAN.

Yes, that is perfectly OK. You will need to apply manual settings to all devices, regardless if they are connected wirelessly or with cable. To be overly specific, you need to provide each unit with:
IP-address (a unique address, ie 192.168.1.x if your router uses 192.168.1.1 for instance)
Net Mask (ie 255.255.255.0)
Default Gateway (This is the IP address of your router, commonly 192.168.1.1 but can vary)
At least one DNS address (Either the gateway address, or any DNS server. I usually use Google’s DNS 8.8.8.8 or 8.8.4.4)
Best practice is to use your gateway/router’s IP as the primary DNS and Google’s DNS as the secondary.

Basically, no one must have a DHCP server, it is just a very easy way to set up a network, with the added benefit: If it is the router that provides the IP addresses, it will also know what unit is what. In that way you can type PRINTERNAME and get connected to the printer without knowing the IP address.

Any TCP/IP interface can potentially acquire an IP address from a DHCP server. The configuration of the interface and the configuration of the network(s) dictate what things are DHCP clients and which are DHCP servers. Perhaps you are referring to the router you buy at your neighborhood electronics and computer store as the interface between your residential ISP and your home network. The router itself has two or more interfaces, and is typically a DHCP client on the Internet-facing interface. It is also normally a DHCP server on the LAN-facing interfaace(s). It has these roles concurrently.

It is sometimes possible to disable the LAN-facing DHCP server, and it may be possible to statically assign an IP that your ISP would provide you with on the Internet facing interface. You could potentially have a completely separate DHCP server for your LAN, even to the point that the LAN facing interfaces on your router are DHCP clients. This would be a fairly unusual configuration, but some of us have different ideas about what functions a router and DHCP server should support.

Some ISPs provide a box which has the role of cable modem and router and wireless access point all rolled into one box. These have an Internet facing interface to which an IP address is assigned by the ISP, but that may not necessarily be done using DHCP.

The term ‘DHCP address’ is actually not a meaningful phrase. A DHCP server dispenses IP addresses (and other network configuration data) to DHCP clients. They are just IP addresses.

So you have a network with multiple routers. If only one router is configured to do DHCP than your machines will get an address from that router and that router will have a record of an IP address being assigned to a MAC address. No other router will know about that DHCP assignment. They don’t need to know.

Now, you have more than one router on the physical network configured to offer up DHCP address. Your machine sends out a request for a DHCP address. All routers configured to assign an IP address can respond to the request. They should all be configured to offer from a different range of addresses (or subnet). Your machine will decides which address it wants to accept. It send a response to that effect to the DHCP server offering that address. That address now knows about the assignment. There is also a lease time associate with assignment. Both your machine and the assigning router know how the duration of the address assignment and when it will expire and when your machine has to re-request an IP address and when the router will be able to offer the IP address again. No other router will know about it. They are not involved in the IP address lease and don’t have to know.

There may be other things going on:

1. The DHCP server does not have to be a router. It can be running on another computer with the DHCP server program. In that case no router needs to know about the ip address being assign.
2. A DHCP server can be configured to offer IP addresses based on MAC address, OS type, hardware type, or something else.
3. If two DHCP servers are configured to offer the same address range, it is possible that two different machines will get the same IP address and you will have network related problems on your system. Again this is because one DHCP server does not know what another one is doing. It does not have to know.
4. Each DHCP server keeps track of the ip addresses it leased to others. Not what other DHCP servers are doing.

Where does your IP Address go at night?

Once your IP address is off the clock so to speak, it joins a few others at the local clubhouse where the Council Of Elders (Class A addresses) convene regularly to determine what is in the best interests of the Internet as a whole, and then delegates responsibility down to the lower Class B and Class C addresses in attendance.

These responsibilities can include, but are not limited to, things like who gets to represent larger more powerful entities with fat bandwidth pipes and tons of gigabytes flowing hither and yon, and who gets to represent lowly Internet users at home with cable internet or even (shudder) dial-up connectivity.

Or who gets be the new address for a popular set of DNS servers. Or who gets to be the pubic address of the new fancy IP camera they was just released.

Sometimes, a practical joke is played with an address or two and it actually gets set up to go nowhere, leaving the hapless address flapping in the breese, serving no purpose other than to frustrate Internet users that are trying to get somewhere.

The list of jobs is varied and wide, and opportunities abound for the more ambitious addresses trying to move up the ladder.

Unfortunately there is an old sub-caste system in place where addresses of a certain lineage will get the better jobs and others will consistently get the ones of lesser importance. This is why IP addresses from your home cable modem and/or router will often be in the 192.168.*.* range, forever isolated to private networks and unable to directly connect and mingle with the larger Internet community. (No one really recalls what actually happened that caused these addresses to fall out of favor with the elders.)

This sub-caste system also effects some of the higher-level class B and A addresses that may seem rise due to their class, but will also be forever regulated to things like private networking uses, isolated from the larger address community. (I am looking at YOU, 10.*.*.* and 172.16.*.* — 172.31.*.*, keep your filthy bits off my Internet!)

And then, after all the infighting and assignments are completed, the IP addresses go to their designated assignments and get ready for the day's tasks of shuffling your data around, making sure everything gets to where it needs to go.

…most of the time, anyway.

Because you don’t use public IP addresses on your home network.

Your router has two sides to it: the public side connected to the ISP, and the private side connected to your home network. The thing is, YOU are responsible for all the IPs in your home network. Your ISP is only responsible for giving you one public address.

So here’s the secret sauce: your router already has a DHCP IP range built in. All the devices on your private network get an address from it. As those devices go out on the Internet, the router translates the private addresses into the one public address from the ISP. It keeps a table of translations so it doesn’t get the messages mixed up.

I might need a bit more information on the ‘non-standard’ nature of the address you are getting, but if that address happens to be along the lines of ‘169.254.x.x’ then it means your PC has failed to establish a connection to the DHCP server, and has given itself a specially reserved IP address as a fallback. It’s called a ‘Link Local Address’.

Seeing the 169 address is normally an indicator that something fairly fundamental has gone wrong - a faulty cable, a failed DHCP server, etc. I’ve also seen it when the DHCP server ran out of addresses to allocate because the pool was too small.

There are other options - If the address is not 196, but just something unexpected, then there may be another DHCP server on the network segment - and/or you may be on the wrong VLAN.

1. You need a network design
2. The goal of the network design is for security and management
3. Network topology should use subnets for managing like group devices
4. Routers should be used to connect networks and subnets
5. Switches should be used to connect devices on a subnet
6. If you are going to use DHCP, normally there will be only 1 DHCP server per subnet (but there can be multiple for failover and redundancy).
7. If I were building the network, I might start with static addresses with a small set of devices, get the network working correctly, and then introduce a DHCP server. Change one device at a time over from static to DHCP.

If you are not using any modem or router and terminating the Ethernet cable directly in your PC, your ISP is probably a Cable ISP assigning private IP addresses to its customers because of non availability of ample public IP addresses. In this case, it must be converting the source IP address of the outgoing traffic to a Public IP address using NAT (Network Address Translation).

On the other hand, if you are using a modem or a router, it is quite likely that a public IP address is being assigned to that device, which uses a private IP address pool for the computers and devices on the local network.

Say your routers IP address is: 192.168.0.1

You use static IP addressing, set your IP address to one UNUSED on the network (more on that later).

Set the Gateway to: 192.168.0.1

Set DNS server details either as the same as the router (192.168.0.1), or pick a manual DNS server (coudflare for example is 1.1.1.1)

It “should” connect to the internet - however some routers may not register it very quickly allowing internet.

If you select an IP address already assigned to a different MAC address the router will probably NOT allow internet access…… & definitely not if that device is active & registered on the LAN.

But WHY not use DHCP? If it’s your intent NOT to gain internet access there’s little issue, but even if you use manual settings, as soon as your PC connects to the router as a gateway before internet access is granted - the router will make a log of the access…… & usually note that IP address as a manual assignment & lock it off the usable list. There’s no way to use the router as internet source & not register the device on the LAN.

You don’t have to disable the DHCP server. If you don’t disable the second router’s DHCP server, you will have two separate networks in your house. Devices on the first network won’t be able to connect to devices on the second network. I do this in my house. The first network is for my IoT devices. If a hacker takes one over, they won’t be able to connect to my computers and phones, which are on the second network. If you do this, the first 3 digits of the IP address in the second network should not be identical to the first network. Of course, this is obviously not what a repeater does. So the answer is, leave the DHCP server on or turn it off, depending on what you want the second router to do.

Canonically, a modem is a layer 2 device and cannot have an IP address.

For convenience, nowdays people use to call “modem” the device that the ISP installs in their home. More correctly, this is a mixed device (a gateway) that acts both as a modem and a simple router.

In series with this gateway the client usually installs his own wi-fi router (which he designates as such).

Now, is the public IP address assigned to the gateway or the client's router? It depends on setup. In some cases, the ISP uses the gateway like a cable modem and the public IP goes to the client's router (which is the best setup, client-wise). In other cases the ISP insists to keep the public IP on his gateway and the client only gets private IP addreses. This is not good, since the client has no control over the firewall, NAT setup, etc. (usually, you have no access or credentials on the gateway).

.

In many cases you will have a DHCP address assigned by your ISP and another one assigned by your router.

in order to be able to communicate with servers in the Internet, you need a public IP address. This is the address assigned by your ISP. If your network contains a router, then the router is assigned this IP address.

however to have multiple devices on your network, rack device needs a different IP address. So your router assigns each device their own private IP address via DHCP. When your computer starts to communicate with a server on the Internet, it will send packets to your router which will forward the packets using its public IP address using NAT (network address translation).

Note that you could statically assign each of your devices their own IP addresses, but it’s much simpler to let your router do the assignment using DHCP.

In most cases with domestic internet, there will be two DHCP servers involved. If you’re into playing about with how your home network is set up or have other more advanced needs this answer might change, but for the vast majority of home users it’ll look something like:

Your ISP will have their own DHCP server(s). These will give an IP address to your modem or router, and which will appear as your external internet-facing IP address. If you go to a site like https://www.whatismyip.com/ this is the IP address that’ll show up.

For internal private IP addresses, which will often be in the format 192.168.x.x or 10.x.x.x, these will be allocated by a private DHCP server. For the vast majority of home users, this DHCP server will sit on your router, and will give IPs out to devices inside your home that ask for one.

The thing is you will have to manually assign ip addresses in the local range when you try to connect to the outside internet.

It is highly likely that your ISP depends on your router to be its DHCP client, and then it downloads the ips of the DNS (nameservers) into the router for your use. So that (router as DHCP client to the ISP router) should remain enabled.

If you currently have no devices connected, you could just as easily turn the router off. That will prevent it from ‘pinging’ the ISP server periodically, and of course prevent anyone unauthorized from connecting through it. When you power it back on, it will load up an external IP address from the ISP and then wait for internal connections via wireless or LAN connections.

You may disable DHCP on the client side, and just connect with a dedicated local ip address in the range of the client-side network mask, that is quite workable.

You don't need to disable the second or more DHCP server, but the issuing of IP address's from the DHCP server must be unique and setting it up is not that difficult, but it isn't easy either with quite a few potential pitfalls.

You would think that for 2 routers you just set up one DHCP range to 10.0.0.0 - 10.0.0.128 and the second to 10.0.0.129 - 10.0.0.255 (if that's the address range you are using) except the routers themselves need an address so that has to be removed from your DHCP scope and the top and bottom of each IP range are used for other things (network broadcasts etc) so you shouldn't use them either. so now our scope ranges are 10.0.0.2 - 10.0.0.127 and 10.0.0.130 to 10.0.0.254. The gateway for router 1 is the same as for one router but what about the gateway for router 2 that has to be set to router 1 for the router but not the systems connected to the router. What about fixed addresses like printers etc.

If you want the nets to be independent you need the correct subnet masks and so it goes on.

As you can see it is not that difficult but it isn't easy either there are a myriad of rules to follow and ensure that there are no IP clashes and connectivity is correct, it is far easier to switch off the second DHCP server and let one deal with it all.

If you connect a second router to extend the subnet from the primary (ISP connected) router, then you must disable DHCP in the second router if any devices are configured to to get their addresses automatically.

If DHCP is enabled in the second router, when a device asks for the address it should use, both DHCP services will respond. There is no guarantee which DHCP response will be accepted by the device that requested the address. Although the IP address will probably be okay, a home router will normally provide its own address as the gateway address. Any device that uses the addresses provided by the second router will not be able to access the Internet as devices have to use the correct router for packets to be routed to the Internet.

If all computers are using static addresses, then no addresses are assigned by DHCP and the second router’s DHCP service can be left on. It is safer to leave the second router’s DHCP is turned off in case any device connects and asks for an address to be assigned automatically.

Well, that’s a big question because it depends what device you’re using. If you’re talking about on a domain and you have a DHCP server role on a server, then that’s quite a different set up from a home router. Either way. Either the DHCP settings are wrong, haven’t been applied and saved (or scope activated on a DHCP server). Or your end device isn’t looking for DHCP. Or cabling is bad if it’s all wired in a domain environment. Obviously, if other and devices are getting addresses, you can rule quite a few things out that might be wrong with the upstream and start looking at cabling or the end device in question only

DHCP assigns IP addresses automatically (basically plug and play network) versus setting up static IP’s. Go into the network device settings and change from DHCP to Static and you can then assign your devices to whatever IP address you want that is in the range of your network. You then need to go to each device’s network settings and assign a static IP. Doing it manually is a form of security in that you limit the IP’s that can be used on your network. When using the correct subnet mask. Most default router settings are set to DHCP for assigning IP addresses and these are set to a default value of 50 available IP addresses. This is the same area in the network settings,, you can assign DNS as well. Some DNS’s are faster/better then others.