Pinging Problem

  • Thread starter Thread starter Inderjeet
  • Start date Start date
I

Inderjeet

I have windows 2000 professional computers and also have
windows 95/98/XP computers in my network. Onle computer
which is acting as a node for some applications is workin
fine and i can access it from any other computers from
network but, the only thing i cannot do is i cannot PING
the computer from any other computer in network.

Rest everything is working fine and i have checked for the
IPSEC policy and that is Disabled on the system under
Local security policy.

What can i do.....Please any suggestions.

Thank You
 
Inderjeet said:
I have windows 2000 professional computers and also have
windows 95/98/XP computers in my network. Onle computer
which is acting as a node for some applications is workin
fine and i can access it from any other computers from
network but, the only thing i cannot do is i cannot PING
the computer from any other computer in network.

Rest everything is working fine and i have checked for the
IPSEC policy and that is Disabled on the system under
Local security policy.

What can i do.....Please any suggestions.

Thank You
Click to expand...

Turn off your internal firewalls while testing, especially those
that are bundled with your virus scanner.
 
-----Original Message-----



Turn off your internal firewalls while testing, especially those
that are bundled with your virus scanner.


.
Click to expand...

But i donot have any Firewall enabled anywhere. I am using
Symantec client and every computer is using the same
client with same configuration
 
But i donot have any Firewall enabled anywhere. I am using
Symantec client and every computer is using the same
client with same configuration
Click to expand...

- Start a DOS prompt on the problem PC (or a Command Prompt
if it is a Win2000 PC).
- Type this command: ipconfig /all > c:\ip.txt
- Do the same thing on one of the other machines.
- Post the contents of both files in your next reply.
 
This is the ip.txt for the computer which is not being
pinged



Windows 2000 IP Configuration



Host Name . . . . . . . . . . . . : jetairt
Primary DNS Suffix . . . . . . . : jetair.co.in
Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : Yes

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : jetair.co.in

Ethernet adapter Local Area Connection 4:



Connection-specific DNS Suffix . : jetair.co.in
Description . . . . . . . . . . . : D-Link DFE-
538TX 10/100 Adapter #4
Physical Address. . . . . . . . . : 00-50-BA-47-2C-
EA

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 10.12.1.9

Subnet Mask . . . . . . . . . . . : 255.255.0.0

Default Gateway . . . . . . . . . : 10.12.0.1

DHCP Server . . . . . . . . . . . : 10.12.0.10

DNS Servers . . . . . . . . . . . : 10.12.0.10
10.1.0.10
Primary WINS Server . . . . . . . : 10.12.0.10

Secondary WINS Server . . . . . . : 10.1.0.10

Lease Obtained. . . . . . . . . . : Friday, July
30, 2004 5:11:47 PM

Lease Expires . . . . . . . . . . : Saturday,
August 07, 2004 5:11:47 PM




this is the ip.txt of the computer from where i was
pinging the above computer

Windows 98 IP Configuration



Host Name . . . . . . . . . : AMITC.jetair.co.in

DNS Servers . . . . . . . . : 10.12.0.10

10.1.0.10

Node Type . . . . . . . . . : Hybrid

NetBIOS Scope ID. . . . . . :

IP Routing Enabled. . . . . : No

WINS Proxy Enabled. . . . . : No

NetBIOS Resolution Uses DNS : No



0 Ethernet adapter :



Description . . . . . . . . : PPP Adapter.

Physical Address. . . . . . : 44-45-53-54-00-00

DHCP Enabled. . . . . . . . : Yes

IP Address. . . . . . . . . : 0.0.0.0

Subnet Mask . . . . . . . . : 0.0.0.0

Default Gateway . . . . . . :

DHCP Server . . . . . . . . : 255.255.255.255

Primary WINS Server . . . . :

Secondary WINS Server . . . :

Lease Obtained. . . . . . . :

Lease Expires . . . . . . . :



1 Ethernet adapter :



Description . . . . . . . . : Realtek 8139-series
PCI
NIC

Physical Address. . . . . . : 10-E0-8D-10-49-4C

DHCP Enabled. . . . . . . . : Yes

IP Address. . . . . . . . . : 10.12.1.43

Subnet Mask . . . . . . . . : 255.255.0.0

Default Gateway . . . . . . : 10.12.0.1

DHCP Server . . . . . . . . : 10.12.0.10

Primary WINS Server . . . . : 10.12.0.10

Secondary WINS Server . . . : 10.1.0.10

Lease Obtained. . . . . . . : 08 02 04 9:46:41 AM

Lease Expires . . . . . . . : 08 10 04 9:46:41 AM
 
In your reply you first say:
This is the ip.txt for the computer which is not being pinged and then you say:
this is the ip.txt of the computer from where i was pinging the above
Click to expand...
computer

There is an inherent contradiction in what you write. I will now
assume that you meant to say:
This is the ip.txt for the computer which is being pinged and
this is the ip.txt of the computer from where i was pinging the above
Click to expand...
computer

I will also give the PCs names. I will call the Win2000 PC the "pingee",
and the Win98 machine the "pinger".

- The pinger's IP address is 10.12.1.43.
- The pingee's IP address is 10.12.1.9.

The addresses are OK. I would now do this:
- Remove one of the two network adapters from the pinger.
You need to keep things simple while testing.
- Force both adapters to run at 10 MBits/s half duplex.
- Make the network icon visible for the pingee, and watch
the byte counter when pinging.
- Install Ethereal on both machines, and watch what happens to
to packets.

I know that you say that you do not have a firewall. On the other
hand I also know that in similar posts I read in the past, there was
almost always a firewall involved, unknown to the poster. If there
is a faint possibility of there being some firewall function embedded
in your Symantec software then you might save yourself a great
deal of time if you dealt with this issue first, until you were absolutely
sure that it does not play a part. Do not rely on the fact that other
machines work: Dig as deep as you can!
 
Back
Top