[windows2000] Re: 192.168.*.* - why?
- From: "Sullivan, Glenn" <GSullivan@xxxxxxxxxxxxxx>
- To: "'windows2000@xxxxxxxxxxxxx'" <windows2000@xxxxxxxxxxxxx>
- Date: Mon, 18 Nov 2002 12:58:54 -0500
The internet backbone routers don't locate anything. They accept a packet
on port X from address number xxx.xxx.xxx.xxx and look up in their routing
tables to see which port they need to forward the packet to to get it to its
destination address yyy.yyy.yyy.yyy.
It so happens that most of these internet backbone routers are configured
to, if they see some of these reserved addresses (the 192.168 ranges, for
example, to bring this back to Ray's question) as a destination address,
drop these packets.
It has nothing to do with DNS, which is the process (or server) which
translate an English-readable Fully Qualified Domain Name to a numeric IP
address. By the time the backbone routers get a hold of a packet the DNS
process is long since completed, usually by the originating machine.
At least the last time I checked...
Glenn Sullivan, MCSE+I MCDBA
David Clark Company Inc.
-----Original Message-----
From: Jeff Stockard [mailto:JStockard@xxxxxxxxxxxxxxx]
Sent: Monday, November 18, 2002 12:49 PM
To: windows2000@xxxxxxxxxxxxx
Subject: [windows2000] Re: 192.168.*.* - why?
The Internet backbone routers use DNS to locate addresses. 10.x.x.x
address are ignored by the Internet backbone routers. For this reason
many companies use this address scheme in their private networks. =20
-----Original Message-----
From: Sullivan, Glenn [mailto:GSullivan@xxxxxxxxxxxxxx]=20
Sent: Monday, November 18, 2002 12:46 PM
To: windows2000@xxxxxxxxxxxxx
Subject: [windows2000] Re: 192.168.*.* - why?
OK, but what does that have to do with DNS? They don't mention DNS in
that
blurb.
Glenn Sullivan, MCSE+I MCDBA
David Clark Company Inc.
-----Original Message-----
From: Jeff Stockard [mailto:JStockard@xxxxxxxxxxxxxxx]
Sent: Monday, November 18, 2002 12:30 PM
To: windows2000@xxxxxxxxxxxxx
Subject: [windows2000] Re: 192.168.*.* - why?
From this site on IP addresses:
http://www.oreilly.com/catalog/coreprot/chapter/appb.html
Where it says "there are groups of "private" Internet addresses that can
be used on internal networks by anyone. These address pools were set
aside in RFC 1918, and therefore cannot be "assigned" to any
organization. The Internet's backbone routers are configured explicitly
not to route packets with these addresses, so they are completely
useless outside of an organization's internal network. The address
blocks available are listed in Table B-4."
Any addresses in 10.x.x.x
-----Original Message-----
From: Daniel Ensor [mailto:densor@xxxxxxxxx]=3D20
Sent: Monday, November 18, 2002 11:59 AM
To: windows2000@xxxxxxxxxxxxx
Subject: [windows2000] Re: 192.168.*.* - why?
Dark N' snowy??
-----Original Message-----
From: Robert Funderburk [mailto:robfunderburk@xxxxxxxxxxx]
Sent: Monday, November 18, 2002 4:54 PM
To: windows2000@xxxxxxxxxxxxx
Subject: [windows2000] Re: 192.168.*.* - why?
What are you talking about with "outside DNS" ?
----- Original Message -----
From: "Jeff Stockard" <JStockard@xxxxxxxxxxxxxxx>
To: <windows2000@xxxxxxxxxxxxx>
Sent: Monday, November 18, 2002 10:52 AM
Subject: [windows2000] Re: 192.168.*.* - why?
>
> That was my point. They don't have anything to do with outside DNS.
If
> you used an address that was in the outside DNS range, you would be
> continually looking to the DNS table to find other PC's on your
network.
>
> -----Original Message-----
> From: Sullivan, Glenn [mailto:GSullivan@xxxxxxxxxxxxxx]=3D3D20
> Sent: Monday, November 18, 2002 9:20 AM
> To: windows2000@xxxxxxxxxxxxx
> Subject: [windows2000] Re: 192.168.*.* - why?
>
>
> <----------Snip-------->
> Companies use theses schemes so their requests for data will not look
to
> the
> outside DNS list. This makes the lookup a little faster, when you can
> skip
> the rest of the entire Internet and just look on your Intranet.
> <----------Snip-------->
>
> What do you mean? These reserved address ranges really don't have
> anything
> to do with DNS, to my knowledge.
>
> A little confused I guess. That's what happens when you wake up with
> three
> inches of ice covering everything...
>
> Glenn Sullivan, MCSE+I MCDBA
> David Clark Company Inc.
>
>
> -----Original Message-----
> From: Jeff Stockard [mailto:JStockard@xxxxxxxxxxxxxxx]
> Sent: Monday, November 18, 2002 9:12 AM
> To: windows2000@xxxxxxxxxxxxx
> Subject: [windows2000] Re: 192.168.*.* - why?
>
>
>
> They are non routable. The same is true with 10.x.x.x. Companies use
> theses schemes so their requests for data will not look to the outside
> DNS list. This makes the lookup a little faster, when you can skip
the
> rest of the entire Internet and just look on your Intranet.
> Hope this helps
> Jeff
> Jesus Loves You
>
> -----Original Message-----
> From: Costanzo, Ray [mailto:rcostanzo@xxxxxxxxxxx]=3D3D3D20
> Sent: Monday, November 18, 2002 8:59 AM
> To: windows2000@xxxxxxxxxxxxx
> Subject: [windows2000] 192.168.*.* - why?
>
>
> Hi list,
>
> I'm just curious about something. It seems that most networks use
> 192.168.*.* for their internal addresses. Why? It doesn't really
> matter, does it? Isn't 192.168.*.* completely arbitrary? My theory
on
> how this came to be the norm is that MS used those addresses in some
> samples in some books or something, and people started using that and
it
> just became the norm. But then there's that whole Internet connection
> sharing feature that came out in what, W98SE? With that, the computer
> that's sharing its Internet connection will be 192.168.1.1. So, I
> imagine that it's coded somewhere into other OS'es to look to see if
> 192.168.1.1 can be used as a gateway when the user does not specify an
> IP configuration. So what came first? 192.168.*.* or computers
looking
> to 192.168.1.1 as a gateway? Or what my real question is is why
> 192.168.*.*?
>
> Thanks,
>
> Ray at work
>
>
> **********************************************************************
> This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they
> are addressed. If you have received this email in error please notify
> the system manager.
>
> This footnote also confirms that this email message has been swept by
> MIMEsweeper for the presence of computer viruses.
>
> www.mimesweeper.com
> **********************************************************************
>
>
>
=3D3D3D3D=3D3D3D3D=3D3D3D3D=3D3D3D3D=3D3D3D3D=3D3D3D3D=3D3D3D3D=3D3D3D3D=3D=
3D3D3D=3D3D3D3D=3D3
D=3D
3D3D=3D3D3D3D=3D3D3D3D=3D3D3D3D=3D3D3
D=3D3D
> =
3D=3D3D3D3D=3D3D3D3D=3D3D3D3D=3D3D3D3D=3D3D3D3D=3D3D3D3D=3D3D3D3D=3D3D3D3=
D=3D3D3D3D
> =3D3D3D3D=3D3D3D
> =
=3D3D3D3D=3D3D3D3D=3D3D3D3D=3D3D3D3D=3D3D3D3D=3D3D3D3D=3D3D3D3D=3D3D3D3D=3D=
3D3D3D
> To Unsubscribe, set digest or vacation
> mode or view archives use the below link.
>
> http://thethin.net/win2000list.cfm
>
>
=3D3D3D=3D3D3D=3D3D3D=3D3D3D=3D3D3D=3D3D3D=3D3D3D=3D3D3D=3D3D3D=3D3D3D=3D=
3D3D=3D3D3D=3D3D3D=3D3D3D=3D3
D=3D
3D=3D3D3D=3D3D3D=3D3D3D=3D3D3D=3D3D3D=3D3D3D=3D3D3D=3D3D3D=3D3D3D
=3D3D3D=3D3D
> =3D3D3D=3D3D3D=3D3D3D=3D3D3D=3D3D3D=3D3D3D=3D3D3D=3D3D3D=3D3D3D
> To Unsubscribe, set digest or vacation
> mode or view archives use the below link.
>
> http://thethin.net/win2000list.cfm
>
>
=3D3D3D=3D3D3D=3D3D3D=3D3D3D=3D3D3D=3D3D3D=3D3D3D=3D3D3D=3D3D3D=3D3D3D=3D=
3D3D=3D3D3D=3D3D3D=3D3D3D=3D3
D=3D
3D=3D3D3D=3D3D3D=3D3D3D=3D3D3D=3D3D3D=3D3D3D=3D3D3D=3D3D3D=3D3D3D
=3D3D3D=3D3D
> =3D3D3D=3D3D3D=3D3D3D=3D3D3D=3D3D3D=3D3D3D=3D3D3D=3D3D3D=3D3D3D
> To Unsubscribe, set digest or vacation
> mode or view archives use the below link.
>
> http://thethin.net/win2000list.cfm
>
> =3D
=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D=
3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D
=3D3D=3D
=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D
> To Unsubscribe, set digest or vacation
> mode or view archives use the below link.
>
> http://thethin.net/win2000list.cfm
=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D=
3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D
=3D3D=3D
=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D
To Unsubscribe, set digest or vacation
mode or view archives use the below link.
http://thethin.net/win2000list.cfm
=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D=
3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D
=3D3D=3D
=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D
To Unsubscribe, set digest or vacation
mode or view archives use the below link.
http://thethin.net/win2000list.cfm
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
To Unsubscribe, set digest or vacation
mode or view archives use the below link.
http://thethin.net/win2000list.cfm
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
To Unsubscribe, set digest or vacation
mode or view archives use the below link.
http://thethin.net/win2000list.cfm
==================================
To Unsubscribe, set digest or vacation
mode or view archives use the below link.
http://thethin.net/win2000list.cfm
==================================
To Unsubscribe, set digest or vacation
mode or view archives use the below link.
http://thethin.net/win2000list.cfm
Other related posts:
