Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

unable to test communication between client and server via ping

Status
Not open for further replies.

obal85

Technical User
Apr 18, 2011
10
GB
Hi Guys,
I have 3 client computers named xpprouser, olubalogun and yomiajayi and one server2003 named london but i have tried but to no avail to ping each of the clients and server.

Let me reveal the tcp/ip settings of my clients (named xpprouser, olubalogun and yomiajayi) and server2003 (named london).

server2003 (named london)
====================
use the following ip address (selected)
ip address: 192.168.0.1
subnet mask: 255-255-255-0
default gateway:
use the following dns server addresses (selected)
preferred dns server: 127.0.0.1
alternate dns server:

client1 (named xpprouser)
====================
obtain an ip address automatically (selected)
ip address:
subnet mask:
default gateway:
use the following dns server addresses (selected)
preferred dns server: 192.168.0.1
alternate dns server:


client2 (named olubalogun)
====================
obtain an ip address automatically (selected)
ip address:
subnet mask:
default gateway:
use the following dns server addresses (selected)
preferred dns server: 192.168.0.1
alternate dns server:

client3 (named yomiajayi)
====================
obtain an ip address automatically (selected)
ip address:
subnet mask:
default gateway:
obtain dns server address automatically (selected)
preferred dns server:
alternate dns server:


Guys, these are my tcp/ip settings for the server2003 and 3 clients. Could you make right changes to these settings for me please. I will really appreciate it. I look forward to hearing from you guys a.s.a.p.
 
firewalls are likely enabled on on either the clients or the server, or both. Those will block ping requests unless you create exceptions for that. Plenty of Google results on how to to that.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.
 
Is DHCP running on the server?
Do the clients actually acquire an address in the 192.168.0.x range?
If you give one of the clients a static address in that range, can you ping the server?
Hint: use IPCONFIG on the client to verify it's IP adress
 
Hi JKnichols,
Thanks a lot for replying to my post. There is no DHCP running. My server200 is configured to obtain ip address manually. Yes both clients and server2003 ip addresses are in the range 192.168.0.x range. I can ping server2003 successfully from both xp pro clients but unable to ping successfully xp pro clients from server2003.

xp pro client 1 tcp/ip properties
---------------------------------
use the following ip address (selected)
ip address: 192.168.0.2
subnet mask: 255.255.255.0
default gateway:
use the following dns server addresses(selected)
preferred dns server: 192.168.0.1
alternate dns server:
================================
xp pro client 2 tcp/ip properties
---------------------------------
use the following ip address (selected)
ip address: 192.168.0.3
subnet mask: 255.255.255.0
default gateway:
use the following dns server addresses(selected)
preferred dns server: 192.168.0.1
alternate dns server:
===================================
server2003 tcp/ip properties
---------------------------------
use the following ip address (selected)
ip address: 192.168.0.1
subnet mask: 255.255.255.0
default gateway:
use the following dns server addresses(selected)
preferred dns server: 127.0.0.1
alternate dns server:
====================================

Also i have not been able to ping both xp pro clients successfully.

I look forward to hearing from you soonest.

 
@58 sniper,
Thanks a lot for your assistance. I have disabled firewalls on both clients and server respectively and still get connection issues.
 
First, you should configure the DNS on the server to use 192.168.0.1, not the loopback (127.0.0.1). But that's not the problem here.

When you're attempting to ping, are you using the IP addresses or the machine names?

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.
 
Hi Sniper,
I ping using computername. Sometimes i use ip address. I have tried to configure the DNS on the server to use 192.168.0.1, but unfortunately the issue still persist. I dont know what else to do man.
 
Those should come back with zero hops since they're all on the same subnet.

Try only pinging via IP address. Back to the basics.

Make sure the firewalls are turned off in Windows for public, work, and domain profiles.

Verify each machine can ping its own IP address.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.
 
@58sniper,
XP1 could successfully ping server2003 as shown below:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\administrator>ping 192.168.0.1

Pinging 192.168.0.1 with 32 bytes of data:

Reply from 192.168.0.1: bytes=32 time=3ms TTL=128
Reply from 192.168.0.1: bytes=32 time<1ms TTL=128
Reply from 192.168.0.1: bytes=32 time<1ms TTL=128
Reply from 192.168.0.1: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 3ms, Average = 0ms

C:\Documents and Settings\administrator>


But server2003 could not successfully ping the ip address of XP1 as shown below:

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator>ping 192.168.0.2

Pinging 192.168.0.2 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.0.2:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Documents and Settings\Administrator>

=================================

I have turned off the firewalls in both clients (namely - xp1 and xp2) and server2003 (named London).

================================

results of client xp1 pinging its own ip address:
--------------------------------------------
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\administrator>ping 192.168.0.2

Pinging 192.168.0.2 with 32 bytes of data:

Reply from 192.168.0.2: bytes=32 time<1ms TTL=128
Reply from 192.168.0.2: bytes=32 time<1ms TTL=128
Reply from 192.168.0.2: bytes=32 time<1ms TTL=128
Reply from 192.168.0.2: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.0.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\administrator>

================================

results of server2003 pinging its own ip address:
--------------------------------------------
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator>ping 192.168.0.1

Pinging 192.168.0.1 with 32 bytes of data:

Reply from 192.168.0.1: bytes=32 time<1ms TTL=128
Reply from 192.168.0.1: bytes=32 time<1ms TTL=128
Reply from 192.168.0.1: bytes=32 time<1ms TTL=128
Reply from 192.168.0.1: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\Administrator>

I need to notify you guys that clients xp pro and server2003 are installed in vmware workstation (that is virtual environment)to carry out this. I just thought u should know.









 
Does each machine only have a single network card? If not, disable all of the others so only one is enabled.

Any antivirus software?

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.
 
@technome

this is the result of xp1 pathping command to server2003:
========================================================

C:\Documents and Settings\administrator>pathping 192.168.0.1

Tracing route to 192.168.0.1 over a maximum of 30 hops

0 olubalogun.nwtraders.com [192.168.0.2]
1 192.168.0.1

Computing statistics for 25 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 olubalogun.nwtraders.com [192.168.
0.2]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1

Trace complete.

C:\Documents and Settings\administrator>

--------------------------------------

this is the result of server2003 pathping command to xp1:
========================================================



C:\Documents and Settings\Administrator>pathping 192.168.0.2

Tracing route to 192.168.0.2 over a maximum of 30 hops

0 london.nwtraders.com [192.168.0.1]
1 * * *
Computing statistics for 25 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 london.nwtraders.com [192.168.0.1]

100/ 100 =100% |
1 --- 100/ 100 =100% 0/ 100 = 0% london.nwtraders.com [0.0.0.0]

Trace complete.

C:\Documents and Settings\Administrator>

------------------------------------------------

tracertcommand from server2003 to xp1
--------------------------------------

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator>tracert 192.168.0.2

Tracing route to 192.168.0.2 over a maximum of 30 hops

1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.


------------------------------------------------

tracertcommand from xp1 to server2003
--------------------------------------

C:\Documents and Settings\administrator>tracert 192.168.0.1

Tracing route to 192.168.0.1 over a maximum of 30 hops

1 3 ms <1 ms <1 ms 192.168.0.1

Trace complete.

C:\Documents and Settings\administrator>

















 
@58 sniper

Network card? I need to be honest with you guys. I started this mcdst windows certification course just less than 2 months hence i have no idea what a network cards is and where to find and how to disable it. Could you tell me how to do these things? I have got kaspersky internet security 2011 installed on my physical computer.
 
@58sniper & technome
Thanks a lot for your assistance. I have re-installed both clients and server2003 and been able to do it successfully.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top