Assign Fixed Static IP Addresses to Devices on Home Network. If you’re like me, you probably have 2. TVs, Blu- ray players, game consoles, media players, and finally computers. With all those devices, you probably also like to share data and files amongst them. Well, normally that works fine as most of the time the DNS name of the device is used. If the IP address changes, you can still use the DNS name to access the device. However, there are quite a few instances where you end up using the IP address to access a device and if that IP address changes, then you have to reconfigure the device. For example, I have a printer that also scans and will save the file directly to a computer. However, it uses the IP address instead of the name of the machine. Every time the machine reboots, it gets a new IP address and I have to type that new IP into the printer. What a pain! In this article, I’ll show you how you can assign static or fixed IP addresses to the devices on your network without manually configuring each device. For example, you can always assign a static IP address to a Windows 8 PC by going to network settings, but it’s far easier to just assign the static IP address on your router. This saves you from having to configure 2. IP addresses from one central location. Most modern routers have some sort of IP address reservation page or configuration option that you just have to find, usually under the Local Area Network or LAN section. Here I will show you how to do it on an AT& T U- verse router and a Netgear router. Hopefully, it’s pretty much the same on other routers like Belkin and D- Link. Assign Static IP Addresses via Router. To get started, you’ll need to login to your wireless router via a web browser. In order to do this, you’ll need the IP address of your router. If you already know it, then you can skip this section. To figure out your router IP, you can simply look up the default gateway on your computer. Here’s how. Open a command prompt on any PC by following this procedure: Windows XP – Click on Start, click on Run and type in CMDWindows 7 – Click on Start and type in command prompt. Windows 8 – Go to Start screen, right- click, choose All apps, then scroll right and click on Command Prompt. Now at the command prompt, type in the following command, which is just one word: ipconfig. You should get a screen that looks like this: Make sure you are looking at the correct network adapter. For example, you see the above screenshot says Ethernet Adapter Local Area Connection, which is the IP address info for my Ethernet connection. If you are using wireless, it should say Wireless adapter. The ip address you want is the one listed under Default Gateway. Now take this IP address and open a web browser. Type it into the address bar and press enter. This will load the web interface for your wireless router. Note that you will probably have to enter the router username and password in order to gain access. If you never changed it, then you can check out a site called routerpasswords. If you have the original packaging, it should be on there too. Now that you’re in the router, you’ll need to find the section that shows the current IP addresses that have been allocated by the DHCP server. On my AT& T router, I had to click on Settings, then LAN, then IP Address Allocation. To give a device a fixed IP address, just find it in the list and then click on the Address Assignment drop down. By default, it is set to Private from pool: IPRange. From the drop down, you can choose a fixed IP address. Just make sure you don’t pick a fixed IP that is already taken by another device on the network. For my Netgear router, the process was a little different. First, once you logged in, you have to go to Attached Devices to see all the connected devices and their MAC addresses. Find the MAC address for the device you want to give a static IP address to and then click on LAN Setup. Click the Add button under Address Reservation and then either choose from the radio buttons at the top or manually type in info yourself. Static IP Address. This page describes how to assign a "Static IP" to your local computer. If you are looking to get an external static IP, that is. Assign the IP address To set a static IP address: Open Windows Start menu. Open Control Panel. Classic view: Open Network Connections Category view: Select Network. Static NAT (also called inbound mapping) is the first mode we're going to talk about and also happens to be the most uncommon between smaller networks. Static NAT was. That’s about it! This is a much easier way to assign static or fixed IP addresses to devices on your network rather than manually configuring it on the device itself. If you have any problems or issues, post a comment and I’ll try to help. Get A Static IP! How to set a static ip address for your computer (for p. Linux, Windows, and Mac. This page describes how to assign a . All networked computers have IP addresses. Most have a static ip, that is, they don't change (for instance, at the time of writing, Google is 7. Google. That is Google's . But some IP's do change. But if you want to do more; run servers, p. NAT rules on your router, to direct incoming traffic to a particular computer (the one running the server), and if you want those rules to be effective past your next reboot, you will need to get a static IP on your computer, so that the incoming data packets can still find you. Imagine the fun your friends and family would have contacting you if your telephone number changed every day! Only the last number will be different from the address of your router which by default (at least for Voyager routers), lives at 1. In Windows, it's in the Support tab of the connexion's Status dialog. A netstat command will get you the same information (and more) on most platforms, perhaps netstat - n. Your router's web interface will likely have all this information, too.
I'll start with the best place, your gateway router. It's like a static IP, but with NO setup on the computer required. This has many advantages. Because the router is always going to dole out the exact same address to that computer (with that particular MAC), the usual DHCP settings will work fine. Your computer asks for any address, and always gets given the exact same one. It's not possible to give many specifics, because each router is different, but I can tell you that if you use IPCop as your gateway (A Very Good Idea), it's as simple as clicking one of connexions in the . Two clicks, and you're set for life! Whatever its name, if it exists it will likely be in your local (LAN) network/IP settings tab/section. You even can reinstall your computer's operating system, reboot, and there is your static IP again! Control Panel > > Network Connections > > Local Area Connection > > Properties > > TCP/IP > > Properties*phew*. In other words, open the control panel, open Network Connections, right- click the . If you use 1. 92. IP address, the dialog will look something like this. When you're done, okay everything to close all the dialogs. It's smart to use 1. But then, the space for DNS servers is clearer in the Windows box. Seems we all still have a lot to learn from each other. Usually you need to edit some plain text file (as root). On some Linux systems, the settings will be in /etc/rc. I guess it might look something like this. It's usually called something like . In a shell you can probably do . Same story for UNIX, Solaris, BSD, etc. NAT rules will be permanent, and you can dabble in all sorts of interesting and esoteric communications devices, servers and p. You could telnet to your router by simply doing telnet router, for instance. If you develop web sites, this is near essential. See here for more details. If this page didn't help you, tell me about it! You will need to talk to your ISP. Note: Not all ISP's offer this service, and those that do will usually charge a premium. Instead, perhaps you simply need to. And No- IP now require you to manually confirm your domains every 3. So unless you want to pay for your DDNS or lose your domains the next time you are on holiday or just forget, I recommend the aforementioned duck dns, freedns. Very handy for automatic shell scripts, and more. Right now, it's 1. This is very similar to the way you get a new external IP whenever you dial- up to the internet (some folks still do that) or disconnect your ADSL for a few minutes. Although it's usual to get a new external IP when you reconnect your DSL, it's not guaranteed. With some ISP's it happens rarely, with others you need to disconnect for a few minutes or more, with some ISP's, you always get a fresh IP with each connect, no matter how quickly you do it. One thing is certain, though; unless you are paying them for a static IP, your current external IP address will change! Remember, your external IP, and your local computer's IP, are two totally separate things (well, in this context). Almost no one needs a static IP for their external connexion, but almost everyone who wants to run peer- to- peer applications, ftp servers, and so on, will need a static IP for their local computer. The former is supplied by your ISP, the latter is down to you. And how do they work? The IP Mask simply describes which parts of an IP address are not going to change. Simply, 2. 55 means none of the bits can change, 0 means all of the bits can change (it can also be any number in between). What sometimes confuses, is that IP Masks can be expressed in two different ways. While the first is, if you understand what I've said so far, fairly obvious; the second needs a little explanation. Okay, in short, your GATEWAY has your Public IP address, and your desktop computer (and any other machines inside your home/organization) have private IP Addresses. Simply put; it's outside and inside. So, let's say a packet of data from . It leaves their machine, and starts its journey, hop- to- hop, attempting to get to yours. When you first connected to the internet, via your ISP's backbone, they assigned your connexion an IP address (or more than one, in some cases) from a large pool of IP Addresses they own. Any machine sending you a packet of data can reach you at this IP. Every time you access a web page, or FTP site, or game server, or announce yourself to a torrent tracker, or anything; that is the IP Address they see at the other end of the connexion, and that is the address they will send the packets back to. This is your Public IP Address. Anything could happen to it. Once that packet hits your gateway machine, it enters the private domain and what happens next, is up to you. The packet may be on a port you don't know, or don't allow, and may be immediately dropped by your gateway's firewall. The gateway's firewall usually does most of this automatically, sorting out which machines asked for what data, but can also be programmed to forward specific traffic to specific machines, for example, when we create port- forwarding rules for P2. P clients on our desktop computers. If you have lots of machines inside your network, they will each have different private addresses, and with a secure gateway, none of these addresses can ever be seen from the outside (unless you hand it out, for example, in your email headers). I want to host a REAL domain! A REAL site! I NEED an external Static IP! While not recommended for mission- critical applications (there will always be a brief spell after you are assigned a new IP, where the name still points to the old IP - these days increasingly briefer, as DNS systems improve), hosting a . Just like dnydns. DUC and it keeps your domain name pointing at your IP address. And if you head along to namecheap. DNS all at the same time. This is a fine place to add that I consider namecheap to be the best domain registrar in the world. Okay, I might have pushed a little. As breathtakingly simple as this sounds, imagining yourself as a packet of data, traveling from A to B is the fastest way to figure out where the trouble lies. That's all there is to it! Try it; you will not be disappointed with the results. Unless required, it is generally best to disable these interfaces. Another computer on your local network already has the IP you are attempting to assign. It might be something other's could use an answer to.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
November 2017
Categories |