On our company network no one can ping my computer, by name or by ip address.
I can access other network resources and my computer works perfectly normally but other people can't access my computer.
I've turned off the ICF in network connections.
I am not running any firewall software.
As far as I know the machine should be open for other's to connect to, but they can't even get a response to a ping.
>On our company network no one can ping my computer, by name or by ip address.
>
>I can access other network resources and my computer works perfectly normally but other people can't access my computer.
>
>I've turned off the ICF in network connections.
>I am not running any firewall software.
>As far as I know the machine should be open for other's to connect to, but they can't even get a response to a ping.
>
>Any ideas?
>
>Thanks,
>Brian
Brian,
Let's start by examining your computer, and one other computer.
Please provide ipconfig information for each computer.
Start - Run - "cmd". Type "ipconfig /all >c:\ipconfig.txt" into the command
window - Open c:\ipconfig.txt in Notepad, copy and paste into your next post.
From each computer, verify connectivity:
1) Ping the other by name.
2) Ping the other by ip address.
3) Ping itself by name.
4) Ping itself by ip address.
5) Ping 127.0.0.1.
Report success / failure of each of 10 pings.
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
>On our company network no one can ping my computer, by name or by ip address.
>>I can access other network resources and my computer works perfectly normally but other people can't access my computer.
>>I've turned off the ICF in network connections.
>I am not running any firewall software.
>As far as I know the machine should be open for other's to connect to, but they can't even get a response to a ping.
>>Any ideas?
>>Thanks,
>Brian
Brian,
Let's start by examining your computer, and one other computer.
Please provide ipconfig information for each computer.
Start - Run - "cmd". Type "ipconfig /all >c:\ipconfig.txt" into the command
window - Open c:\ipconfig.txt in Notepad, copy and paste into your next post.
From each computer, verify connectivity:
1) Ping the other by name.
2) Ping the other by ip address.
3) Ping itself by name.
4) Ping itself by ip address.
5) Ping 127.0.0.1.
Report success / failure of each of 10 pings.
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
Ping statistics for 192.168.21.173:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Pinging koncan [192.168.55.223] with 32 bytes of data:
Reply from 192.168.55.223: bytes=32 time<1ms TTL=128
Reply from 192.168.55.223: bytes=32 time<1ms TTL=128
Reply from 192.168.55.223: bytes=32 time<1ms TTL=128
Reply from 192.168.55.223: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.55.223:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Pinging 192.168.55.223 with 32 bytes of data:
Reply from 192.168.55.223: bytes=32 time<1ms TTL=128
Reply from 192.168.55.223: bytes=32 time<1ms TTL=128
Reply from 192.168.55.223: bytes=32 time<1ms TTL=128
Reply from 192.168.55.223: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.55.223:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Ping statistics for 127.0.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Bluetooth LAN Access Server Driver
Physical Address. . . . . . . . . : 00-10-C6-1F-1B-A8
Pinging koncan.chicago.solcorp.com [192.168.55.223] with 32 bytes of data:
Reply from 192.168.55.223: bytes=32 time=43ms TTL=125
Reply from 192.168.55.223: bytes=32 time=23ms TTL=125
Reply from 192.168.55.223: bytes=32 time=32ms TTL=125
Reply from 192.168.55.223: bytes=32 time=44ms TTL=125
Ping statistics for 192.168.55.223:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 44ms, Average = 35ms
Pinging 192.168.55.223 with 32 bytes of data:
Reply from 192.168.55.223: bytes=32 time=23ms TTL=125
Reply from 192.168.55.223: bytes=32 time=23ms TTL=125
Reply from 192.168.55.223: bytes=32 time=23ms TTL=125
Reply from 192.168.55.223: bytes=32 time=23ms TTL=125
Ping statistics for 192.168.55.223:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 23ms, Average = 23ms
Pinging bkearney [192.168.21.173] with 32 bytes of data:
Reply from 192.168.21.173: bytes=32 time<1ms TTL=128
Reply from 192.168.21.173: bytes=32 time<1ms TTL=128
Reply from 192.168.21.173: bytes=32 time<1ms TTL=128
Reply from 192.168.21.173: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.21.173:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Pinging 192.168.21.173 with 32 bytes of data:
Reply from 192.168.21.173: bytes=32 time<1ms TTL=128
Reply from 192.168.21.173: bytes=32 time<1ms TTL=128
Reply from 192.168.21.173: bytes=32 time<1ms TTL=128
Reply from 192.168.21.173: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.21.173:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Ping statistics for 127.0.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Well, to start, your computer has ip address 192.168.21.173/24. The other
computer has 192.168.55.223/24. Are you connecting your computer to the same
physical network as the other computer, or is this a routing issue? Both the
subnet that your computer is on, and the other computer, are apparently part of
your company private network.
Is there another computer on 192.168.21/24 that you can test with, as the
"other" computer?
This may be an issue which you have to take up with the IT group at your
company, as it depends upon how your company private network is setup.
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
Well, to start, your computer has ip address 192.168.21.173/24. The other
computer has 192.168.55.223/24. Are you connecting your computer to the same
physical network as the other computer, or is this a routing issue? Both the
subnet that your computer is on, and the other computer, are apparently part of
your company private network.
Is there another computer on 192.168.21/24 that you can test with, as the
"other" computer?
This may be an issue which you have to take up with the IT group at your
company, as it depends upon how your company private network is setup.
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
I've repeated the test with a computer on the same subnet. Sorry, I should have used a local computer the first time.
Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Bluetooth LAN Access Server Driver
Physical Address. . . . . . . . . : 00-10-C6-1F-1B-A8
Pinging popeye.chicago.solcorp.com [192.168.21.108] with 32 bytes of data:
Reply from 192.168.21.108: bytes=32 time<1ms TTL=128
Reply from 192.168.21.108: bytes=32 time<1ms TTL=128
Reply from 192.168.21.108: bytes=32 time<1ms TTL=128
Reply from 192.168.21.108: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.21.108:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Pinging 192.168.21.108 with 32 bytes of data:
Reply from 192.168.21.108: bytes=32 time<1ms TTL=128
Reply from 192.168.21.108: bytes=32 time<1ms TTL=128
Reply from 192.168.21.108: bytes=32 time<1ms TTL=128
Reply from 192.168.21.108: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.21.108:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Pinging bkearney [192.168.21.173] with 32 bytes of data:
Reply from 192.168.21.173: bytes=32 time<1ms TTL=128
Reply from 192.168.21.173: bytes=32 time<1ms TTL=128
Reply from 192.168.21.173: bytes=32 time<1ms TTL=128
Reply from 192.168.21.173: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.21.173:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Pinging 192.168.21.173 with 32 bytes of data:
Reply from 192.168.21.173: bytes=32 time<1ms TTL=128
Reply from 192.168.21.173: bytes=32 time<1ms TTL=128
Reply from 192.168.21.173: bytes=32 time<1ms TTL=128
Reply from 192.168.21.173: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.21.173:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Ping statistics for 127.0.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
----> From other computer
Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.
Ping statistics for 192.168.21.173:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Ping statistics for 192.168.21.173:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
F:\>ping popeye
Pinging popeye [192.168.21.108] with 32 bytes of data:
Reply from 192.168.21.108: bytes=32 time<10ms TTL=128
Reply from 192.168.21.108: bytes=32 time<10ms TTL=128
Reply from 192.168.21.108: bytes=32 time<10ms TTL=128
Reply from 192.168.21.108: bytes=32 time<10ms TTL=128
Ping statistics for 192.168.21.108:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
F:\>ping 192.168.21.108
Pinging 192.168.21.108 with 32 bytes of data:
Reply from 192.168.21.108: bytes=32 time<10ms TTL=128
Reply from 192.168.21.108: bytes=32 time<10ms TTL=128
Reply from 192.168.21.108: bytes=32 time<10ms TTL=128
Reply from 192.168.21.108: bytes=32 time<10ms TTL=128
Ping statistics for 192.168.21.108:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
F:\>ping 127.0.0.1
Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
Ping statistics for 127.0.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
>
>
> ----- Chuck wrote: -----
>
> On Wed, 28 Apr 2004 13:36:04 -0700, "Brian Kearney"
> <anonymous@discussions.microsoft.com> wrote:
>
> <SNIP very detailed diagnostic data>
>
> Brian,
>
> Well, to start, your computer has ip address 192.168.21.173/24. The other
> computer has 192.168.55.223/24. Are you connecting your computer to the same
> physical network as the other computer, or is this a routing issue? Both the
> subnet that your computer is on, and the other computer, are apparently part of
> your company private network.
>
> Is there another computer on 192.168.21/24 that you can test with, as the
> "other" computer?
>
> This may be an issue which you have to take up with the IT group at your
> company, as it depends upon how your company private network is setup.
>
> Cheers,
> Chuck
> Paranoia comes from experience - and is not necessarily a bad thing.
>
>I've repeated the test with a computer on the same subnet. Sorry, I should have used a local computer the first time.
>
>Here are the results from the new test.
<SNIP detail diagnostic data>
Brian,
Well, this is a challenge.
You have now showed me two computers on the same subnet. Both are apparently
connecting to the subnet - and names resolving properly (from popeye, bkearney
is resolving to its ip address correctly).
There is no connectivity problem - bkearney pings outward - pings popeye fine.
Yet popeye can't ping bkearney. Though popeye can ping itself fine. So no
apparent problem with popeye.
The only explanation for this is a firewall on bkearney. "I am not running any
firewall software." Did you EVER install firewall software on bkearney?
I am kind of curious about the Bluetooth Ethernet adapter on bkearney. Maybe
the static route table will give us a clue.
Please provide static route tables for bkearney and popeye.
Start - Run - "cmd". Type "route print >c:\route.txt" into the command window -
Open c:\route.txt in Notepad, copy and paste into your next post.
Other observances, which may be relevant, maybe your IT folks can explain.
You have 2 DHCP/DNS/WINS servers on your subnet: 192.168.21.2 and 192.168.21.7,
with reversed roles (probably load balancing design). How many different
computers have you tested with this problem pinging bkearney? Did they all get
DHCP from 192.168.21.2 (as popeye did)? Can you run the same test on one that
got DHCP from 192.168.21.7 (as bkearney did)?
Your computer bkearney is WinXP. Is koncan WinXP also? I see that popeye is
Win2K. Do you have other WinXP on your subnet?
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
>>> ----- Chuck wrote: -----
>> On Wed, 28 Apr 2004 13:36:04 -0700, "Brian Kearney"
><anonymous@discussions.microsoft.com> wrote:
>><SNIP very detailed diagnostic data>>> Brian,
>> Well, to start, your computer has ip address 192.168.21.173/24. The other
> computer has 192.168.55.223/24. Are you connecting your computer to the same
> physical network as the other computer, or is this a routing issue? Both the
> subnet that your computer is on, and the other computer, are apparently part of
> your company private network.
>> Is there another computer on 192.168.21/24 that you can test with, as the
> "other" computer?
>> This may be an issue which you have to take up with the IT group at your
> company, as it depends upon how your company private network is setup.
>> Cheers,
> Chuck
> Paranoia comes from experience - and is not necessarily a bad thing.
>>I've repeated the test with a computer on the same subnet. Sorry, I should have used a local computer the first time.
>>Here are the results from the new test.
<SNIP detail diagnostic data>
Brian,
Well, this is a challenge.
You have now showed me two computers on the same subnet. Both are apparently
connecting to the subnet - and names resolving properly (from popeye, bkearney
is resolving to its ip address correctly).
There is no connectivity problem - bkearney pings outward - pings popeye fine.
Yet popeye can't ping bkearney. Though popeye can ping itself fine. So no
apparent problem with popeye.
The only explanation for this is a firewall on bkearney. "I am not running any
firewall software." Did you EVER install firewall software on bkearney?
I am kind of curious about the Bluetooth Ethernet adapter on bkearney. Maybe
the static route table will give us a clue.
Please provide static route tables for bkearney and popeye.
Start - Run - "cmd". Type "route print >c:\route.txt" into the command window -
Open c:\route.txt in Notepad, copy and paste into your next post.
Other observances, which may be relevant, maybe your IT folks can explain.
You have 2 DHCP/DNS/WINS servers on your subnet: 192.168.21.2 and 192.168.21.7,
with reversed roles (probably load balancing design). How many different
computers have you tested with this problem pinging bkearney? Did they all get
DHCP from 192.168.21.2 (as popeye did)? Can you run the same test on one that
got DHCP from 192.168.21.7 (as bkearney did)?
Your computer bkearney is WinXP. Is koncan WinXP also? I see that popeye is
Win2K. Do you have other WinXP on your subnet?
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
Thanks for your help. We seem to have identified the problem. The primary cause is that my computer has our new VPN software on it (which has builtin firewall support) but the interoffice VPN and most users have not switched over yet.
Given the changes we made yesterday it works completely or partially. When I'm inside the office I need to stop the VPN service and then everything works. When I'm outside the office then only people on my subnet can see my machine because of a routing problem between the interoffice VPN and the new VPN. This will go away once everyone has moved to the new VPN (our security policy on the new VPN restricts who my computer will respond to, and it seems to only respond to those who are also running the same VPN? I dunno, some times I can't understand what tech. services is saying).
On Tue, 4 May 2004 10:11:03 -0700, "Brian Kearney"
<anonymous@discussions.microsoft.com> wrote:
<SNIP>
>Thanks for your help. We seem to have identified the problem. The primary cause is that my computer has our new VPN software on it (which has builtin firewall support) but the interoffice VPN and most users have not switched over yet.
>
>Given the changes we made yesterday it works completely or partially. When I'm inside the office I need to stop the VPN service and then everything works. When I'm outside the office then only people on my subnet can see my machine because of a routing problem between the interoffice VPN and the new VPN. This will go away once everyone has moved to the new VPN (our security policy on the new VPN restricts who my computer will respond to, and it seems to only respond to those who are also running the same VPN? I dunno, some times I can't understand what tech. services is saying).
>
>Thanks again.
>Brian
Brian,
Thanks for the update. Glad you figured it out.
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
No Response to PING of XP Pro Computer 
Linear Mode
