J
jurriaanvan.doornik
We're using a local network consisting of 5 Windows 2000 PC's that are
connected through a router to the internet and other sites.
On the network is a specific IP address/resource (non PC, it concerns a
PABX system) that is used by all PC's on the network. If I try pinging
it from any computer in the same network, this works without a problem.
This also works without a problem through the WAN connection (and hence
the router that connects that network to the rest of the world seems to
work properly).
One PC on the network tho does not see the IP address/resource that is
fully pingable through other PC's. A ping returns a request-timed-out.
I've tried pinging the router (a higher address than the PABX) from
that PC, aswell as another PC (a lower IP address than the PABX) in
that same network, and these work without a problem. The resource
however seems to remain as elusive as ever.
Using tracert on both addresses that are pingable does show it to be
able to reach the addresses through a broadcast (one hop), so they are
seen as local to the PC. The address that's unpingable (which is the in
between address) should therefore be reachable much in the same way...
Which it's not for whatever reason.
Logging into servers, and accessing the internet from this one PC works
without any problems whatsoever.
I've flushed the ARP cache, didn't work. Manually entered the ARP entry
for the resource (copied from a PC that does know how to reach the
resource), no go. Flushed DNS, and reregistered the address... Still
nothing. Restarting the PC? Still doesn't see the address. Updates? All
have been installed, and it works fine with any other address, just not
this one.
I've looked at firewall rules that may affect traffic on the
troublesome IP address (the PABX includes a firewall). There are none.
I've looked at IPSec and IP Filtering on the local PC... Both are
completely off. No local firewall software is installed.
The IP address and subnetmasks are granted through DHCP. These are
fine, because I can ping the offending PC from other PC's in the same
network, and reach it through a PC over the WAN connection. Vice versa
connectivity also works fine.
I've looked at the routing table, and compared it with another PC that
does work fine. No differences are shown (other then the local IP
address, but that should be obvious).
All in all, I'm a bit stumped on the cause of this issue, and would
like to ask for further input on what could be tried to resolve the
matter.
Thanks in advance for any and all replies.
connected through a router to the internet and other sites.
On the network is a specific IP address/resource (non PC, it concerns a
PABX system) that is used by all PC's on the network. If I try pinging
it from any computer in the same network, this works without a problem.
This also works without a problem through the WAN connection (and hence
the router that connects that network to the rest of the world seems to
work properly).
One PC on the network tho does not see the IP address/resource that is
fully pingable through other PC's. A ping returns a request-timed-out.
I've tried pinging the router (a higher address than the PABX) from
that PC, aswell as another PC (a lower IP address than the PABX) in
that same network, and these work without a problem. The resource
however seems to remain as elusive as ever.
Using tracert on both addresses that are pingable does show it to be
able to reach the addresses through a broadcast (one hop), so they are
seen as local to the PC. The address that's unpingable (which is the in
between address) should therefore be reachable much in the same way...
Which it's not for whatever reason.
Logging into servers, and accessing the internet from this one PC works
without any problems whatsoever.
I've flushed the ARP cache, didn't work. Manually entered the ARP entry
for the resource (copied from a PC that does know how to reach the
resource), no go. Flushed DNS, and reregistered the address... Still
nothing. Restarting the PC? Still doesn't see the address. Updates? All
have been installed, and it works fine with any other address, just not
this one.
I've looked at firewall rules that may affect traffic on the
troublesome IP address (the PABX includes a firewall). There are none.
I've looked at IPSec and IP Filtering on the local PC... Both are
completely off. No local firewall software is installed.
The IP address and subnetmasks are granted through DHCP. These are
fine, because I can ping the offending PC from other PC's in the same
network, and reach it through a PC over the WAN connection. Vice versa
connectivity also works fine.
I've looked at the routing table, and compared it with another PC that
does work fine. No differences are shown (other then the local IP
address, but that should be obvious).
All in all, I'm a bit stumped on the cause of this issue, and would
like to ask for further input on what could be tried to resolve the
matter.
Thanks in advance for any and all replies.