NAT question
arsham
hello
must i use private ip addresses in my entire network when i am using NAT or
connection sharing?
when i share m y internet connection, it automatically changes my lan
adaptor settings to using private address like 192.168.0.1
best regards
Arsham
__________ Information from ESET Smart Security, version of virus signature database 4201 (20090630) __________
The message was checked by ESET Smart Security.
Chris M
> must i use private ip addresses in my entire network when i am using NAT
> or connection sharing?
> when i share m y internet connection, it automatically changes my lan
> adaptor settings to using private address like 192.168.0.1
Broadly speaking the whole point of NAT is so that you don't need a
public IP address for each of your internal machines.
You don't *have* to use private IP addresses on the Internal network,
but Internet Connection Sharing won't let you do it any other way. If
you want to do something more elaborate than basic NAT with 192.168.0.x
as your internal network, you'll need to use some other NAT routing
software/hardware like RRAS.
Chris.
John R
"arsham" <mohsen.far...@live.com> wrote in message
news:9C97DC70-59C1-4653...@microsoft.com...
> hello
> must i use private ip addresses in my entire network when i am using NAT
> or connection sharing?
> when i share m y internet connection, it automatically changes my lan
> adaptor settings to using private address like 192.168.0.1
>
Yes. Using NAT means that your internal private IP addresses are getting
wrapped and sent out using a routable public IP address. This allows you to
share a single (or maybe more) routable public IP address with multiple
internal devices. That's just how it works.
John R
JohnB
That's the downside to ICS; the subnet that it uses for your LAN isn't
configurable, it must be 192.168.0.0
http://support.microsoft.com/kb/306126
"arsham" <mohsen.far...@live.com> wrote in message
news:9C97DC70-59C1-4653...@microsoft.com...
John R
"JohnB" <jbr...@yahoo.com> wrote in message
news:%23tVtOfm%23JHA...@TK2MSFTNGP04.phx.gbl...
> That's the downside to ICS; the subnet that it uses for your LAN isn't
> configurable, it must be 192.168.0.0
>
> http://support.microsoft.com/kb/306126
>
More importantly, that is how it works.
Using NAT means that your internal private IP addresses are getting wrapped
and sent out using a routable public IP address. This allows you to share a
single (or maybe more) routable public IP address with multiple internal
devices.
By definition, ICS means you are sharing your connection. The 192.168.0.x
subnet is private class C address space. The fact that it limits you to
192.168.0 is not important, this subnet is enough for 254 devices. If you
are sharing more than that, you should not be using ICS. Shoot, if you
sharing more than 15 or 20 you should not be using ICS. If 192.168.0
interferes with other private address space networks on your LAN, again, you
should not be using ICS. ICS was designed for the home user with limited
networking abilities to share a few computers with a single
DSL/Cable/dial-up connection without configuring a router.
Simply replacing ICS with a cable/dsl router will give you all the
functionality you need to overcome any ICS issues you might have. If you
insist on using dial-up, and your network is that complex, get an RRAS
server.
John R
Lawrence Garvin [MVP]
news:h2f516$dds$1...@aioe.org...
> arsham wrote:
>> must i use private ip addresses in my entire network when i am using NAT
>> or connection sharing?
>> when i share m y internet connection, it automatically changes my lan
>> adaptor settings to using private address like 192.168.0.1
>
> Broadly speaking the whole point of NAT is so that you don't need a public
> IP address for each of your internal machines.
>
> You don't *have* to use private IP addresses on the Internal network,
But you *should* use private IP Addresses on the Internal network, because
if you don't, whichever non-private IP network you usurp for your use will
be inaccessible to you on the public Internet -- because any traffic to that
real public network will be stuck inside your private network.
The fact is.. there's no good reason NOT to use private IP addresses behind
a NAT router.
--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
PAJ
<lawr...@news.postalias> wrote:
>The fact is.. there's no good reason NOT to use private IP addresses behind
>a NAT router.
In your opinion!
I never use NAT. I have no need for it and cannot be bothered with the
extra hassle in getting everything working with it.
SIP works better without it and that is good enough reason for me.
Lawrence Garvin [MVP]
news:cglg5597uh93pfadm...@4ax.com...
> On Fri, 10 Jul 2009 18:56:27 -0500, "Lawrence Garvin [MVP]"
> <lawr...@news.postalias> wrote:
>
>>The fact is.. there's no good reason NOT to use private IP addresses
>>behind
>>a NAT router.
>
Then this conversation is pointless.. because you "never use NAT".
The thread is about scenarios that DO use NAT.
--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
MS WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
PAJ
<lawr...@news.postalias> wrote:
>"PAJ" <ne...@news-only.invalid> wrote in message
>news:cglg5597uh93pfadm...@4ax.com...
>> On Fri, 10 Jul 2009 18:56:27 -0500, "Lawrence Garvin [MVP]"
>> <lawr...@news.postalias> wrote:
>>
>>>The fact is.. there's no good reason NOT to use private IP addresses
>>>behind
>>>a NAT router.
>>
>> I never use NAT.
>
>Then this conversation is pointless.. because you "never use NAT".
>
>The thread is about scenarios that DO use NAT.
No it was not! You brought a NAT router into it.
The OP wrote:
"must i use private ip addresses in my entire network when i am using
NAT or
connection sharing?
when i share m y internet connection, it automatically changes my lan
adaptor settings to using private address like 192.168.0.1"
So follow the thread properly. There's a good boy.
Lawrence Garvin [MVP]
>>>> The fact is.. there's no good reason NOT to use private IP addresses
>>>> behind a NAT router.
>>> I never use NAT.
>>Then this conversation is pointless.. because you "never use NAT".
>>
>>The thread is about scenarios that DO use NAT.
> No it was not! You brought a NAT router into it.
>
> The OP wrote:
>
> "must i use private ip addresses in my entire network when i am using
> NAT or connection sharing?"
<sigh>... "connection sharing" employs NAT. "connection sharing" *requires*
the use of private addresses.
The *option* to use, or not use, private addresses does not apply to
"connection sharing", it ONLY applies to NAT devices.
Note, also, the subject of this thread: "NAT question".
> So follow the thread properly. There's a good boy.
The condescension is unnecessary. Shame on me for feeding the trolls.
PAJ
<lawr...@news.postalias> wrote:
><sigh>... "connection sharing" employs NAT. "connection sharing" *requires*
>the use of private addresses.
>The condescension is unnecessary. Shame on me for feeding the trolls.
You had already used it in your first reply and continue to do so with
the term <sigh> so stop being a pompous dipshit. It was humour. Fool!
Resorting to the troll insult also shows you cannot win any argument.
Pot, kettle, black. Now go back to your mommy.