Discussion Locked

Assigning IP addresses on LAN

0 helpful
12 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
When I first set up the network at my office, I had no previous networking experience. When assigning IP addresses I assigned them in order like this... 10.0.0.1 10.0.0.2 10.0.0.3, and so on. Later I was told that if our office ever decided to have internet access (took awhile to convince the boss that it was beneficial) that I would need to redo those addresses. At one time I did try to do so, but ended up with pc's not being able to see each other on the network. Is it necessary to change these ip addresses and if so how should I go about doing so?

12 replies

by scarlett_o

Is there a specific reason you have static IP addresses? If your server is DHCP enabled, the best way to solve the problem would be to change the PC's to Obtain an IP Address automatically. And get to the internet through a DNS server.

by shanghai sam

Changing the addresses isn't required if you use a router or firewall capable of NAT (Network Address Translation) to connect to your ISP. It might be a challenge to convince the boss to spend the money on a firewall, but I wouldn't connect your office to the internet without one.

by shanghai sam

If you do decide to change the addresses the
first thing you should do is, get
information, how many machines, printers,
anything needing an IP address. Discuss with
your peers and/or manager what the
requirements for the business are nowand
what is needed for growth. How is network
currently utiized. Decide on how many subnets
are needed now and how many for growth. With
this information decide on whether it is a
class a, b, c address that is needed. choose
an IP address and do the math for the
subnets. Setup a DHCP, DNS server etc. if so
desired. setup an IP scheme. Which IP's will
be static which ones dynamic, which for
printers, hubs, switches, routers. etc.Make a
batch file to run on login to changeworkstations from static to DHCP if desired.
Get a team in on a weekend and change
everyting. This can be done. I was part of a
6 man team that converted IP's from one set
of IP addresses to another when the company I
worked for was boughtover. Total
workstations about 2500, 150 printers, around
300 hubs 2 switches, and 7 routers. We
started Friday at 6:00pm and finished Sunday
3:00

by pkust

Not only is it not necessary to change IP addresses, it is not even advisable.

If you read RFC1918, you know that 10.0.0.0, along with 172.16.0.0-172.32.255.255, and 192.168.0.0, are designated as "private" IP nets. By administrative fiat, thesenets are not routed across any public Internet segment.

Thus, your network is already ideally positioned for Internet access. By using private IP addresses on your LAN, you are able to use an absolute minimum of public IP addresses, which means you and your ISP will have no problem adhering to the guidelines of RFC2050, which outlines how public addresses should be allocated. Either your Internet router will need to be configured with NAT or you will need to deploy a firewall (which is advisable anyway, for obvious security reasons).

You should be able to incorporate Internet access with few difficulties--fewer, in fact, than if you had not used private IP addresses.

Cordially,

Peter Nayland Kust
TEKMedia Communications
pkust@tekmedia.com
http://www.tekmedia.com

by yagar

I knew about
172.16.0.0 and 192.168.0.0 but not the others. Where can I obtain a copy of RFC1918 and RFC2050

Thanks

by ebob

1 - Keep your 10.a.b.c addresses.
2 - Use NAT and PAT on your firewall. Since you've decided to implement an Ineternet connection, you WILL be using a firewall. Right? (PAT = Port Address Translation, and further extends the capabilities of your address translation). Pick a firewall in keeping with your security requirements, like the size of your network, and just how private you need to be. Oh and you need to consider your budget. The IP address space on the outside of your firewall (aka, "public address" space) will be provided by your ISP. PAT allows you to use a very small address space from your ISP; smaller than the number of users you have inside.

3 - Use DHCP on your LAN. It makes your life as an admin so much easier.

4 - If you really ever do want to redo your addressing scheme (but you probably won't) then you need to route between your 10.a.b.c network and your "public address" space. The simplest way to do this is with a small router with 2 LAN interfaces, one configured on your 10.a.b.c network and the other on your "public" network.

by samlukecantwell

probably should get a server installed and use DHCP to assign... easy way! this option would be most beneficial for problem solving and future upgrading..

otherwise use class c licenses and assign the correct gateway to were the modem is attached.. c-ya

by marshallkeithusa

You did not say how you were networking but as long as you don't need public addresses for the workstations you will not need to change the addresses just set up a proxy server or set up a linux box using IP masq . . . Good luck . . . .

Marshall

by r_borth

Thanks for all the information. I did not realize that 10.a.b.c was private addressing. The people who did my wiring had told me otherwise. This info helps alot. Thanks again.

Reba

by admin

and are using windows 98 or ME on one machine..

You can just use the built in internet connection sharing with your modem (or router that may be called a modem by your isp i.e. "dsl modem")This will actually require you to use private ip's in your network. There are also other software proxy programs to do this, but this is a free and easy start that takes advantage of your already established private ip scheme.... Some more details would be good too, if you are looking for how to do this. I'd keep the private ip addressing as above though...

This discussion is closed to new replies.