Ping times out

I have two Win98 (non-SE) PCs networked together simply
via a crossover cable. Each one can see the other in
Network Neighborhood. I can copy files between each
system. Multiplayer games that use IPX work fine. Each
machine can successfully ping itself (both the assigned IP
address and 127.0.0.1) but neither can ping the other;
returns "request timed out". What could be wrong?

Turn off your firewalls.


"Steve B." <(E-Mail Removed)> wrote in message
news:420c01c3d021$eb69bf20$(E-Mail Removed)...
> I have two Win98 (non-SE) PCs networked together simply
> via a crossover cable. Each one can see the other in
> Network Neighborhood. I can copy files between each
> system. Multiplayer games that use IPX work fine. Each
> machine can successfully ping itself (both the assigned IP
> address and 127.0.0.1) but neither can ping the other;
> returns "request timed out". What could be wrong?

The firewall (ZoneAlarm) is not on when I am doing the
Ping. I have ZoneAlarm set up to only start when I
connect to the internet.

>-----Original Message-----
>Turn off your firewalls.
>
>
>"Steve B." <(E-Mail Removed)> wrote in
message
>news:420c01c3d021$eb69bf20$(E-Mail Removed)...
>> I have two Win98 (non-SE) PCs networked together simply
>> via a crossover cable. Each one can see the other in
>> Network Neighborhood. I can copy files between each
>> system. Multiplayer games that use IPX work fine. Each
>> machine can successfully ping itself (both the assigned
IP
>> address and 127.0.0.1) but neither can ping the other;
>> returns "request timed out". What could be wrong?
>
>
>.
>

Set the second computer on an ip address one off from the
first. e.g 127.0.0.1 and the other should be 127.0.0.2
>-----Original Message-----
>The firewall (ZoneAlarm) is not on when I am doing the
>Ping. I have ZoneAlarm set up to only start when I
>connect to the internet.
>
>>-----Original Message-----
>>Turn off your firewalls.
>>
>>
>>"Steve B." <(E-Mail Removed)> wrote
in
>message
>>news:420c01c3d021$eb69bf20$(E-Mail Removed)...
>>> I have two Win98 (non-SE) PCs networked together
simply
>>> via a crossover cable. Each one can see the other in
>>> Network Neighborhood. I can copy files between each
>>> system. Multiplayer games that use IPX work fine.
Each
>>> machine can successfully ping itself (both the
assigned
>IP
>>> address and 127.0.0.1) but neither can ping the other;
>>> returns "request timed out". What could be wrong?
>>
>>
>>.
>>
>.
>

On Thu, 1 Jan 2004 12:48:04 -0800, "T"
<(E-Mail Removed)> wrote:

>Set the second computer on an ip address one off from the
>first. e.g 127.0.0.1 and the other should be 127.0.0.2

That's wrong. 127.0.0.1 is a loopback address for connecting to your
own machine.


Jim

On Thu, 1 Jan 2004 09:36:28 -0800,
<(E-Mail Removed)> wrote:

>The firewall (ZoneAlarm) is not on when I am doing the
>Ping. I have ZoneAlarm set up to only start when I
>connect to the internet.

That doesn't necessarily mean that ZA isn't the problem. The only way
to know for sure is to remove it completely (including following the
additional instructions on the zonelabs website)


Jim.

Here are more details of my setup. Both PCs are
configured like the following in Win98's Control
Panel/Network:

Client for Microsoft Networks
Dial-Up Adapter
Ethernet Adapter
IPX -> Dial-Up Adapter
IPX -> Ethernet Adapter
NetBEUI -> Dial-Up Adapter
NetBEUI -> Ethernet Adapter
TCP/IP -> Dial-Up Adapter
TCP/IP -> Ethernet Adapter
File and printer sharing for Microsoft Netorks

All protocols are bound to all Clients for the Ethernet
Adapter.
TCP/IP is the only protocol that is bound to the Client
for Microsoft Networks for the Dial-Up Adapter. No other
protocol is bound to any other client for the Dial-Up
Adapter.

PC #1's TCP/IP - Ethernet Adapter IP address is
192.168.0.1 and subnet mask of 255.255.255.0.
PC #2's TCP/IP - Ethernet Adapter IP address is
192.168.0.2 and subnet mask of 255.255.255.0.

They each have unique Computer names and both have a
Workgroup name of Network.
Both PCs are using Windows Logon as the Primary Network
Logon. I've tried having them both use Client for
Microsoft Networks but it didn't make any difference.

If no program or process of ZoneAlarm's is running, it
can't affect the network, can it? I stripped both PCs
down to where the only thing showing up in the Ctrl-Alt-
Del window is Explorer and Systray. I also ran the
Process Viewer that comes with Visual C++ v5 and it showed
the following processes running on both PCs:
PVIEW95.EXE (this is the Process Viewer)
DDHELP.EXE
SYSTRAY.EXE
TASKMON.EXE
EXPLORER.EXE
MMTASK
MPREXE.EXE
MSGSRV32
KERNEL32.DLL
SPOOL32.EXE (PC #1 only because PC #2 shares the printer).

If I run Ping from within a DOS box, I see the PING.EXE
process show up in the process viewer but no other
processes (other than DOS's WINOLDAP).

I can still Ping the local PC successfully both via
127.0.0.1 and 192.168.0.1 (or 2) but cannot Ping the other
PC. I always get Request timed out.

Any other ideas? This should work, right?



>-----Original Message-----
>On Thu, 1 Jan 2004 09:36:28 -0800,
><(E-Mail Removed)> wrote:
>
>>The firewall (ZoneAlarm) is not on when I am doing the
>>Ping. I have ZoneAlarm set up to only start when I
>>connect to the internet.
>
>That doesn't necessarily mean that ZA isn't the problem.
The only way
>to know for sure is to remove it completely (including
following the
>additional instructions on the zonelabs website)
>
>
>Jim.
>
>.
>

I recommend you remove NetBeui and do a manual unstall of ZoneAlarm
(shutting it down does not prevent the preloading of the VXD which can only
be done through a proper uninstall or manuall uninstall, directions for
which can be found on the ZoneLabs web-site).

Carey

"Steve B." <(E-Mail Removed)> wrote in message
news:232e01c3d18c$714fd5f0$(E-Mail Removed)...
> Here are more details of my setup. Both PCs are
> configured like the following in Win98's Control
> Panel/Network:
>
> Client for Microsoft Networks
> Dial-Up Adapter
> Ethernet Adapter
> IPX -> Dial-Up Adapter
> IPX -> Ethernet Adapter
> NetBEUI -> Dial-Up Adapter
> NetBEUI -> Ethernet Adapter
> TCP/IP -> Dial-Up Adapter
> TCP/IP -> Ethernet Adapter
> File and printer sharing for Microsoft Netorks
>
> All protocols are bound to all Clients for the Ethernet
> Adapter.
> TCP/IP is the only protocol that is bound to the Client
> for Microsoft Networks for the Dial-Up Adapter. No other
> protocol is bound to any other client for the Dial-Up
> Adapter.
>
> PC #1's TCP/IP - Ethernet Adapter IP address is
> 192.168.0.1 and subnet mask of 255.255.255.0.
> PC #2's TCP/IP - Ethernet Adapter IP address is
> 192.168.0.2 and subnet mask of 255.255.255.0.
>
> They each have unique Computer names and both have a
> Workgroup name of Network.
> Both PCs are using Windows Logon as the Primary Network
> Logon. I've tried having them both use Client for
> Microsoft Networks but it didn't make any difference.
>
> If no program or process of ZoneAlarm's is running, it
> can't affect the network, can it? I stripped both PCs
> down to where the only thing showing up in the Ctrl-Alt-
> Del window is Explorer and Systray. I also ran the
> Process Viewer that comes with Visual C++ v5 and it showed
> the following processes running on both PCs:
> PVIEW95.EXE (this is the Process Viewer)
> DDHELP.EXE
> SYSTRAY.EXE
> TASKMON.EXE
> EXPLORER.EXE
> MMTASK
> MPREXE.EXE
> MSGSRV32
> KERNEL32.DLL
> SPOOL32.EXE (PC #1 only because PC #2 shares the printer).
>
> If I run Ping from within a DOS box, I see the PING.EXE
> process show up in the process viewer but no other
> processes (other than DOS's WINOLDAP).
>
> I can still Ping the local PC successfully both via
> 127.0.0.1 and 192.168.0.1 (or 2) but cannot Ping the other
> PC. I always get Request timed out.
>
> Any other ideas? This should work, right?
>
>
>
> >-----Original Message-----
> >On Thu, 1 Jan 2004 09:36:28 -0800,
> ><(E-Mail Removed)> wrote:
> >
> >>The firewall (ZoneAlarm) is not on when I am doing the
> >>Ping. I have ZoneAlarm set up to only start when I
> >>connect to the internet.
> >
> >That doesn't necessarily mean that ZA isn't the problem.
> The only way
> >to know for sure is to remove it completely (including
> following the
> >additional instructions on the zonelabs website)
> >
> >
> >Jim.
> >
> >.
> >

Okay, I removed NetBEUI (I didn't have this in there
originally; it didn't work either way) and I uninstalled
ZoneAlarm. I also went through all of the gory details of
editing the registry to clean everything out.

After the reboot...tada...it works.

I will be having a discussion with ZoneAlarm to see if
they want to fix this.

Thanks for all of the help!

>-----Original Message-----
>I recommend you remove NetBeui and do a manual unstall of
ZoneAlarm
>(shutting it down does not prevent the preloading of the
VXD which can only
>be done through a proper uninstall or manuall uninstall,
directions for
>which can be found on the ZoneLabs web-site).
>
>Carey
>
>"Steve B." <(E-Mail Removed)> wrote in
message
>news:232e01c3d18c$714fd5f0$(E-Mail Removed)...
>> Here are more details of my setup. Both PCs are
>> configured like the following in Win98's Control
>> Panel/Network:
>>
>> Client for Microsoft Networks
>> Dial-Up Adapter
>> Ethernet Adapter
>> IPX -> Dial-Up Adapter
>> IPX -> Ethernet Adapter
>> NetBEUI -> Dial-Up Adapter
>> NetBEUI -> Ethernet Adapter
>> TCP/IP -> Dial-Up Adapter
>> TCP/IP -> Ethernet Adapter
>> File and printer sharing for Microsoft Netorks
>>
>> All protocols are bound to all Clients for the Ethernet
>> Adapter.
>> TCP/IP is the only protocol that is bound to the Client
>> for Microsoft Networks for the Dial-Up Adapter. No
other
>> protocol is bound to any other client for the Dial-Up
>> Adapter.
>>
>> PC #1's TCP/IP - Ethernet Adapter IP address is
>> 192.168.0.1 and subnet mask of 255.255.255.0.
>> PC #2's TCP/IP - Ethernet Adapter IP address is
>> 192.168.0.2 and subnet mask of 255.255.255.0.
>>
>> They each have unique Computer names and both have a
>> Workgroup name of Network.
>> Both PCs are using Windows Logon as the Primary Network
>> Logon. I've tried having them both use Client for
>> Microsoft Networks but it didn't make any difference.
>>
>> If no program or process of ZoneAlarm's is running, it
>> can't affect the network, can it? I stripped both PCs
>> down to where the only thing showing up in the Ctrl-Alt-
>> Del window is Explorer and Systray. I also ran the
>> Process Viewer that comes with Visual C++ v5 and it
showed
>> the following processes running on both PCs:
>> PVIEW95.EXE (this is the Process Viewer)
>> DDHELP.EXE
>> SYSTRAY.EXE
>> TASKMON.EXE
>> EXPLORER.EXE
>> MMTASK
>> MPREXE.EXE
>> MSGSRV32
>> KERNEL32.DLL
>> SPOOL32.EXE (PC #1 only because PC #2 shares the
printer).
>>
>> If I run Ping from within a DOS box, I see the PING.EXE
>> process show up in the process viewer but no other
>> processes (other than DOS's WINOLDAP).
>>
>> I can still Ping the local PC successfully both via
>> 127.0.0.1 and 192.168.0.1 (or 2) but cannot Ping the
other
>> PC. I always get Request timed out.
>>
>> Any other ideas? This should work, right?
>>
>>
>>
>> >-----Original Message-----
>> >On Thu, 1 Jan 2004 09:36:28 -0800,
>> ><(E-Mail Removed)> wrote:
>> >
>> >>The firewall (ZoneAlarm) is not on when I am doing the
>> >>Ping. I have ZoneAlarm set up to only start when I
>> >>connect to the internet.
>> >
>> >That doesn't necessarily mean that ZA isn't the
problem.
>> The only way
>> >to know for sure is to remove it completely (including
>> following the
>> >additional instructions on the zonelabs website)
>> >
>> >
>> >Jim.
>> >
>> >.
>> >
>
>
>.
>

It is my pleasure. Thanks for letting us know!

Carey

"Steve B." <(E-Mail Removed)> wrote in message
news:239401c3d214$28d74000$(E-Mail Removed)...
> Okay, I removed NetBEUI (I didn't have this in there
> originally; it didn't work either way) and I uninstalled
> ZoneAlarm. I also went through all of the gory details of
> editing the registry to clean everything out.
>
> After the reboot...tada...it works.
>
> I will be having a discussion with ZoneAlarm to see if
> they want to fix this.
>
> Thanks for all of the help!
>
> >-----Original Message-----
> >I recommend you remove NetBeui and do a manual unstall of
> ZoneAlarm
> >(shutting it down does not prevent the preloading of the
> VXD which can only
> >be done through a proper uninstall or manuall uninstall,
> directions for
> >which can be found on the ZoneLabs web-site).
> >
> >Carey
> >
> >"Steve B." <(E-Mail Removed)> wrote in
> message
> >news:232e01c3d18c$714fd5f0$(E-Mail Removed)...
> >> Here are more details of my setup. Both PCs are
> >> configured like the following in Win98's Control
> >> Panel/Network:
> >>
> >> Client for Microsoft Networks
> >> Dial-Up Adapter
> >> Ethernet Adapter
> >> IPX -> Dial-Up Adapter
> >> IPX -> Ethernet Adapter
> >> NetBEUI -> Dial-Up Adapter
> >> NetBEUI -> Ethernet Adapter
> >> TCP/IP -> Dial-Up Adapter
> >> TCP/IP -> Ethernet Adapter
> >> File and printer sharing for Microsoft Netorks
> >>
> >> All protocols are bound to all Clients for the Ethernet
> >> Adapter.
> >> TCP/IP is the only protocol that is bound to the Client
> >> for Microsoft Networks for the Dial-Up Adapter. No
> other
> >> protocol is bound to any other client for the Dial-Up
> >> Adapter.
> >>
> >> PC #1's TCP/IP - Ethernet Adapter IP address is
> >> 192.168.0.1 and subnet mask of 255.255.255.0.
> >> PC #2's TCP/IP - Ethernet Adapter IP address is
> >> 192.168.0.2 and subnet mask of 255.255.255.0.
> >>
> >> They each have unique Computer names and both have a
> >> Workgroup name of Network.
> >> Both PCs are using Windows Logon as the Primary Network
> >> Logon. I've tried having them both use Client for
> >> Microsoft Networks but it didn't make any difference.
> >>
> >> If no program or process of ZoneAlarm's is running, it
> >> can't affect the network, can it? I stripped both PCs
> >> down to where the only thing showing up in the Ctrl-Alt-
> >> Del window is Explorer and Systray. I also ran the
> >> Process Viewer that comes with Visual C++ v5 and it
> showed
> >> the following processes running on both PCs:
> >> PVIEW95.EXE (this is the Process Viewer)
> >> DDHELP.EXE
> >> SYSTRAY.EXE
> >> TASKMON.EXE
> >> EXPLORER.EXE
> >> MMTASK
> >> MPREXE.EXE
> >> MSGSRV32
> >> KERNEL32.DLL
> >> SPOOL32.EXE (PC #1 only because PC #2 shares the
> printer).
> >>
> >> If I run Ping from within a DOS box, I see the PING.EXE
> >> process show up in the process viewer but no other
> >> processes (other than DOS's WINOLDAP).
> >>
> >> I can still Ping the local PC successfully both via
> >> 127.0.0.1 and 192.168.0.1 (or 2) but cannot Ping the
> other
> >> PC. I always get Request timed out.
> >>
> >> Any other ideas? This should work, right?
> >>
> >>
> >>
> >> >-----Original Message-----
> >> >On Thu, 1 Jan 2004 09:36:28 -0800,
> >> ><(E-Mail Removed)> wrote:
> >> >
> >> >>The firewall (ZoneAlarm) is not on when I am doing the
> >> >>Ping. I have ZoneAlarm set up to only start when I
> >> >>connect to the internet.
> >> >
> >> >That doesn't necessarily mean that ZA isn't the
> problem.
> >> The only way
> >> >to know for sure is to remove it completely (including
> >> following the
> >> >additional instructions on the zonelabs website)
> >> >
> >> >
> >> >Jim.
> >> >
> >> >.
> >> >
> >
> >
> >.
> >