How to Statically Change IP Address, Subnet Mask, and Confirm You Can Still Send and Receive Packets. How to Enable DHCP and Communicate on a Network. How to Create and Use an Ad-hoc

by ShadeArrow13 in Circuits > Tools

14489 Views, 9 Favorites, 0 Comments

How to Statically Change IP Address, Subnet Mask, and Confirm You Can Still Send and Receive Packets. How to Enable DHCP and Communicate on a Network. How to Create and Use an Ad-hoc

CMD.png
Control Panel.jpg

This is a basic guide on how to change certain network features on your computer. This tutorial will be done in Windows 10 for convenience use.

How to Statically Change an IP Address and Subnet Mask

CMD.png
Control Panel.jpg

Changing one is very simple. All you need is Control Panel and Command Prompt (will be referred as cmd from now on).

Opening Up Pop-up on the Taskbar

step one.PNG

Right click on the Wi-Fi/Network icon.

Click on Open Network and Sharing Center

Screenshot (12).png

Changing Adapter Settings

Network and Sharing Center.PNG
step2.PNG

In the Network and Sharing Center Area there is a blue link to change adapter settings. Click on that.

Right Click on the Ethernet Option

Screenshot (13).png
Screenshot (14).png
step3.PNG

Right click on it and select Properties.

Click on the IPv4 Option and Click Properties

step31.PNG
IP Properties.PNG
step32.PNG

Click on the IPv4 Section and click properties.

Can click on the option in the Center and get the first picture instead.

Select the "Use the Following IP Address:"

step34.PNG

Type in the numbers for the IP address you wish to change to. There are four octets and different number for the octets signify different areas on the IP addresses. If you don't know which one you want, look it up because there are both public and private IP addresses and also reserved sections not used.

If Needed, Changing the Subnet Mask

step33.PNG
step34.PNG

The subnet mask is just below the IP address that can be changed. Needs four octets like the IP address. Can use zeroes in it though.

Pop-up on the picture.

Testing to See If You Can Still Send and Recieve Packets (Hint: You Should Still Be Able To)

cmdstep.PNG
Capture.PNG

Click Windows tab in bottom right of the taskbar. Type in cmd and right click on it. Select "Run as administrator". When the cmd opens, type in ipconfig. See the results. Type in ping ###.###.###.### (# being your numbers to input in to ping another machine). Should say that there were four sent and four received.

Obtaining a DHCP and Communicating on a Network

Go through steps of changing and IPv4 connection statically until getting to step nine. Then it changes at step nine, but is still similar to it.

Set to Automatically Obtain "DNS Server Address Automatically"

step33.PNG
DNS.PNG

Click option to set it to automatic.

Open Cmd and Ping Another Machine

cmdstep.PNG
Capture.PNG

Ad-hocing

Connect a Wifi Adapter of Some Kind

wifi adapter.png

Can be USB or anything that gives Wi-Fi.

Start Setting Up the Network by Showing Drivers

adhoc 1.PNG
adhoc 2.PNG

Type in 'netsh wlan show drivers' and you will get a long list of text.

Setting Up the Network Mode, Name, and Password

adhoc 4.PNG
adhoc 3.PNG

Type in 'netsh wlan set hostednetwork mode = allow SSID = ******* key = ******** '

Asterisks/stars are what user inputs that they wish the name and password is.

Starting the Network

Captureadhoc5.PNG

Type in 'netsh wlan start hostenetwork'.

Will get a response in return that says you started it.

Connect Another User to the Network

Screenshot (11).png

Adding another user is easy. Have another machine connect to the Network that was just created like anytime you try to connect to a network.

For this picture I had to connect to it by adding name and password myself through Hidden Network, but it will show up there if done properly.

Ping Each Other's Machines

Capture.PNG

This is to make sure that the other machine is on the network. Once they both have a reply then the machine that is connected can use the network.

Footnotes: Anything You Should Know Before Attempting This

1.) Know the vocabulary when researching how to do these three things

2.) It's okay to research things that you don't know

3.) If you are in the cmd and says something that does not look like the pinging that was in the picture before, that has to do with the network or a computer on the network. Usually it's because the user did something wrong or because of default values (i.e. firewall is up), not the network.

4.) Make sure you follow the directions carefully when doing the tasks because (especially in ad-hocing) it can be easy to mess up. This includes typing in something wrong in cmd and it does nothing or gives a error message.

5.) Do not get mad at an error occurring. All that means is something went wrong, so fix it. It also could be showing that you should try a different way.

6.) When implementing these steps, you need either an Ethernet cord/cable or something that uses Wi-Fi (i.e. adapter, dongle, USB, etc.)

6. cont.) If you are using an Ethernet cord/cable, make sure that the cord/cable is fully connected on both ends.

6. cont.) If you are using something for the Wi-Fi, make sure that it is screwed in, fully connected, or whatever else that is being used for Wi-Fi.

Note: Step 0,1, and 14 images are not my own. They are from google images when searching for cmd, control panel, and wifi adapter.