Win2k and Win98se machine not connecting

I have four machines on my network that were all connecting up until about 2
weeks ago. Since then I have not been able to connect the Win2k and one
Win98 SE machine.

I can ping the Win98 SE machine from all the other machines and from the
Win2k machine, the win98 SE machine answers. However I cannot ping any
machine from the Win98 machine.

When I open network neighborhood on the Win98 SE machine it takes forever
while it looks for the other computers, sometimes it finds them, however
when you click on them an error message says Computer not accessible network
path not available.

I have one other Win98 SE machine and one WinME and they can see and connect
to the Win98 SE machine.

The Win2K machine can neither see or connect to the Win2k machine.

R Hyte

I figured it out.

The old router was configured to only assign IPs between 192.168.0.2 and
192.168.0.6. The new router was assigning the one machine 192.168.0.8 so it
was outside of all the other computers trusted zones on the PC Firewalls.
Pinging would work because all the other machines were with-in the trusted
range however replies from that machine were refused because of the IP
range.

Finally I have something to show for my weeks worth of tinkering.

R Hyte

"Hyte News" wrote in message
...
I have four machines on my network that were all connecting up until about
2
weeks ago. Since then I have not been able to connect the Win2k and one
Win98 SE machine.

I can ping the Win98 SE machine from all the other machines and from the
Win2k machine, the win98 SE machine answers. However I cannot ping any
machine from the Win98 machine.

When I open network neighborhood on the Win98 SE machine it takes forever
while it looks for the other computers, sometimes it finds them, however
when you click on them an error message says Computer not accessible
network
path not available.

I have one other Win98 SE machine and one WinME and they can see and
connect
to the Win98 SE machine.

The Win2K machine can neither see or connect to the Win2k machine.

R Hyte

I figured it out.

The old router was configured to only assign IPs between 192.168.0.2 and
192.168.0.6. The new router was assigning the one machine 192.168.0.8 so it
was outside of all the other computers trusted zones on the PC Firewalls.
Pinging would work because all the other machines were with-in the trusted
range however replies from that machine were refused because of the IP
range.

Finally I have something to show for my weeks worth of tinkering.

R Hyte

"Hyte News" wrote in message
...
I have four machines on my network that were all connecting up until about
2
weeks ago. Since then I have not been able to connect the Win2k and one
Win98 SE machine.

I can ping the Win98 SE machine from all the other machines and from the
Win2k machine, the win98 SE machine answers. However I cannot ping any
machine from the Win98 machine.

When I open network neighborhood on the Win98 SE machine it takes forever
while it looks for the other computers, sometimes it finds them, however
when you click on them an error message says Computer not accessible
network
path not available.

I have one other Win98 SE machine and one WinME and they can see and
connect
to the Win98 SE machine.

The Win2K machine can neither see or connect to the Win2k machine.

R Hyte

good show :

"Hyte News" wrote in message
...
I figured it out.

The old router was configured to only assign IPs between 192.168.0.2 and
192.168.0.6. The new router was assigning the one machine 192.168.0.8 so
it
was outside of all the other computers trusted zones on the PC Firewalls.
Pinging would work because all the other machines were with-in the trusted
range however replies from that machine were refused because of the IP
range.

Finally I have something to show for my weeks worth of tinkering.

R Hyte

"Hyte News" wrote in message
...
I have four machines on my network that were all connecting up until
about
2
weeks ago. Since then I have not been able to connect the Win2k and one
Win98 SE machine.

I can ping the Win98 SE machine from all the other machines and from the
Win2k machine, the win98 SE machine answers. However I cannot ping any
machine from the Win98 machine.

When I open network neighborhood on the Win98 SE machine it takes forever
while it looks for the other computers, sometimes it finds them, however
when you click on them an error message says Computer not accessible
network
path not available.

I have one other Win98 SE machine and one WinME and they can see and
connect
to the Win98 SE machine.

The Win2K machine can neither see or connect to the Win2k machine.

R Hyte

good show :

"Hyte News" wrote in message
...
I figured it out.

The old router was configured to only assign IPs between 192.168.0.2 and
192.168.0.6. The new router was assigning the one machine 192.168.0.8 so
it
was outside of all the other computers trusted zones on the PC Firewalls.
Pinging would work because all the other machines were with-in the trusted
range however replies from that machine were refused because of the IP
range.

Finally I have something to show for my weeks worth of tinkering.

R Hyte

"Hyte News" wrote in message
...
I have four machines on my network that were all connecting up until
about
2
weeks ago. Since then I have not been able to connect the Win2k and one
Win98 SE machine.

I can ping the Win98 SE machine from all the other machines and from the
Win2k machine, the win98 SE machine answers. However I cannot ping any
machine from the Win98 machine.

When I open network neighborhood on the Win98 SE machine it takes forever
while it looks for the other computers, sometimes it finds them, however
when you click on them an error message says Computer not accessible
network
path not available.

I have one other Win98 SE machine and one WinME and they can see and
connect
to the Win98 SE machine.

The Win2K machine can neither see or connect to the Win2k machine.

R Hyte