Home / server / Questions / 616375
In Process
CIA
Asked: 2014-07-30 09:25:00 +0800 CST

Why am I unable to tracert to an IP on my desktop, but I can on my server?

  • 772
Desktop IP: 10.65.115.145
Server IP:  10.65.107.100
Local Core Switch: 10.65.0.1
Remote Core Switch: 10.64.0.1
Remote Server vLAN (sits in core switch): 10.64.30.1
Remote Server: 10.64.30.10
  • I can ping and tracert from my local core switch to the remote server and remote server vlan.
  • I cannot ping or tracert from my desktop to the remote server or remote server vlan.
  • I can ping from my desktop to the remote core switch.
  • I can ping and tracert from my server to the remote core switch and remote server.
  • A tracert from my desktop to the remote server shows the hop dies at the remote core switch.
  • A tracert from my server to the remote server shows it routes properly.
  • A tracert from my local core switch to the remote server shows it routes properly.

I tested this from another system on the same vlan as my desktop and found I am unable to ping or tracert from the desktop's vlan; this is weird, since I can tracert all the way up to the remote core switch.

Does this mean the issue is on the remote end? or is this an issue on the local end?

static-routes

0 Answers