[windows2000] Re: 192.168.*.* - why?
- From: Robert Funderburk <robfunderburk@xxxxxxxxxxx>
- To: windows2000@xxxxxxxxxxxxx
- Date: Mon, 18 Nov 2002 11:51:31 -0500
Huh,
Agreed. What does internal IP's have to do with DNS? I think this person
is confusing DNS with subnet masks.
----- Original Message -----
From: "Sullivan, Glenn" <GSullivan@xxxxxxxxxxxxxx>
To: <windows2000@xxxxxxxxxxxxx>
Sent: Monday, November 18, 2002 9:19 AM
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]=20
> 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
> **********************************************************************
>
>
>
=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
==================================
To Unsubscribe, set digest or vacation
mode or view archives use the below link.
http://thethin.net/win2000list.cfm
Other related posts:
