Peer-to-peer addreses

yes, it would most likely have stopped working when you changed the IP
Address.

An IP address is integral to any network whether that between two computers
like peer to peer or between your computer and the you internet service
provider. They always have meet certain rules in order for it to work
properly.
Thus, just changing an IP address may quite easily cause problems.

--
Jon Hildrum
DTS MVP

www.hildrum.com
wrote in message
...
"Jon_Hildrum" said:

In order to see the other computer both computers need to be on the
same network. Thus, if you use an IP address of 192.168.1.5 with a
netmask of 255.255.255.0 then the other computer must have an IP
address in the range 192.168.1 (between 1and254 excluding 5 with
netmask 255.255.255.0).

Like I said, it has already been working and quit, so I obviously had
these things right.

But what has this to do with the system choking on a manually entered IP
- my actual question?

Jim L via the eCS 1.15 version of OS/2

--
Politicians: Their lips move too much.

yes, it would most likely have stopped working when you changed the IP
Address.

You're misunderstanding completely. I put in an IP address manually
from day one and it worked. Then it QUIT working and Network
Neighborhood couldn't even see the machines own resources. THEN I tried
setting it to auto. That way it sees itself, but not the other
computer. Trying to set it back to the ORIGINAL IP makes the "Entire
Network" inaccessable (per Net Hood).

OK, you've made the standard assumption that a user has no clue about
anything and that there actually is no problem. That doesn't solve the
problem. I'm relatively new to windows, but I've been computer active
for over 25 years (and studied college level computer science). So your
assumption is off. If this is a user error instead of computer problem
it's a very esoteric and indirect one. But judging from the 3 or 4
years experience I _have_ had with windows I have every reason to
suspect otherwise. That is, windows screws up all the time.

Like I indicated in my original question it now "rejects" a manual IP -
- it did NOT before. "Reject" meaning becoming inaccessable when it is
there.

Said differently. Originally it accepted (and worked with) the
192.168.1.5 IP (and 192.168.1.1 on the other machine). Now it doesn't.
So my original question is valid. Why would it be rejecting the
manually entered IP?

An IP address is integral to any network whether that between two
computers like peer to peer or between your computer and the you
internet service provider. They always have meet certain rules in
order for it to work properly.
Thus, just changing an IP address may quite easily cause problems.

Jim L

--
Politicians: Their lips move too much.

yes, it would most likely have stopped working when you changed the IP
Address.

You're misunderstanding completely. I put in an IP address manually
from day one and it worked. Then it QUIT working and Network
Neighborhood couldn't even see the machines own resources. THEN I tried
setting it to auto. That way it sees itself, but not the other
computer. Trying to set it back to the ORIGINAL IP makes the "Entire
Network" inaccessable (per Net Hood).

OK, you've made the standard assumption that a user has no clue about
anything and that there actually is no problem. That doesn't solve the
problem. I'm relatively new to windows, but I've been computer active
for over 25 years (and studied college level computer science). So your
assumption is off. If this is a user error instead of computer problem
it's a very esoteric and indirect one. But judging from the 3 or 4
years experience I _have_ had with windows I have every reason to
suspect otherwise. That is, windows screws up all the time.

Like I indicated in my original question it now "rejects" a manual IP -
- it did NOT before. "Reject" meaning becoming inaccessable when it is
there.

Said differently. Originally it accepted (and worked with) the
192.168.1.5 IP (and 192.168.1.1 on the other machine). Now it doesn't.
So my original question is valid. Why would it be rejecting the
manually entered IP?

An IP address is integral to any network whether that between two
computers like peer to peer or between your computer and the you
internet service provider. They always have meet certain rules in
order for it to work properly.
Thus, just changing an IP address may quite easily cause problems.

Jim L

--
Politicians: Their lips move too much.

control panelnetwork ...remove all instances (tcp/ip etc.)
conotrol paneldevice manager ...remove NIC

reboot and reinstall NIC and network protocals (try on both machines , one
or both machines may have corrupt network settings)
don't forget to re-share drives etc.

--
Please read http://dts-l.org/goodpost.htm on how to post messages to NG's

Windows support http://www.aumha.org

wrote in message
...
yes, it would most likely have stopped working when you changed the IP
Address.

You're misunderstanding completely. I put in an IP address manually
from day one and it worked. Then it QUIT working and Network
Neighborhood couldn't even see the machines own resources. THEN I tried
setting it to auto. That way it sees itself, but not the other
computer. Trying to set it back to the ORIGINAL IP makes the "Entire
Network" inaccessable (per Net Hood).

OK, you've made the standard assumption that a user has no clue about
anything and that there actually is no problem. That doesn't solve the
problem. I'm relatively new to windows, but I've been computer active
for over 25 years (and studied college level computer science). So your
assumption is off. If this is a user error instead of computer problem
it's a very esoteric and indirect one. But judging from the 3 or 4
years experience I _have_ had with windows I have every reason to
suspect otherwise. That is, windows screws up all the time.

Like I indicated in my original question it now "rejects" a manual IP -
- it did NOT before. "Reject" meaning becoming inaccessable when it is
there.

Said differently. Originally it accepted (and worked with) the
192.168.1.5 IP (and 192.168.1.1 on the other machine). Now it doesn't.
So my original question is valid. Why would it be rejecting the
manually entered IP?

An IP address is integral to any network whether that between two
computers like peer to peer or between your computer and the you
internet service provider. They always have meet certain rules in
order for it to work properly.
Thus, just changing an IP address may quite easily cause problems.

Jim L

--
Politicians: Their lips move too much.

control panelnetwork ...remove all instances (tcp/ip etc.)
conotrol paneldevice manager ...remove NIC

reboot and reinstall NIC and network protocals (try on both machines , one
or both machines may have corrupt network settings)
don't forget to re-share drives etc.

--
Please read http://dts-l.org/goodpost.htm on how to post messages to NG's

Windows support http://www.aumha.org

wrote in message
...
yes, it would most likely have stopped working when you changed the IP
Address.

You're misunderstanding completely. I put in an IP address manually
from day one and it worked. Then it QUIT working and Network
Neighborhood couldn't even see the machines own resources. THEN I tried
setting it to auto. That way it sees itself, but not the other
computer. Trying to set it back to the ORIGINAL IP makes the "Entire
Network" inaccessable (per Net Hood).

OK, you've made the standard assumption that a user has no clue about
anything and that there actually is no problem. That doesn't solve the
problem. I'm relatively new to windows, but I've been computer active
for over 25 years (and studied college level computer science). So your
assumption is off. If this is a user error instead of computer problem
it's a very esoteric and indirect one. But judging from the 3 or 4
years experience I _have_ had with windows I have every reason to
suspect otherwise. That is, windows screws up all the time.

Like I indicated in my original question it now "rejects" a manual IP -
- it did NOT before. "Reject" meaning becoming inaccessable when it is
there.

Said differently. Originally it accepted (and worked with) the
192.168.1.5 IP (and 192.168.1.1 on the other machine). Now it doesn't.
So my original question is valid. Why would it be rejecting the
manually entered IP?

An IP address is integral to any network whether that between two
computers like peer to peer or between your computer and the you
internet service provider. They always have meet certain rules in
order for it to work properly.
Thus, just changing an IP address may quite easily cause problems.

Jim L

--
Politicians: Their lips move too much.

"Haggis" said:

control panelnetwork ...remove all instances (tcp/ip etc.)

Thanks, I'll try that. That reminds me, since there is no internal
modem in this particular TP 770E, why does Win98 keep insisting on
putting in clients and protocols for it? That and the infrared. I
remove them and they come right back. I have minimal memory and don't
need extra junk in it.

Jim L via the eCS 1.24 version of OS/2

--
Politicians: Their lips move too much.

"Haggis" said:

control panelnetwork ...remove all instances (tcp/ip etc.)

Thanks, I'll try that. That reminds me, since there is no internal
modem in this particular TP 770E, why does Win98 keep insisting on
putting in clients and protocols for it? That and the infrared. I
remove them and they come right back. I have minimal memory and don't
need extra junk in it.

Jim L via the eCS 1.24 version of OS/2

--
Politicians: Their lips move too much.

"Haggis" said:

control panelnetwork ...remove all instances (tcp/ip etc.) conotrol
paneldevice manager ...remove NIC

reboot and reinstall NIC and network protocals (try on both machines ,
one or both machines may have corrupt network settings)
don't forget to re-share drives etc.

Voila. Thanks.

It took along time to get all the bits and pieces, and things kept
coming back after I deleted them, but by bouncing back and forth between
Network Configuration and Device Manager with a healthy sprinkling of
reboots, I finally got rid of everything but infrared. (As the
understatement of the year, that thing is dogged.)

Plugged the card back in and minutes later everything was working.

What did the trick was staying on it until Network Configuration was
(almost) empty. Without that I could delete the networking items and
they would pop right back up - even though the card was pulled. Made no
sense to me, but when I got past that the reinstall worked.

Thanks again.

Jim L

--
Politicians: Their lips move too much.

"Haggis" said:

control panelnetwork ...remove all instances (tcp/ip etc.) conotrol
paneldevice manager ...remove NIC

reboot and reinstall NIC and network protocals (try on both machines ,
one or both machines may have corrupt network settings)
don't forget to re-share drives etc.

Voila. Thanks.

It took along time to get all the bits and pieces, and things kept
coming back after I deleted them, but by bouncing back and forth between
Network Configuration and Device Manager with a healthy sprinkling of
reboots, I finally got rid of everything but infrared. (As the
understatement of the year, that thing is dogged.)

Plugged the card back in and minutes later everything was working.

What did the trick was staying on it until Network Configuration was
(almost) empty. Without that I could delete the networking items and
they would pop right back up - even though the card was pulled. Made no
sense to me, but when I got past that the reinstall worked.

Thanks again.

Jim L

--
Politicians: Their lips move too much.

"Haggis" said:

Please read http://dts-l.org/goodpost.htm on how to post messages to
NG's

Not everyone can be clones of you and/or perfectly please you. If
people knew how to word a problem in a precisely and techically correct
form, with all the right buzzwords, references and nuances, chances are
they would be expert enough not to need help in the first place. Most
newsgroups are places to get help, not places to be nitpicked to death.
Lighten up for God's sake. What's the point in chasing people away when
they are at rock bottom and least prepared to fulfill your dreams of the
perfect newsgroup user - which, for you, is apparently one who has no
problems and therefore doesn't use the newsgroups?

Jim L

--
Politicians: Their lips move too much.