Can't get there from here

christopher_hall · ‎06-12-2013

I had previously posted about an issue with accessing an interface on our Exchange server. The discussion was posted here: https://supportforums.cisco.com/message/3954951#3954951

I'm still having the issue. From my workstation, I cannot reach this interface. Here's an overview:

My PC: 10.20.104.50

Switch/Data vlan: 10.20.104.1

Exchange DAG: 10.20.100.100

I can trace/ping to my switch from my workstation.

From the switch, I can ping/trace to the Exchange DAG.

I can Not reach the Exchange DAG.

Here are results from the trace from my workstation:

C:\>tracert 10.20.100.100

Tracing route to rep00mail01.secfedbank.com [10.20.100.100]

over a maximum of 30 hops:

1 1 ms 2 ms 1 ms 10.20.104.1

2 * * * Request timed out.

3 * * * Request timed out.

4 * * * Request timed out.

5 * * * Request timed out.

6 * * ^C

C:\>

Results from the trace from switch:

sw00-3560-01#traceroute 10.20.100.100

Type escape sequence to abort.

Tracing the route to 10.20.100.100

1 10.20.100.100 210 msec 0 msec 0 msec

sw00-3560-01#

Thanks for any thoughts.

mfurnival · ‎06-12-2013

I love that topic title!

Can you post the switch config and also include ipconfig from the desktop and Exchange server?

christopher_hall · ‎06-12-2013

Title caught your eye, huh? I have the workstation and exchange info listed below. The switch config is attached. Thanks for the quick reply!

Workstation:

C:\>ipconfig

Windows IP Configuration

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : secfedbank.com

Link-local IPv6 Address . . . . . : fe80::a401:16ea:4035:a086%13

IPv4 Address. . . . . . . . . . . : 10.20.104.50

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 10.20.104.1

Exchange:

Microsoft Windows [Version 6.1.7601]

U:\>ipconfig

Windows IP Configuration

Ethernet adapter Local Area Connection* 9:

Connection-specific DNS Suffix . :

Link-local IPv6 Address . . . . . : fe80::2164:455e:c6d0:f084%15

IPv4 Address. . . . . . . . . . . : 169.254.1.246

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

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

Ethernet adapter MAPI:

Connection-specific DNS Suffix . :

IPv4 Address. . . . . . . . . . . : 10.20.102.33

Subnet Mask . . . . . . . . . . . : 255.255.255.0

IPv4 Address. . . . . . . . . . . : 10.20.102.35

Subnet Mask . . . . . . . . . . . : 255.255.255.0

IPv4 Address. . . . . . . . . . . : 10.20.102.142

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 10.20.102.1

Ethernet adapter Replication:

Connection-specific DNS Suffix . :

IPv4 Address. . . . . . . . . . . : 10.20.100.100

Subnet Mask . . . . . . . . . . . : 255.255.255.0

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

Tunnel adapter isatap.{7EE66D73-90D5-4645-90AD-DA147AD643AF}:

Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . :

Tunnel adapter isatap.{AEB97A35-C661-47AA-A128-EA50E841B9BB}:

Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . :

Tunnel adapter isatap.{61CD3CE1-D6B8-4276-87DA-3B6500A1A83B}:

Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . :

mfurnival · ‎06-12-2013

The address you are pinging - 10.20.100.10. On the server there is no default gateway for this interface. So the switch can ping it because it has an interface in that subnet (VLAN4). I am guessing that if you ping the address from the switch and specify VLAN104 (10.20.104.1) as the source interface it won't work.

christopher_hall · ‎06-12-2013

Looking at the switch config and the exchange config, if I were to set the gateway on the exchange to 10.20.100.1, it should work, huh?

mfurnival · ‎06-12-2013

You could do that - though not sure of your overall topology of whether that is something desirable or not...

You could just add a static route on the server:

route add 10.20.104.0 netmask 255.255.255.0 10.20.100.1 -p

christopher_hall · ‎06-12-2013

I talked to our exchange guy and there's a reason that the gateway isn't assigned. I was thinking I could add a route on the switch..

ip route 10.20.100.100 255.255.255.255 10.20.100.1

But of course, that is ON the switch.

Added the static route you mentioned above and that did the trick!

Thanks!

Chris

mfurnival · ‎06-12-2013

Excellent - now you can get from here to there and back again

christopher_hall · ‎06-12-2013

That's right! And if I ever get lost going from here to there and back, I'll just trace my way back to here and my friendly form folks!