How to quickly add multiple ip addresses to windows servers

1. Open “START” Menu.
2. In Windows XP click on “RUN” and type “ncpa.cpl” (this is not case sensitive). If using Windows Vista or 7 after hitting the “START” icon, type “ncpa.cpl” into the search bar above the “START” icon.
3. Find the “Local Area Connection” then “right-click” on it.
4. Click on “Properties”.
5. In Windows XP you will double click on “Internet Protocol (TCP/IP)”. However, with Windows Vista and Windows 7 you will need to double click “Internet Protocol Version 4 (TCP/IPv4)”.

• If there is no static IP, set the static IP, subnet, gateway and DNS information according to what is found from double-clicking the network connection of concern (e.g. “Local Area Connection”), and click on the “Details” button (in Windows XP, the “Details” button is located on the Support tab).

KB ID: DD1990270

DISCLAIMER: Use of this content may void the equipment warranty, please read the disclaimer prior to performing any service of the equipment.

DAKTRONICS DOES NOT PROMISE THAT THE CONTENT PROVIDED HEREIN IS ERROR-FREE OR THAT ANY DEFECTS WILL BE CORRECTED, OR THAT YOUR USE OF THE CONTENT WILL PROVIDE SPECIFIC RESULTS. THE CONTENT IS DELIVERED ON AN “AS-IS” AND “AS-AVAILABLE” BASIS. ALL INFORMATION PROVIDED IN THIS ARTICLE IS SUBJECT TO CHANGE WITHOUT NOTICE. DAKTRONICS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING ANY WARRANTIES OF ACCURACY, NON-INFRINGEMENT, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. DAKTRONICS DISCLAIMS ANY AND ALL LIABILITY FOR THE ACTS, OMISSIONS AND CONDUCT OF YOU OR ANY THIRD PARTIES IN CONNECTION WITH OR RELATED TO YOUR USE OF THE CONTENT. ADJUSTMENT, REPAIR, OR SERVICE OF THE EQUIPMENT BY ANYONE OTHER THAN DAKTRONICS OR ITS AUTHORIZED REPAIR AGENTS MAY VOID THE EQUIPMENT WARRANTY. YOU ASSUME TOTAL RESPONSIBILITY FOR YOUR USE OF THE CONTENT AND ANY LINKED CONTENT. YOUR SOLE REMEDY AGAINST DAKTRONICS FOR DISSATISFACTION WITH THE CONTENT IS TO STOP USING THE CONTENT. THIS LIMITATION OF RELIEF IS A PART OF THE BARGAIN BETWEEN THE PARTIES.

The above disclaimer applies to any property damage, equipment failure, liability, infringement, or personal injury claim arising out of or in any way related to your use or application of the content, whether such claim is for breach of contract, tort, negligence or any other cause of action.

Sign Up to Receive Emails

Always be the first to know about new trends, products and services in the digital display industry. Sign up to keep in touch and start receiving relevant emails and newsletters from Daktronics.

Window Server 2012 DHCP server is currently configured as:

• Subnet: 10.0. x.x (e.g. 10.0.0.0/16)
• Dynamic IP Range: 10.0.0. 12 – 10.0.0. 120

This is done to limit dynamically assigned addresses to a small range on the subnet (and not overlap into other ranges).

I would like to add another address range to pool of available ranges that DHCP can pull from on our 10.0.x.x subnet:

DHCP Address Pool

• 10.0.0. 12 – 10.0.0. 200
• 10.0.27. 12 – 10.0.27. 150

Of course you can’t do that because:

Of course it doesn’t conflict; it’s just being stubbon.

I want the DHCP server to offer addresses from a pool of two ranges on the 10.0.x.x subnet:

DHCP Address Pool

• 10.0.0.x
• 10.0.27.x

How do i do that?

Workaround

i suppose i could do it with exclusions:

• Range: 10.0.0.0 – 10.0.255.255
• Exclude: 10.0.0.0 – 10.0.0.11
• Exclude: 10.0.0.151 – 10.0.0.255
• Exclude: 10.0.1.0 – 10.0.26.255
• Exclude: 10.0.27.0 – 10.0.27.11
• Exclude: 10.0.27.151 – 10.0.26.255
• Exclude: 10.0.28.0 – 10.0.255.255

But that idea is so dumb that I won’t even bring it up.

Bonus Reading

• How to add extra range of IP in DHCP of Windows Server 2008 R2(archive)
• Adding another IP Range to DHCP(archive)
• KB255999 – Increasing the number of IP addresses on a subnet in DHCP Server

How does DHCP work?

Dynamic host configuration protocol can be used to automatically configure network devices with information they need:

• Network subnet mask (e.g. 255.255.0.0)
• DNS server (e.g. 10.0.42.7, 10.0.13.29)
• Domain name (e.g. stackoverexchange.com)
• Default gateway (e.g. 10.0.241.1)

In addition to being able to configure host options, it can automatically give clients an IP address. The DHCP server is given a block of IP addresses it can assign to clients, e.g.:

• 10.0.0.12 – 10.0.0.100
• 10.0.0.200 – 10.0.0.245
• 10.0.3.100 – 10.0.3.200

And when a client shows up needed an IP address, it looks in it’s available pool of addresses, picks one, and gives it to the machine:

• 10.0.0.12 – Unassigned
• 10.0.0.13 – Unassigned
• 10.0.0.14 – Unassigned
• .
• 10.0.0.98 – Unassigned
• 10.0.0.99 – Unassigned
• 10.0.0.100 – Unassigned
• 10.0.0.200 – Unassigned
• 10.0.0.201 – Unassigned
• 10.0.0.202 – Unassigned
• .
• 10.0.0.243 – Unassigned
• 10.0.0.244 – Unassigned
• 10.0.0.245 – Unassigned
• 10.0.3.100 – Unassigned
• 10.0.3.101 – Assigned to de-ad-be-ef-ba-ad (IANBOYD)
• 10.0.3.102 – Unassigned
• .
• 10.0.3.198 – Unassigned
• 10.0.3.199 – Unassigned
• 10.0.3.200 – Unassigned

I want to add more ranges of IPs to the available pool of IPs to be assigned.

Other DHCP servers do it

Of course other DHCP servers can do this:

But i already know how to do it in other DHCP servers. I’m asking how to do it in the DHCP server that ships with Windows Server 2012.

If Windows Server 2012 DHCP server cannot do it: it’s ok to say it:

It cannot be done; Windows Server 2012 does not support this feature that other DHCP servers support.

But i’m hoping it does support it. DHCP has been around a long time; and Microsoft has had a long time to get it right.

Yesterday, I showed you how to block IP addresses in Windows Firewall using PowerShell. This comes in handy when blocking IP addresses that are brute-force attacking your servers. In this short post I’ll show you how to bulk add IP addresses in Windows Firewall, list an IP address and how to remove all IP addresses from Windows Defender Firewall with Advanced Security.

For this post, I assume to have the same firewall data available as in my previous post Block brute force attacks on SQL Server, block IP addresses in Windows Firewall using PowerShell. Read that article first if you’re unsure. Let’s assume you have not yet created your firewall rule “IP Block SQL Server”, but you have your unique_ips.txt input file ready.

The cmdlets I’ll be using are:

Add IP addresses to Windows Firewall in bulk

The Set-NetFirewallRule and New-NetFirewallAddressFilter cmdlets both accept an array as an input for the RemoteAddress attribute. And that’s great, because now you can add a lot of IP’s in bulk to your firewall:

Add one (1) IP address in Windows Firewall

Here is how you can add one (1) IP address to your firewall. This involves having to add that one IP address to an array of currently blocked IP’s.

Look up an IP address

Looking up an IP address in your firewall -using PowerShell- is quite easy:

You may even use an array of IP addresses to look up:

List active firewall rules

Use the following to neatly display active firewall rules. Adjust to your needs.

Remove an IP address from your blocklist

Sometimes, or perhaps even often, you need to remove an IP address from your brute-force block list. Removing an IP address from your firewall involves the same steps as adding one; you must manipulate the array of currently blocked IP’s. And except of adding one, you remove one and putt the array back.

Remove firewall rule completely

If you need to remove the firewall rule completely, use Remove-NetfirewallRule :

Or use Disable-NetFirewallRule -DisplayName “IP Block SQL Server” to disable this rule.

Many new Windows sys admins are not sure about – how to add additional IP address to a Windows 2003 (2000) server. It is easy to add an IP address. J ust follow the instruction mentioned below.

=> Click on Start button

=> Open Cotnrol Panel

=> Open Network connections

=> Select Local Area Connection (for first Ethernet card)

=> Right Click and select Properties

=> Select Internet Protocol (TCP/IP)

=> Now click on Properties button

=> Click on Advanced tab

=> Now you need to add in an IP address section Enter IP details such as IP address, Subnetmask etc

=> Save the changes and go back to Windows server desktop

How do I verifty that new settings are working?

Open command prompt > Click on Start button

=> Type cmd and press enter

Related posts:

1. How to Windows 2003 Server start or stop services
2. How do I upgrade Windows 2000 or 2003 server nework card port speed?
3. How to find and change Nintendo Wii DNS server IP address
4. Flash Windows Vista / XP DNS Cache With ipconfig Command
5. Change the welcome banner For Windows FTP server

Author: admin

I like chocolate, gadgets, open source software, photography, traveling and all shades of green colors. I love spending time with fun loving friends and family members. This is my own online journal. View all posts by admin

7 thoughts on “Windows 2003 server add additional IP address”

This one makes sence “One’s first step in wisdom is to kuesstion everything – and one’s last is to come to terms with everything.”

DHCP reservation is the creation of a special entry on the DHCP server. Thanks to this, the same IP address from the DHCP scope address pool will be issued for a specific device (MAC address). In this article, we’ll look at how to create and manage reservations on a DHCP server running Windows Server 2019.

If some network devices (printers, scanners, workstations) require a permanent IP address (instead of manually setting a static IP address in the device settings), you can reserve an IP address on a DHCP server. In the DHCP server on Windows Server 2019, you can create a reservation from any leased IP address, or manually create a new entry.

Open the DHCP Management Console (System Manager > Tools > DHCP) or simply run the dhcpmgmt.msc command. Expand your DHCP server, select IPv4, then select the scope where you want to manage reservations.

If the DHCP server client already received a dynamic IP address from your DHCP server, you can reserve this address. Go to the Address Leases section, find the DHCP client you need in the list (the fact that this IP address is dynamic is indicated by the presence of a date in the Lease Expiration field), right-click on it, and select Add to Reservation.

You can also create a DHCP reservation manually. To do this, you need to find out the MAC address of the device. In case you use a Windows device, you can find out the MAC address of your network adapter with the command:

In this example, the Physical Address is 08-3E-8E-AA-F3-0D, copy it.

To create a new reservation, right-click the Reservations section in the DHCP console and select New Reservation.

Fill in the following fields in the New reservation window:

• Reservation name: specify the network name of the device;
• IP address: specify the IP address from your DHCP scope that you want to assign to the device;
• MAC address: use the physical device address obtained earlier;
• Descriptions: provide a description of the device (optional).

After you have filled in the fields, click the Add button.

If you entered the MAC address in the wrong format, an error will appear “The Unique Identifier you have entered may not be correct. Do you want to use this Identifier anyway?”. In this case, check the MAC address.

Network clients won’t switch to reserved IP addresses automatically. The client will get a new IP address when trying to renew its current lease, on reboot, or when manually use the ipconfig command:

You can manage your reserved IP addresses in the Reservation section. Here you can delete or change the parameters of any DHCP reservation.

Alternatively, you can create a DHCP reservation from the PowerShell command line. To do this, use the Add-DhcpServerv4Reservation cmdlet.

The following command will reserve the leased IP address for a device that has already received an IP address from your DHCP server:

If you need to create a new DHCP reservation for a specific MAC address, use the command:

To create multiple DHCP reservations in bulk, create a CSV file in the following format:

To create reservations for all devices in this file, run the command:

I am a newbie for setting up the server environment and mongoDB. This may sounds something really simple, however, I really need your help on it.

I am trying to connect to my virtual machine which runs the mongodb instance from the local machine, which I believe should be similar to the production environment when I run it on a separate remote server.

The environment is as following:

Private IP for virtual machine: 192.168.184.155

Public IP for both local machine and virtual machine: 96.88.169.145

I changed the bind_ip in /etc/mongod.conf file from

After I restarted the mongod service, neither the virtual machine nor the local machine can access mongodb through mongodb command and giving me the following error.

However, if I change the

and restart the service, it works and I can access using mongo from my local machine. It seems just not work with multiple ip addresses. I tried to do look up in the mongodb document, however, they does mention that bind_ip takes a comma separated list, which really confused me.

Thanks for your help in advance.

18 Answers 18

You can now choose to sort by Trending, which boosts votes that have happened recently, helping to surface more up-to-date answers.

Trending is based off of the highest score sort and falls back to it if no posts are trending.

Wrap the comma-separated-Ips with brackets works in mongo 3.2.7 for me:

With the following version of MongoDB: MongoDB shell version v3.6.10

Reproducing Problem: When [127.0.0.1,xxx.xxx.xxx.xxx] is used we get the following error. Scalar option ‘net.bindIp’ must be a single value try ‘mongod –help’ for more information

Analysis This is because, according to MongoDB Documentation:

net.bindIP is of type “string“.

Solution for binding multiple IP Addresses

Note: No spaces after commas

You can do that by:

Remember to not put a space after the comma.

Thanks for @wdberkeley and @anhlc brought up the clue.

I looked at the log file under /var/log/mongodb/mongod.log. It shows the failing reason for the problem.

So the mongo.conf file is sensitive to space, which I happened to add and should have noticed. Also just as @anhlc pointed out, 96.88.169.145 is not a valid IP address for VM. So that one also contribute to the error.

Great thanks for both of your help! Hope this may help if someone happened to run into the same problem.

I successfully added a second ip on my version 3.2 service using a comma, no spaces and an FQDN

I am running 3.6 on SUSE 12.x and had an issues using comma separated IP lists. I fixed the issue by bindIp: 0.0.0.0

In my case the solution was to put the comma separated IP and without any spaces.

That way worked:

mongod –version db version v3.6.3 git version: 9586e557d54ef70f9ca4b43c26892cd55257e1a5 OpenSSL version: OpenSSL 1.1.0g 2 Nov 2017 allocator: tcmalloc modules: none build environment: distarch: x86_64 target_arch: x86_64

The default /etc/mongod.conf file has this entry for network interfaces:

This corresponds to the –bind-ip arg parameter on the command line. Notice the dash notation converted to camel case. To expose the database running in a VM to the host, it’s simplest to bind the database to all interfaces for testing purposes. This will cover situations where the VM is using a NAT interface or bridged interface. The command line parameter is –bind_ip_all which does not have a parameter, it’s existence corresponds to the bindIPAll: true parameter in the configuration file. Therefore, the configuration file should be changed to:

Notice the bindIp parameter is removed.

It should also be noted that it is possible to add parameters to the command line that override parameters in the config file. Normally, mongod is run with the –config /etc/mongod.conf parameter. It’s easier to change the config file instead of hunting down the script what runs it as a daemon and getting systemd to reload and use it.

For details on the YAML-ness of the config file vs. parameters on the command line, see the documentation currently at

If you are running mongod on a VM using NAT, the default port 27017 will not be exposed to the host. It will be necessary to map a port on the host to this port in the guest VM. That’s beyond the scope of this answer, but a little research will provide a method used for the VM software you are using (VirtualBox, VMware, etc.)

This section describes how multiple IP addresses can be used in LoadRunner Enterprise .

Multiple IP addresses overview

Application servers and network devices use IP addresses to identify clients. The application server often caches information about clients coming from the same machine. Network routers try to cache source and destination information to optimize throughput. If many users have the same IP address, both the server and the routers try to optimize. Since Vusers on the same load generator have the same IP address, server and router optimizations do not reflect real-world situations.

The Multiple IP Addresses feature enables Vusers running on a single load generator to be identified by many IP addresses. The server and router recognize the Vusers as coming from different load generators and as a result, the testing environment is more realistic.

This feature can be implemented on Windows and Linux platforms with the following protocols:

DNS, IMAP, Oracle NCA, Oracle Web Applications 11i, POP3, RTE, SAP-Web, Siebel-Web, SMTP, Web (HTTP/HTML), Web Services, and Windows Sockets.

Note: IP spoofing should be disabled for Dockerized load generators.

Enable IP spoofing

The following steps describe how to add IP addresses to a load generator to enable IP Spoofing.

Create multiple IP addresses on the load generator

Windows: Run the IP Wizard to create multiple IP addresses. For details on running the IP Wizard, see IP Wizard.

The new IP addresses are added to the load generator once and are used for all performance tests. After running the wizard, restart the load generator machine.

Linux: Manually configure the new IP addresses for Linux load generators. For details, see Configure multiple IP addresses on Linux.

Update the server’s routing table with the new addresses

Once the client machine has new IP addresses, the server needs the addresses in its routing table, so that it can recognize the route back to the client. If the server and client share the same netmask, IP class, and network, the server’s routing table does not require modification.

Note: If there is a router between the client and server machines, the server needs to recognize the path via the router. Make sure to add the following to the server routing table:

A route from the web server to the router,

Routes from the router to all of the IP addresses on the load generator.

Update the web server routing table as follows:

Edit the batch file that appears in the IP Wizard Summary page. An example .bat file is shown below.

For each occurrence of [CLIENT_IP], insert your IP address instead.

Run the batch file on the server machine.

Enable the Multiple IP Addresses feature from LoadRunner Enterprise

After you define multiple IP addresses, you set an option to tell the Controller to use this feature.

1. In LoadRunner Enterprise , click Open the navigation toolbar and select Test Management (under Testing). Select a performance test in the test management tree and click Edit Test. In the Groups and Workload tab, select More > Test Options in the Groups pane toolbar, and in the General section select Enable IP Spoofer.

Note: You must select this option before running a performance test.

Specify how the Controller should allocate the IP addresses: per process or per thread. For details, see the Controller’s general run option settings described in Configure IP spoofing and advance warning settings.

Configure multiple IP addresses on Linux

The following section describe how to manually configure multiple IP addresses on the Linux load generator.

1. To define multiple IP addresses for a single Ethernet card, you need IP Aliasing compiled into the kernel. To do this, use the ifconfig command: /sbin/ifconfig eth0:0 x.x.x.x netmask 255.255.x.x up

Substitute the new IP address for x.x.x.x, and insert the correct information for subnet mask. Place this command in the rc.local file so that it executes upon boot.

IP Wizard

This wizard enables you to create and save new IP addresses on Windows machines.

Use one of the following:

Start > Program Files > Micro Focus > LoadRunner Enterprise Host > Tools > IP Wizard

From the LoadRunner Enterprise Host’s \bin directory, run ipwizard.exe.

The IP wizard resides on each load generator.

The new addresses can be a range of addresses defined by the Internet Assignment Numbers Authority. They are for internal use only, and cannot connect to the Internet. This range of addresses is the default used by the IP Wizard.

The IP Wizard only works on machines with a fixed IP, not on machines with a DHCP.

Before any of the changes can take effect, you must restart the machine after you run the wizard, and the web server’s routing table may need to be updated.

IP Wizard Welcome – Step 1 of 3

User interface elements are described below:

Enables you to define new IP settings on the load generator.

Enables you to use an existing file with IP address settings.

Restores original settings.

IP Wizard – Step 2 of 3 (Optional)

User interface elements are described below (unlabeled elements are shown in angle brackets):

If you have more than one network card, enables you to choose the card to use for IP addresses.

This step enables the IP Wizard to check the server’s routing table to see if it requires updating after new IP addresses are added to the load generator.

IP Wizard – Step 3 of 3 (Optional)

User interface elements are described below:

Opens the Add dialog box, enabling you to add a new IP address.

Private Address Spaces. The class that represents the correct submask for the machine’s IP addresses.

From IP. Adds IP addresses starting with this number.

Submask. IP addresses include two components, a netid and hostid. The submask determines where the netid portion of the address stops and where the hostid begins.

Number to add. The number of IP addresses to add.

Verify that new IP addresses are not already in use. Instructs the IP Wizard to check the new addresses. The IP Wizard adds only the addresses that are not already in use.

Removes a selected IP Address.

The IP addresses on the load generator machine.

The submasks of the IP addresses on the load generator machine.

The number of IP addresses added to the load generator machine.

IP Wizard – Summary

User interface elements are described below (unlabeled elements are shown in angle brackets):

Displays a summary of the operations performed by the IP Wizard.

Take note of the location of the batch file (.bat). This is used to update the routing table if necessary. See Enable IP spoofing.

If you updated the routing table, rebooting initializes the Windows device drivers with the new addresses.

Comments

ghost commented Jun 25, 2020 •

IMPORTANT NOTE : The issue is caused by Windows. I have just tested barrier across two Linux systems and it was working fine. Both of the two Linux system are reporting only one IP address that is also bolded.

Operating Systems

Server: Windows 10 Enterprise N 1909 18363

Client: Debian 10.2 KDE

Barrier Version

Windows Version 2.3.2-snapshot-210c2b70
Linux Version 2.2.0-Release-00000000

Steps to reproduce bug

1. I pick the Windows machine to be a Server (share it’s mouse and keyboard)
2. Under the “IP addresses” I see multiple entries one with bolded text
3. The IP with bolded text is the VMware Adapted for Virtual Machines
4. The other IP addresses are also adapters for different program that require networking protocols access
5. The last IP is the IP address of the actual computer on the local network.
6. I don’t know which IP address to fill in when filling the “Server IP” on the Client (Linux Debian) machine.

Other info

• Previously I’ve encountered the “Cannot write into configuration file bug” error that occurred only on Windows. I used a workaround fix in which you interactively configure the server after that you save the configuration into a file manually and then you mark “Use existing configuration” with the proper path to the configuration file
• When I fill in the original IP address of the computer and click “Start” on both ends I see the “Barrier is starting” text and the “Start” button changes to “Stop” but I don’t see any connection happening
• Does this bug prevent you from using Barrier entirely? > Yes

I don’t see any error messages popping up. I’ve also setup the next client in the “Configure Server” window, properly positioned the location of the other monitor and renamed it’s “Screen name” to the one I see written in the client’s side. I am not sure if I’m filling the IP address in properly since there is multiple IPs.

The text was updated successfully, but these errors were encountered:

This article describes how to install and configure a Dynamic Host Configuration Protocol (DHCP) Server in a Workgroup.

Applies to: В Windows Server 2012 R2
Original KB number: В 323416

Summary

This step-by-step article describes how to configure a new Windows Server 2003-based Dynamic Host Configuration Protocol (DHCP) server on a stand-alone server, which can provide centralized management of IP addresses and other TCP/IP configuration settings for the client computers on a network.

How to Install the DHCP Service

Before you configure the DHCP service, you must install it on the server. DHCP is not installed by default during a typical installation of Windows Standard Server 2003 or Windows Enterprise Server 2003. You can install DHCP during the initial installation of Windows Server 2003, or after the initial installation is completed.

How to Install the DHCP Service on an Existing Server

1. Click Start, point to Control Panel, and then click Add or Remove Programs.
2. In the Add or Remove Programs dialog box, click Add/Remove Windows Components.
3. In the Windows Components Wizard, click Networking Services in the Components list, and then click Details.
4. In the Networking Services dialog box, click to select the Dynamic Host Configuration Protocol (DHCP) check box, and then click OK.
5. In the Windows Components Wizard, click Next to start Setup. Insert the Windows Server 2003 CD-ROM into the computer’s CD-ROM or DVD-ROM drive if it is prompted to do so. Setup copies the DHCP server and tool files to your computer.
6. When Setup is completed, click Finish.

How to Configure the DHCP Service

After you have installed the DHCP service and started it, you must create a scope. The scope is a range of valid IP addresses available for lease to the DHCP client computers on the network. Microsoft recommends that, each DHCP server in your environment has at least one scope that does not overlap with any other DHCP server scope in your environment. In Windows Server 2003, DHCP servers in an Active Directory-based domain must be authorized to prevent rogue DHCP servers from coming online. Any Windows Server 2003 DHCP Server that determines itself to be unauthorized will not manage clients.

How to Create a New Scope

1. Click Start, point to Programs, point to Administrative Tools, and then click DHCP.
2. In the console tree, right-click the DHCP server on which you want to create the new DHCP scope, and then click New Scope.
3. In the New Scope Wizard, click Next, and then type a name and description for the scope. The name can be anyone that you want, but it should be descriptive enough so that you can identify the purpose of the scope on your network (for example, you can use a name such as “Administration Building Client Addresses”). Click Next.
4. Type the range of addresses that can be leased as part of this scope. For example, use a range of IP addresses from a starting IP address of 192.168.100.1 to an ending address of 192.168.100.100. Because these addresses are given to clients, they must all be valid addresses for your network and not currently in use. If you want to use a different subnet mask, type the new subnet mask. Click Next.
5. Type any IP addresses that you want to exclude from the range that you entered. These addresses include any one in the range described in step 4 that may have already been statically assigned to various computers in your organization. Typically, domain controllers, Web servers, DHCP servers, Domain Name System (DNS) servers, and other servers, have statically assigned IP addresses. Click Next.
6. Type the number of days, hours, and minutes before an IP address lease from this scope expires. It determines how long a client can hold a leased address without renewing it. Click Next, and then click Yes, I want to configure these options now to extend the wizard to include settings for the most common DHCP options. Click Next.
7. Type the IP address for the default gateway that should be used by clients that obtain an IP address from this scope. Click Add to add the default gateway address in the list, and then click Next.
8. If you are using DNS servers on your network, type your organization’s domain name in the Parent domain box. Type the name of your DNS server, and then click Resolve to make sure that your DHCP server can contact the DNS server and determine its address. Click Add to include that server in the list of DNS servers that are assigned to the DHCP clients. Click Next, and then follow the same steps. If you are using a Windows Internet Naming Service (WINS) server, by adding its name and IP address, click Next.
9. Click Yes, I want to activate this scope now to activate the scope and allow clients to obtain leases from it, and then click Next.
10. Click Finish.
11. In the console tree, click the server name, and then click Authorize on the Action menu.

Troubleshooting

The following sections explain how to troubleshoot some of the issues that you may experience, when you try to install and configure a Windows Server 2003-based DHCP server in a workgroup.

Clients Cannot Obtain an IP Address

If a DHCP client does not have a configured IP address, it typically indicates that the client was not able to contact a DHCP server. This issue can be caused by a network problem, or because the DHCP server is unavailable. When the DHCP server started and other clients can obtain valid addresses, verify that the client has a valid network connection and that all the related client hardware devices (including cables and network adapters) are working properly.

The DHCP Server Is Unavailable

When a DHCP server does not provide leased addresses to clients, it is frequently because the DHCP service did not start. In this case, the server may not be authorized to operate on the network. If you were previously able to start the DHCP service, use Event Viewer to check the System log for any entries. These logs may explain why you cannot start the DHCP service.

To restart the DHCP service:

1. Click Start, and then click Run.
2. Type cmd, and then press ENTER.
3. Type net start dhcpserver , and then press ENTER.

1. Click Start, point to Control Panel, point to Administrative Tools, and then click Computer Management.
2. Expand Services and Applications, and then click Services.
3. Locate and then double-click DHCP Server.
4. Verify that Startup is set to Automatic and that Service Status is set to Started. If not, click Start.
5. Click OK, and then close the Computer Management window.

References

For additional information about DHCP in Windows Server 2003, click the following article number to view the article in the Microsoft Knowledge Base:
169289 DHCP (Dynamic Host Configuration Protocol) Basics
167014 DHCP Client May Fail to Obtain a DHCP-Assigned IP Address
133490 Resolving Duplicate IP Address Conflicts on a DHCP Network

Every Cloud Servers will include a public IP address through which the server can be accessed remotely. The IP can be set as either DHCP (automatic) configuration or static IP configuration. DHCP configuration detects IP address setting automatically, whereas static IP configuration requires the IP address settings to be manually set in the server.

This guide outlines the basic steps on how to configure the IP address of your server manually in your Linux or Windows Cloud Servers. The same steps can also be used to update the new IP address in the server manually.

Windows OS

Click Start Menu , then click Control Panel option.

Click Network & Sharing Center option.

Click Change adapter settings in the left panel.

Right-click adapter with the name Ethernet and select Properties .

In the properties window, select Internet Protocol Version 4 (TCP/IPv4) and click Properties button.

Select Use the following IP address: option and configure the static IP address.

Example for 203.86.232.249:

Note: The netmask is 255.255.255.0 and the gateway is 203.86.232.1.

Once IP and Subnet are entered, check the box Validate Settings upon exit , click OK and then close the Ethernet property window.

Windows Network Diagnostic tool will run to check to see any issues, close this window.

To check if the static IP address is configured properly, right-click Start Menu , then click Command Prompt .

Execute the following command for checking network configuration.

AlmaLinux

Edit the network configuration file using the below command.

NOTE: ens3 is the device name of the server. Please replace with the correct device name if necessary.

Change the value of BOOTPROTO to static from dhcp and then add the following entries in the network card to configure the static IP address.

Example for 203.86.232.249:

Note: The netmask is 255.255.255.0 and the gateway is 203.86.232.1.

Restart the network service and make the changes effect.

Check the static IP address configured properly inside the network card.

Rocky Linux

Edit the network configuration file using the below command.

NOTE: ens3 is the device name of the server. Please replace with the correct device name if necessary.

Change the value of BOOTPROTO to static from dhcp and then add the following entries in the network card to configure the static IP address.

Example for 203.86.232.142:

Note: The netmask is 255.255.255.0 and the gateway is 203.86.232.1.

Restart the network service and make the changes effect.

Check the static IP address configured properly inside the network card.

Ubuntu

Edit the network configuration file using the below command.

Add the following entries for the network card and configure the static IP address.

Example for 203.86.232.249:

Note: The netmask is 255.255.255.0 and the gateway is 203.86.232.1.

Restart the network service and make the changes effect.

Check the static IP address configured properly inside the network card.

Ubuntu 17.10 and higher versions use NetPlan as the default network management tool and its configuration files are written in YAML syntax with a .yaml file extension .

Edit the network configuration file using the below command.

Example for 203.86.232.249:

NOTE: Change the name of the ethernet interface on your server.

Update networking with the below command and then the changes will take effect.

Debian

Edit the network configuration file using the below command.

Add the following entries for the network card and configure the static IP address.

Example for 203.86.232.249:

Note: The netmask is 255.255.255.0 and the gateway is 203.86.232.1.

Restart the network service and make the changes effect.

Check the static IP address configured properly inside the network card.

CentOS – 8

Edit the network configuration file using the below command.

Note: eth1/ens1 is the device name of the server. Please replace with the correct device name if necessary.

Change the value of BOOTPROTO to static from dhcp and then add the following entries in the network card to configure the static IP address.

Example for 203.86.232.249:

Note: The netmask is 255.255.255.0 and the gateway is 203.86.232.1.

Restart the network service and make the changes effect.

Check the static IP address configured properly inside the network card.

CentOS – 6 / 7

Edit the network configuration file using the below command.

Note: eth1/ens1 is the device name of the server. Please replace with the correct device name if necessary.

Change the value of BOOTPROTO to static from dhcp and then add the following entries in the network card to configure the static IP address.

Example for 203.86.232.249:

Note: The netmask is 255.255.255.0 and the gateway is 203.86.232.1.

Restart the network service and make the changes effect.

Check the static IP address configured properly inside the network card.

Fedora

Edit the network configuration file using the below command.

Note: eth1/ens1 is the device name of the server. Please replace with the correct device name if necessary.

Change the value of BOOTPROTO to static from dhcp and then add the following entries in the network card to configure the static IP address.

Example for 203.86.232.249:

Note: The netmask is 255.255.255.0 and the gateway is 203.86.232.1.

Restart the network service and make the changes effect.

Check the static IP address configured properly inside the network card.

Note: The netmask is 255.255.255.0 and the gateway is 203.86.232.1.

Restart the network service and make the changes effect.

Check the static IP address configured properly inside the network card.