In the TCP/IP properties you can set the IP address. WHAT IP address?

On a P2P LAN are you setting the address of the machine you are on or are
you setting the address of the other computer you want it to look for and
connect to?


JimL

--

America always does the right thing, but only after exhausting all other possibilities, Winston
Churchhill.

inkleputDEL@ETEisp.com wrote:

> In the TCP/IP properties you can set the IP address. WHAT IP address?
>
> On a P2P LAN are you setting the address of the machine you are on or are
> you setting the address of the other computer you want it to look for and
> connect to?

You are setting the IP address of your very own, local computer.

Malke
--
MS-MVP
Elephant Boy Computers
www.elephantboycomputers.com
Don't Panic!

Malke <malke@invalid.invalid> said:



>inkleputDEL@ETEisp.com wrote:

>> In the TCP/IP properties you can set the IP address. WHAT IP address?
>>
>> On a P2P LAN are you setting the address of the machine you are on or are
>> you setting the address of the other computer you want it to look for and
>> connect to?

>You are setting the IP address of your very own, local computer.

>Malke

Thank you very much.

I wonder what damage it would cause documentation writers if they actually
said, "the IP address of THIS COMPUTER."

JimL

--

America always does the right thing, but only after exhausting all other possibilities, Winston
Churchhill.

inkleputDEL@ETEisp.com wrote:


>
> I wonder what damage it would cause documentation writers if they actually
> said, "the IP address of THIS COMPUTER."
>

I don't suppose it would cause any damage but then I don't suppose anyone
who has the vaguest idea of what an IP address is would even consider that
you would be setting anything other than your own machine's IP address from
that location.

If you really thought otherwise, then you are most probably unique and can
take comfort in your individuality.

Malke
--
MS-MVP
Elephant Boy Computers
www.elephantboycomputers.com
Don't Panic!

Malke <malke@invalid.invalid> said:

>inkleputDEL@ETEisp.com wrote:


>>
>> I wonder what damage it would cause documentation writers if they actually
>> said, "the IP address of THIS COMPUTER."
>>

>I don't suppose it would cause any damage but then I don't suppose anyone
>who has the vaguest idea of what an IP address is would even consider
>that you would be setting anything other than your own machine's IP
>address from that location.

>If you really thought otherwise, then you are most probably unique and
>can take comfort in your individuality.

>Malke

An IP address on the internet is a destination to look for.

Given that no instance of the instruction specifies location, I can think
of no reason it wold be odd to think the entry might mean the same thing
when setting up your network.

Now if you requalify your statement to say anyone who has previous
_successful_ experience with setting up networks and understands them, you
might have a point.

Tell me, what happens to your sneering grin when you encounter a page with
a whole list of IP addresses to fill in? If you say you've never seen
such a thing you're even less experienced than me and that's saying a
great big mouthful.

JimL

--

It's been said Pelosi should be slapped silly, but that condition has been in effect long since.

On Tue, 06 May 2008 10:36:24 -0400, inkleputDEL@ETEisp.com wrote:

> Malke <malke@invalid.invalid> said:

>>inkleputDEL@ETEisp.com wrote:

>>> I wonder what damage it would cause documentation writers if they actually
>>> said, "the IP address of THIS COMPUTER."

>>I don't suppose it would cause any damage but then I don't suppose anyone
>>who has the vaguest idea of what an IP address is would even consider
>>that you would be setting anything other than your own machine's IP
>>address from that location.
>
>>If you really thought otherwise, then you are most probably unique and
>>can take comfort in your individuality.

> An IP address on the internet is a destination to look for.

And IP address, in general, is a unique machine identifier; sort of like the
address on the outside of your house. Whose street address would you put on
the front of your own house?

> Given that no instance of the instruction specifies location, I can think
> of no reason it wold be odd to think the entry might mean the same thing
> when setting up your network.

If you understand the concept that an IP address is used to identify a
specific device, then it would stand to reason that, when configuring a
device, you would use the IP address which that device will use to identify
itself.

> Now if you requalify your statement to say anyone who has previous
> _successful_ experience with setting up networks and understands them, you
> might have a point.

I gather that it never occurred to you why they publish that "Networking for
Dummies" book? Surely you know the one:

Home Networking for Dummies, by Kathy Ivens. Published by John Wiley & Sons
Inc.
ISBN 0-764-50857-1

No, I did not use that book; but there were other networking books which I
picked up when I first attempted to set up a network:

Mastering Home Networking, by Mark Henricks. Published by Sybex.
ISBN 0-7821-2630-8
NetWare to NT Complete, by Arnold Villeneuve & Wayne McKinnon. Published by
McGraw Hill.
ISBN 0-07-913171-9
Novell's Dictionary of Networking, by Peter Dyson. Published by Sybex.
ISBN 0-7821-1494-6

Considering that networking has been built into Windows since Windows for
Workgroups 3.11, any OS tech help book would have revealed that, as well.

When I bought a horse, I did not just buy a saddle, throw it on, and start
riding. I didn't just climb into a car and start driving. And, while it is
certainly possible (and utterly stupid) to do so, I did not just by a gun
and start shooting. Some things require a rational approach.

Oh, and there are a number of web sites dedicated to home networking
assistance; a few of which are especially geared to newbies.

> Tell me, what happens to your sneering grin when you encounter a page with
> a whole list of IP addresses to fill in? If you say you've never seen
> such a thing you're even less experienced than me and that's saying a
> great big mouthful.

The very first list of IP addresses that I saw was a Unix hosts file at
Hewlett Packard Corporation. At that time, the IP address was a baffling
concept to me. Just four years ago, the subnet mask was a baffling concept
to me. Google was very much my friend in that situation...allow me to
introduce him (and one of his buddies, as well):

http://www.google.com/
http://find.copernic.com/

--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum

"N. Miller" <anonymous@msnews.aosake.net> said:

>I gather that it never occurred to you why they publish that "Networking
>for Dummies" book? Surely you know the one:

>Home Networking for Dummies, by Kathy Ivens. Published by John Wiley &
>Sons Inc.

I do not deny being a dummy about networking. I have read all kinds of
things in all kinds of places, over and over again. It's interesting that
almost anyone who gets networking invariably assumes that one who doesn't
understand it is a total lazy ass who never attempts so much as to lift a
finger. I've seen that so many times in so many places it's nausiating.

Surely you can find something clever and derogatory to say about the fact
that I literally can't remember 5% of what I read any more. I'll not
explain why, because that invites a whole new level of sneer about
something that can't possibly be grasped by those who haven't been there.

JimL

--

It's been said Pelosi should be slapped silly, but that condition has been in effect long since.

On Tue, 06 May 2008 14:07:51 -0400, inkleputDEL@ETEisp.com wrote:

> "N. Miller" <anonymous@msnews.aosake.net> said:

>>I gather that it never occurred to you why they publish that "Networking
>>for Dummies" book? Surely you know the one:

>>Home Networking for Dummies, by Kathy Ivens. Published by John Wiley &
>>Sons Inc.

> I do not deny being a dummy about networking. I have read all kinds of
> things in all kinds of places, over and over again. It's interesting that
> almost anyone who gets networking invariably assumes that one who doesn't
> understand it is a total lazy ass who never attempts so much as to lift a
> finger. I've seen that so many times in so many places it's nausiating.

The basic information is out there. If you didn't grasp it from the basic
information available, I don't know what to think. Despite the claims of
publishers of OSes and networking hardware, networking isn't easy. Deity
knows I see all kinds of troubles people get into because they thought the
manufacturers claims of "ease of use" were factual. All the Wizards on all
of the D-Link, Linksys, and Netgear install disks are often no help when a
newbie gets into trouble.

But, if you had truly "read all kinds of things in all kinds of places", you
would not have made this basic error:

"An IP address on the internet is a destination to look for."

Most people don't look for a destination, they already know it, in the form
of a "Fully Qualified Domain Name" (Google it, and learn something new). If
they don't know a destination, they search (Google) using key words, not IP
addresses. The finding of IP addresses is a, largely, transparent ("behind
the scenes") operation of the ISP DNS servers. End users, even experienced
ones, generally don't worry about IP addresses in the normal course of
surfing the Internet.

Technically, (and, having "read all kinds of things in all kinds of places",
you should have known this) an IP address is a unique device address on an
IP network. Every device on an IP network must have a unique IP address.
Including the one from which requests are made to other machines, using
either FQDNs, or IP addresses (if known).

> Surely you can find something clever and derogatory to say about the fact
> that I literally can't remember 5% of what I read any more. I'll not
> explain why, because that invites a whole new level of sneer about
> something that can't possibly be grasped by those who haven't been there.

The "* for Dummies" series of books is a time honored series of primers,
written with self-deprecatory humor, which taught my parents much about
computers. My mother recently shipped off her "MS DOS for Dummies" and
"Windows for Dummies" books to the Goodwill. Maybe some other, less
sensitive, newbie will find them useful. The authors of the books start out
from the premise that they, themselves, are among the "Dumbest Dummies" to
lay hands on whatever the topic of their book is about.

--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum

> On Tue, 06 May 2008 14:07:51 -0400, inkleputDEL@ETEisp.com wrote:
>
>> "N. Miller" <anonymous@msnews.aosake.net> said:
>
>>> I gather that it never occurred to you why they publish that
>>> "Networking for Dummies" book? Surely you know the one:
>
>>> Home Networking for Dummies, by Kathy Ivens. Published by John
>>> Wiley & Sons Inc.
>
>> I do not deny being a dummy about networking. I have read all kinds
>> of things in all kinds of places, over and over again. It's
>> interesting that almost anyone who gets networking invariably
>> assumes that one who doesn't understand it is a total lazy ass who
>> never attempts so much as to lift a finger. I've seen that so many
>> times in so many places it's nausiating.
>
> The basic information is out there. If you didn't grasp it from the
> basic information available, I don't know what to think. Despite the
> claims of publishers of OSes and networking hardware, networking
> isn't easy. Deity knows I see all kinds of troubles people get into
> because they thought the manufacturers claims of "ease of use" were
> factual. All the Wizards on all of the D-Link, Linksys, and Netgear
> install disks are often no help when a newbie gets into trouble.
>
> But, if you had truly "read all kinds of things in all kinds of
> places", you would not have made this basic error:
>
> "An IP address on the internet is a destination to look for."
>
> Most people don't look for a destination, they already know it, in
> the form of a "Fully Qualified Domain Name" (Google it, and learn
> something new). If they don't know a destination, they search
> (Google) using key words, not IP addresses. The finding of IP
> addresses is a, largely, transparent ("behind the scenes") operation
> of the ISP DNS servers. End users, even experienced ones, generally
> don't worry about IP addresses in the normal course of surfing the
> Internet.
>
> Technically, (and, having "read all kinds of things in all kinds of
> places", you should have known this) an IP address is a unique device
> address on an IP network. Every device on an IP network must have a
> unique IP address. Including the one from which requests are made to
> other machines, using either FQDNs, or IP addresses (if known).
>
>> Surely you can find something clever and derogatory to say about the
>> fact that I literally can't remember 5% of what I read any more.
>> I'll not explain why, because that invites a whole new level of
>> sneer about something that can't possibly be grasped by those who
>> haven't been there.
>
> The "* for Dummies" series of books is a time honored series of
> primers, written with self-deprecatory humor, which taught my parents
> much about computers. My mother recently shipped off her "MS DOS for
> Dummies" and "Windows for Dummies" books to the Goodwill. Maybe some
> other, less sensitive, newbie will find them useful. The authors of
> the books start out from the premise that they, themselves, are among
> the "Dumbest Dummies" to lay hands on whatever the topic of their
> book is about.

Wow, must be a full moon tonight! You're quite the idiot.

"Twayne" <nobody@devnull.spamcop.net> wrote in message
news:eyePo2LsIHA.2208@TK2MSFTNGP04.phx.gbl...
>> On Tue, 06 May 2008 14:07:51 -0400, inkleputDEL@ETEisp.com wrote:
>>
>>> "N. Miller" <anonymous@msnews.aosake.net> said:
>>
>>>> I gather that it never occurred to you why they publish that
>>>> "Networking for Dummies" book? Surely you know the one:
>>
>>>> Home Networking for Dummies, by Kathy Ivens. Published by John
>>>> Wiley & Sons Inc.
>>
>>> I do not deny being a dummy about networking. I have read all kinds
>>> of things in all kinds of places, over and over again. It's
>>> interesting that almost anyone who gets networking invariably
>>> assumes that one who doesn't understand it is a total lazy ass who
>>> never attempts so much as to lift a finger. I've seen that so many
>>> times in so many places it's nausiating.
>>
>> The basic information is out there. If you didn't grasp it from the
>> basic information available, I don't know what to think. Despite the
>> claims of publishers of OSes and networking hardware, networking
>> isn't easy. Deity knows I see all kinds of troubles people get into
>> because they thought the manufacturers claims of "ease of use" were
>> factual. All the Wizards on all of the D-Link, Linksys, and Netgear
>> install disks are often no help when a newbie gets into trouble.
>>
>> But, if you had truly "read all kinds of things in all kinds of
>> places", you would not have made this basic error:
>>
>> "An IP address on the internet is a destination to look for."
>>
>> Most people don't look for a destination, they already know it, in
>> the form of a "Fully Qualified Domain Name" (Google it, and learn
>> something new). If they don't know a destination, they search
>> (Google) using key words, not IP addresses. The finding of IP
>> addresses is a, largely, transparent ("behind the scenes") operation
>> of the ISP DNS servers. End users, even experienced ones, generally
>> don't worry about IP addresses in the normal course of surfing the
>> Internet.
>>
>> Technically, (and, having "read all kinds of things in all kinds of
>> places", you should have known this) an IP address is a unique device
>> address on an IP network. Every device on an IP network must have a
>> unique IP address. Including the one from which requests are made to
>> other machines, using either FQDNs, or IP addresses (if known).
>>
>>> Surely you can find something clever and derogatory to say about the
>>> fact that I literally can't remember 5% of what I read any more.
>>> I'll not explain why, because that invites a whole new level of
>>> sneer about something that can't possibly be grasped by those who
>>> haven't been there.
>>
>> The "* for Dummies" series of books is a time honored series of
>> primers, written with self-deprecatory humor, which taught my parents
>> much about computers. My mother recently shipped off her "MS DOS for
>> Dummies" and "Windows for Dummies" books to the Goodwill. Maybe some
>> other, less sensitive, newbie will find them useful. The authors of
>> the books start out from the premise that they, themselves, are among
>> the "Dumbest Dummies" to lay hands on whatever the topic of their
>> book is about.
>
> Wow, must be a full moon tonight! You're quite the idiot.
>

Bam, three posts in a row from you helping the OP not one jot, doing nothing
but adding gratuitous insults to responders - "closed mind spews its
tripe", "balderdash spewed out... get a life" & "quite the idiot". What's
your problem, for crying out loud??

That was rhetorical.

*plonk*