can't ping

[R.H.]

I have a Windows 2000 machine and a windows xp machine. I can ping the
windows xp machine from my windows 2000 machine, but I can't ping my
windows 2000 machine from my windows xp machine. I even turned off the
firewall on my windows 2000 machine, but still nothing. Does anybody
know how to get my xp machine to ping my 2000 machine.

Roger

 

[Mike]

I have a Windows 2000 machine and a windows xp machine. I can ping the
windows xp machine from my windows 2000 machine, but I can't ping my
windows 2000 machine from my windows xp machine. I even turned off the
firewall on my windows 2000 machine, but still nothing. Does anybody
know how to get my xp machine to ping my 2000 machine.

Roger

Assuming that both machines are on the same LAN, make sure they both have
the same subnet mask.

Mike

 

[R.H.]

They do. I attached my laptop to the network which has Windows XP home
verison and the two XP machines can ping each other, but they can not
ping the Windows 2000 machine though the Windows 2000 machine can ping
both XP machines. I was able to get the shared drives to show up
finally, but XP pro machine can access the Windows 2000 shared folders
which seems weird since it can not ping the Windows 2000 machine. But
the XP pro machine is unable to access the XP home version for some
reason though I think it might be a password issue though I am unsure at
this point becasue I changed the guest account to a know password and it
still was not working.

Roger

 

[R.H.]

I can finally network my desktop Windows 2000 and my desktop Windows XP
machine though I still don't quite understand why I can't ping the 2000
machine. Now I am having problems connecting my laptop to the network.
My laptop has Windows XP home version and though my desktop XP machine
can see the laptop it can not access it and in fact it does not even ask
for a password which it should. My laptop can not see or ping anything
though last night it could ping both. I have noticed something
different though my laptop has an incoming connection icon whereas my
desktop does not, does anyone know what this does? At the moment I am
tempted to remove all networking and then reinstall it and see if I can
get it working this way. Can anyone help me?

Roger

 

[Newbie]

is it the name it can't ping or the ip address?

 

[Phill]

You mentioned FIREWALL.
When W2k pings XP machine then all works ok So therefore XP machine can talk
back to W2k. Which means networking is ok, IP addresses and subnet masks.
When you ping are you using IP addresses or names. ie ping 10.1.1.2 or ping
PCone.
If you are using names then try with IP addresses instead.
If you are using ip addresses then the problem points to firewall software
on W2k blocking new incoming IP requests from XP pc but accepting responses
from XP pc to IP requests sent from W2k.

 

[R.H.]

The ip address

Roger

is it the name it can't ping or the ip address?

 

[R.H.]

From my XP machine I can not ping either with an Ip address of with a
name, but I can access the shared files and folders though I noticed
that connecting to the folders on the is intially a bit slow compared to
the Windows 2000 machine connecting to the XP machines's files and folders.

From my Win 2K machine I can ping both with an Ip address and with a
name as well as access the shared files and folders.

I noticed with my Win2k that I had the same problem before I turned off
my firewall. I tried disabling the firewall in XP with regards to the
local network, in the TCP/IP properties on the advanced tab, gut that
did not help. Still though I am wondering if something to do with the
XP firewall, might be causing this. What do you think?

Roger

 

[Marina Roos]

Can you post the ipconfig/al from both machines?

Marina

 

[R.H.]

OK.

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : blacknight
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel 8255x-based PCI
Ethernet Adapter (10/100)
Physical Address. . . . . . . . . : 00-E0-18-00-97-DF
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 169.254.246.216
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . :



Windows XP IP Configuration

Host Name . . . . . . . . . . . . : superwizard
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 CT
Network Connection
Physical Address. . . . . . . . . : 00-0C-6E-6C-EF-3E
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 169.254.246.215
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

 

[Marina Roos]

You haven't got a DHCP-server, so your computers are not getting an
IP-address. How are those machines connecting to each other?
You might give them static IP-s like 192.168.0.1, subnet 255.255.255.0 and
the other machine 192.168.0.2.

Marina

 

[Mike]

If you are able to see the shares, you must be running another protocol
other than TCP/IP. Is this correct?


1.Have you tryed a class C subnet(255.255.255.0)?

2.Have you tryed a different NIC in each box?

3.Are the computers connected together with a crossover or are you using a
hub/switch?

Mike

 

[Mike]

If you are able to see the shares, you must be running another
protocol other than TCP/IP. Is this correct?


1.Have you tryed a class C subnet(255.255.255.0)?

2.Have you tryed a different NIC in each box?

3.Are the computers connected together with a crossover or are you
using a hub/switch?

Mike

I know, I know, Some of you are asking if I have trIed a spelling checker.

Sorry

Mike

 

[R.H.]

I had them configured like that with 192.168.0.1 and 192.168.0.2, but
that was not working either. So, I was tinkering with Windows XP and it
assigned the 169.254.246.215 number so I used that just to see if it
worked. It did not seemed to matter which address scheme I used. Are
you saying that the 169.254.246.215 address scheme is only for dhcp? It
seems to work in any case other than I am unable to ping just like with
the 192.168.0.1 scheme.

Roger

 

[R.H.]

Yes, I am running ipx protocal as well and I was running a class C
before tinkering with Win XP's wizard, but neither way seemed to affect
my ability to ping from the xp machine. As for a different NIC, what
exactly would that accomplish? I mean it is obviously working other
than not being able to ping from my xp machine. My 2000 machine can
ping the XP machine just fine. My NIC's are onboard NICs so though I
could do this I suspect that it would not do much since my 2000 machine
seems to work fine. But I am far from an expert in this and I will try
it if you really think that is a problem. But I have a laptop with XP
home version on it and it has the same problem pinging Windows 2000.

Roger

 

[Marina Roos]

Give your workstations a static IP and tell us how those workstations are
connected.

Marina

 

[Mike]

As for a different
NIC, what exactly would that accomplish? I mean it is obviously
working other than not being able to ping from my xp machine. My 2000
machine can ping the XP machine just fine. My NIC's are onboard NICs
so though I could do this I suspect that it would not do much since my
2000 machine seems to work fine. But I am far from an expert in this
and I will try it if you really think that is a problem. But I have a
laptop with XP home version on it and it has the same problem pinging
Windows 2000.

Roger

Looks like the W2K box is suspect. Your NIC is just a tranceiver. It
transmits and it receives. It can do both at the same time (full
duplex), or one at a time (half duplex).

Changing the NIC was an easier way to isolate if the problem has to to
with duplexing. Find your NIC in Device Manager, select properties, and
if the Line is running at half duplex, change it to full duplex. If its
running at full duplex, change it to half. Sometimes chaning this
feature requires power cycling the NIC (or in your case, the whole
computer).

You never answered question 3.

Are the computers connected together with a crossover or are you using a
hub/switch?

Mike

 

[R.H.]

Oh, forgot about that one. I am using a switch, a DLink DSS-8+. So,
you think it is the Win2K box rather than the XP box? Hmm, I would have
thought the other way around since the Win2K can ping, but the XP can
not. Oh well, I am not exactly an expert so I will look into the Win2K
box then.

Roger

 

[Paul A.]

I have the same problem with a W2000 SP4 machine, but no
solution yet. (My second machine is W95.)

When I do run ZoneAlarm on the W2 machine, ZoneAlarm sees
the ping request. So without ZoneAlarm, W2 is getting the
ping request but does not reply. Not replying might have
been construed as a security feature actually.

One person said there is some feeling that ZoneAlarm may
leave a few hooks in the system even when not running.
However I think this behavior predated the first time when
I used ZoneAlarm.

Of course there is no separate ping "server" program.
Rather the ping handling seems to be integrated at a lower
level of tcp/ip module.

I did search the W2000 registry for "ping", "Tcpip", and
"reply" in case there might be an obvious parameter. And a
few files referenced such as NetTcpIp.inf. Nothing leapt
out at me. Regards. Paul

 

[Brian Oakes [MSFT]]

If you are unable to ping then we are dealing with something at a low level,
in all honesty I would remove zone alarm as a test. Also make sure there is
no TCP/IP Filtering enabled on the W2K box. Make sure there is no firewall
type software on that box as well. Also I am assuming they are in the same
subnet ie not crossing any routers etc.
--

Brian Oakes

This posting is provided "AS IS" with no warranties and confers no rights.
Please reply to the newsgroup so that others may benefit.