Peer-to-peer addreses

If I specify an IP address in my ethernet protocol properties (Control
Panel -> Networking), Network Neighborhood can't even see the computer
it is on (Network Neighborhood -> Entire Network). It says the network
is inaccessable. If I tell it to get an address automatically Network
Neighborhood pops up the local resources right away. But then I have no
address to give to the other (non-windows) machine.

How can I get it to use a manually entered IP address? (Network
troubleshooting doesn't work. I mark one option, click and get nothing
but a blank page).

Jim

--
Politicians want to know all about security measures. That they don't understand the "need to know" principle proves they should not know.

You need to tell us about your network setup before the question can be
answered.
How is the computer connected ?
Are you using Dial -up ??, ISDN ?? or Cable??
Is the computer connected directly to the modem or do you have a router ???
Where is the other computers you want to provide IP address to ??


--
Jon Hildrum
DTS MVP
(E-Mail Removed)
www.hildrum.com
<(E-Mail Removed)> wrote in message
news:43eee248$2$vaxyrchg$(E-Mail Removed)...
> If I specify an IP address in my ethernet protocol properties (Control
> Panel -> Networking), Network Neighborhood can't even see the computer
> it is on (Network Neighborhood -> Entire Network). It says the network
> is inaccessable. If I tell it to get an address automatically Network
> Neighborhood pops up the local resources right away. But then I have no
> address to give to the other (non-windows) machine.
>
> How can I get it to use a manually entered IP address? (Network
> troubleshooting doesn't work. I mark one option, click and get nothing
> but a blank page).
>
> Jim
>
> --
> Politicians want to know all about security measures. That they don't
> understand the "need to know" principle proves they should not know.

Peer-to-peer, known good crossover cable. One other computer on the
other end of the XO. My internet access is fine.

It has accepted a manually entered IP before and the network worked, but
suddenly won't. (I've since reinstalled the drivers - no change.) I
can set the IP to auto and the (local) network becomes accessable. Set
it to 192.168.1.5 and it becomes inaccessable.

"Jon_Hildrum" <(E-Mail Removed)> said:

>You need to tell us about your network setup before the question can be
> answered.
>How is the computer connected ?
>Are you using Dial -up ??, ISDN ?? or Cable??
>Is the computer connected directly to the modem or do you have a router
>??? Where is the other computers you want to provide IP address to ??

Jim L via the eCS 1.15 version of OS/2

--
Politicians want to know all about security measures. That they don't understand the "need to know" principle proves they should not know.

When set to Auto, the IP address of the computer is assigned by one of the
following:
1. Your internet access provider
2. Your router if you use one for your internet access
3. ICS or similar software if you use it.
You do need to use something if both computers are to have internet access.

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).




--
Jon Hildrum
DTS MVP
(E-Mail Removed)
www.hildrum.com
<(E-Mail Removed)> wrote in message
news:43ef5b19$1$vaxyrchg$(E-Mail Removed)...
> Peer-to-peer, known good crossover cable. One other computer on the
> other end of the XO. My internet access is fine.
>
> It has accepted a manually entered IP before and the network worked, but
> suddenly won't. (I've since reinstalled the drivers - no change.) I
> can set the IP to auto and the (local) network becomes accessable. Set
> it to 192.168.1.5 and it becomes inaccessable.
>
> "Jon_Hildrum" <(E-Mail Removed)> said:
>
>>You need to tell us about your network setup before the question can be
>> answered.
>>How is the computer connected ?
>>Are you using Dial -up ??, ISDN ?? or Cable??
>>Is the computer connected directly to the modem or do you have a router
>>??? Where is the other computers you want to provide IP address to ??
>
> Jim L via the eCS 1.15 version of OS/2
>
> --
> Politicians want to know all about security measures. That they don't
> understand the "need to know" principle proves they should not know.

"Jon_Hildrum" <(E-Mail Removed)> 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.

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
(E-Mail Removed)
www.hildrum.com
<(E-Mail Removed)> wrote in message
news:43ef9a6e$1$vaxyrchg$(E-Mail Removed)...
> "Jon_Hildrum" <(E-Mail Removed)> 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.

control panel>network ...remove all instances (tcp/ip etc.)
conotrol panel>device 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

<(E-Mail Removed)> wrote in message
news:43f0cb89$1$vaxyrchg$(E-Mail Removed)...
> >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" <(E-Mail Removed)> said:

>control panel>network ...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" <(E-Mail Removed)> said:

>control panel>network ...remove all instances (tcp/ip etc.) conotrol
>panel>device 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.