Application not working when Switch/router as Gateway

[faamin011]

In change network topology, we are going to assign PC's Gateway as Switch (3750X) IP Address rather than server IP Address. Currently we have configured all Sytems's Gateway is Internet Server IP Address which we are going to replace with Switch IP as Gateway.

See the result when I have Server as Gateway

C:\Users\fahadamin>ping www.teamviewer.com

Pinging www.teamviewer.com [46.163.100.220] with 32 bytes of data:
Reply from 46.163.100.220: bytes=32 time=190ms TTL=110
Reply from 46.163.100.220: bytes=32 time=188ms TTL=110

Ping statistics for 46.163.100.220:
    Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 188ms, Maximum = 190ms, Average = 189ms

See when I change Switch/router IP as gateway

C:\Users\fahadamin>ping www.teamviewer.com

Pinging www.teamviewer.com [46.163.100.220] with 32 bytes of data:
Request timed out.
Request timed out.

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

Issue is while connecting specific application like team viewer in which application tried to send keepalive message to the live server and in case of switch/router IP as gateway. Connection doesn't established. However it is working fine when Internet Server IP treated as gateway.

Please advice, no ACL or blockage implemented on Switch

[John Blakley]

How is your switch configured? I'm assuming you have a l3 svi configured on the switch for the hosts to use as the gateway? Do you have routing enabled (ip routing) under the global config?

What is the default route for the switch? Does it point to the router that you're ultimately going to the internet for?

John

[faamin011]

switch Configuration is pasted below, yes svi is configured but all ports are switch ports. Public internet is connected directly to Server,ipconfig is like as

C:>ipconfig

Windows IP Configuration

Ethernet adapter ASDLHR:

   Connection-specific DNS Suffix  . :
   IPv4 Address. . . . . . . . . . . : 10.10.10.61
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . :

Ethernet adapter LDN:

   Connection-specific DNS Suffix  . :
   IPv4 Address. . . . . . . . . . . : 210.2.154.226
   Subnet Mask . . . . . . . . . . . : 255.255.255.248
   Default Gateway . . . . . . . . . : 210.2.154.225

Tunnel adapter Teredo Tunneling Pseudo-Interface:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

*******************************************************************************************

sh run
Switch1#sh running-config
Building configuration...

Current configuration : 4623 bytes
!
!
!
version 12.2
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
service password-encryption
!
hostname Switch1
!
boot-start-marker
boot-end-marker
!
!

!
no aaa new-model
switch 1 provision ws-c3750x-24s
system mtu routing 1500
!
!
!
vtp mode transparent
!
!
crypto pki trustpoint TP-self-signed-767726976
enrollment selfsigned
subject-name cn=IOS-Self-Signed-Certificate-767726976
revocation-check none
rsakeypair TP-self-signed-767726976
!
!
crypto pki certificate chain TP-self-signed-767726976
certificate self-signed 01
3082023D 308201A6 A0030201 02020101 300D0609 2A864886 F70D0101 04050030
30312E30 2C060355 04031325 494F532D 53656C66 2D536967 6E65642D 43657274
69666963 6174652D 37363737 32363937 36301E17 0D393330 33303130 30303132
325A170D 32303031 30313030 30303030 5A303031 2E302C06 03550403 1325494F
532D5365 6C662D53 69676E65 642D4365 72746966 69636174 652D3736 37373236
39373630 819F300D 06092A86 4886F70D 01010105 0003818D 00308189 02818100
B3C34545 83726A91 C837532F 4831246B DB94AD45 48E9DA96 714BA6DD FE088ABE
376DC8F9 194D336D 19694D83 FD2659EC 7BE6EADD B2672907 AB93E1FF 41401CBA
D6B0FAA7 3BDDF6AC DD98493C 925F9E40 BD0B32A8 F8879A39 A7C64E13 5DD8BEBA
46886E13 4A44F55B A711E3A3 23BA7002 A3CF822A 57499CC6 B366B917 05A2242B
02030100 01A36730 65300F06 03551D13 0101FF04 05300301 01FF3012 0603551D
11040B30 09820753 77697463 6832301F 0603551D 23041830 16801420 C124135C
A708F613 E0DE307A 808D04DA F3298030 1D060355 1D0E0416 041420C1 24135CA7
08F613E0 DE307A80 8D04DAF3 2980300D 06092A86 4886F70D 01010405 00038181
00776BA6 84068FFD D0430A8E B639F1A6 85ABCC72 7C02E6B2 BDC8E26A BDB3DB14
47948CB9 91FCEE2F EC3047B5 DA011B4E 2FC9A3BE C4B21A64 76DF3F2E 0A08BA0E
4F3393EE 4E877257 199E9F8F D2B93D4A 20D5EA86 60FE7A11 0199F59C 059AAD39
1E5290C4 6E677CE7 FE175351 4571A39E F548CA19 C6EBAF6B 256D8215 8FA080C6 DB
quit
spanning-tree mode pvst
spanning-tree extend system-id
!
!
!
!
vlan internal allocation policy ascending
!
!
!
!
!
!
!
interface FastEthernet0
no ip address
no ip route-cache cef
no ip route-cache
!
interface GigabitEthernet1/0/1
description ""Uplink To 24Port First Floor C 10.10.10.10"
switchport trunk encapsulation dot1q
switchport mode trunk
!
interface GigabitEthernet1/0/2
description ""Uplink To 24Port First Floor B 10.10.10.9"
switchport trunk encapsulation dot1q
switchport mode trunk
!
interface GigabitEthernet1/0/3
description ""Uplink To 24Port First Floor A 10.10.10.8""
switchport trunk encapsulation dot1q
switchport mode trunk
!
interface GigabitEthernet1/0/4
description ""Uplink To 24Port Basement A 10.10.10.4"
switchport trunk encapsulation dot1q
switchport mode trunk
!
interface GigabitEthernet1/0/5
description ""Uplink To 24Port Basement B 10.10.10.5""
switchport trunk encapsulation dot1q
switchport mode trunk
!
interface GigabitEthernet1/0/6
description ""Uplink To 24Port Basement C 10.10.10.6""
switchport trunk encapsulation dot1q
switchport mode trunk
!
interface GigabitEthernet1/0/7
description ""Uplink To 24Port Fin_NWD_CR 10.10.10.7"
switchport trunk encapsulation dot1q
switchport mode trunk
!
interface GigabitEthernet1/0/8
!
interface GigabitEthernet1/0/9
description description ""Uplink To 24Port Server Farm 10.10.10.3"
switchport trunk encapsulation dot1q
switchport mode trunk
!
interface GigabitEthernet1/0/10
!
interface GigabitEthernet1/0/11
!
interface GigabitEthernet1/0/12
!
interface GigabitEthernet1/0/13
!
interface GigabitEthernet1/0/14
!
interface GigabitEthernet1/0/15
!
interface GigabitEthernet1/0/16
!
interface GigabitEthernet1/0/17
!
interface GigabitEthernet1/0/18
!
interface GigabitEthernet1/0/19
!
interface GigabitEthernet1/0/20
!
interface GigabitEthernet1/0/21
!
interface GigabitEthernet1/0/22
!
interface GigabitEthernet1/0/23
!
interface GigabitEthernet1/0/24
!
interface GigabitEthernet1/1/1
!
interface GigabitEthernet1/1/2
!
interface GigabitEthernet1/1/3
!
interface GigabitEthernet1/1/4
!
interface TenGigabitEthernet1/1/1
!
interface TenGigabitEthernet1/1/2
!
interface Vlan1
ip address 10.10.50.1 255.255.0.0
no ip route-cache cef
no ip route-cache
!
ip default-gateway 10.10.10.61
!
ip http server
ip http secure-server
!
!
logging esm config
logging 10.10.10.103
!
snmp-server community ASD RO
snmp-server host 10.10.10.103 ASD
!
!
line con 0
line vty 0 4

login
length 0
line vty 5 15
login
!
end

[John Blakley]

Try enabling ip routing on the switch. Remove the ip default-gateway line and replace with "ip route 0.0.0.0 0.0.0.0 10.10.10.61"

Hth,
John

Sent from Cisco Technical Support iPhone App

[Rick Morris]

Perhaps I am reading into this a bit too much but the ip 10.10.10.61 showing in the config is the same IP on the workstation in the ipconfig output.  Is this what you want?  What is the next hop device, is it another switch, router, etc...?  What is providing the L3 function?

[faamin011]

Basically it is l3 switch where svi configured, but right now we Are utilizing this switch on layer2 mode no routing at the moment, switch is Acting as distribution layer Where All other switch are connected. In coming days this will perform intervlan routing as we have planned to introduce vlans.

10.10.10.61 is internal ip of Internet server, clients approaching internet via proxy. Now only one Application team viewer is having problem once I put switch svi ip on gateway. But same works when we switch gateway as 10.10.10.61. Remember im talking about clients gateway.

Hope this clarify

[faamin011]

Advice pls

[Rick Morris]

I am still not sure I understand the set-up.

10.10.10.61 is the IP of the proxy?

What is the IP of the default gateway that works?

What is the IP of the default gateway that does not work?

What is the topology of the network, just looking for a basic layout?

Can you post a traceroute of the working connection and a traceroute of the non-working connection?

When you have the config that does not work, are you able to ping the ethernet interface on the switch?

What is the IP of the workstation you are testing from?

[faamin011]

10.10.10.61 is the IP of the proxy? Yes, refer picture as well

What is the IP of the default gateway that works? 10.10.10.61

What is the IP of the default gateway that does not work? 10.10.50.1

What is the topology of the network, just looking for a basic layout? attached

Can you post a traceroute of the working connection and a traceroute of the non-working connection? traceroute to destined what ?

When you have the config that does not work, are you able to ping the ethernet interface on the switch? 10.10.10.61 is bale to ping but 210.2.154.226 is neither able to ping from Switch or my PC.

What is the IP of the workstation you are testing from?10.10.10.103

[Abzal]

Hi,

Have you added ip route to switch 3750?

no ip default-gateway 10.10.10.61

ip route 0.0.0.0 0.0.0.0 10.10.10.61

Try to traceroute teamviewer.com. Try to ping teamviewer.com from proxy server.

Try to ping 210.2.154.226 from PC.

Hope it will help.

[faamin011]

My PC is not able to ping 210.2.154.226. From Proxy Server i can make ping to teamviewer.com.

no ip default-gateway 10.10.10.61 Done

rather than default route I have configured ip route 10.10.10.103 255.255.255.255 10.10.10.61

But after this configuration my system is communicate with all computers in LAN and internet is ok but unable to ping 10.10.50.1 (Switch VLAN 1) also to 210.2.154.226. results are below

C:\Users\fahadamin>tracert teamviewer.com

Tracing route to teamviewer.com [46.163.100.220]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * ^C
C:\Users\fahadamin>ping 10.10.10.61

Pinging 10.10.10.61 with 32 bytes of data:
Reply from 10.10.10.61: bytes=32 time<1ms TTL=128

^C

C:\Users\fahadamin>ping 210.2.154.226

Pinging 210.2.154.226 with 32 bytes of data:
Request timed out.
Request timed out.

C:\Users\fahadamin>ping teamviewer.com

Pinging teamviewer.com [46.163.100.220] with 32 bytes of data:
Request timed out.
Request timed out.

Ping statistics for 46.163.100.220:
Packets: Sent = 2, Received = 0, Lost = 2 (100% loss),
Control-C
^C
C:\Users\fahadamin>nslookup teamviewer.com
Server: autosr12.asdlhr.local
Address: 10.10.10.56

Non-authoritative answer:
Name: teamviewer.com
Address: 46.163.100.220

C:

no ip route 10.10.10.103 255.255.255.255 10.10.10.61

Results are

C:\Users\fahadamin>ping 210.2.154.226

Pinging 210.2.154.226 with 32 bytes of data:
Reply from 10.10.50.1: Destination host unreachable.
Reply from 10.10.50.1: Destination host unreachable.

Ping statistics for 210.2.154.226:
Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Control-C
^C
C:\Users\fahadamin>ping teamviewer.com

Pinging teamviewer.com [46.163.100.220] with 32 bytes of data:
Reply from 10.10.50.1: Destination host unreachable.
Reply from 10.10.50.1: Destination host unreachable.

Ping statistics for 46.163.100.220:
Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Control-C
^C
C:\Users\fahadamin>ping 10.10.50.1

Pinging 10.10.50.1 with 32 bytes of data:
Reply from 10.10.50.1: bytes=32 time=2ms TTL=255

Ping statistics for 10.10.50.1:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 2ms, Average = 2ms
Control-C
^C
C:\Users\fahadamin>

[Raju Sekharan]

Hi Fahad,

All your device are in same subnet. Ideally default gateway should be the device which has route to the outside network which in this case is your server. Your internet connection is conneced to server

If you make 3750 switch as default-gateway, how is it going to route the internet traffic?

Let us be clear about  your design  before we trying to make config changes

Thanks

Raju

[faamin011]

You are right, to communicate different subnets/networks default gateway would be utilzed. But right now we are running 10.10.0.0/16 as whole in LAN network and treating it as VLAN 1. In near future, we plan to advertise VLANs and perform intervlan routing. As far as internet is conncern, this is running via proxy. On every host we have set proxy 10.10.10.61 Port 8080. Likewise specific applications like team viewer see the proxy while making connection to their Public Servers.

Any other clarification required please feel free to ask me, also would like to inform you that we are in transition phase to implement intervlan routing. In which the first step to assign 10.10.50.1 as gateway to all computers, previously it used to be 10.10.10.61 as gateway of all systems. Cisco 3750x (10.10.50.1) is newly installed switch.

In this step all my LAN applications work well also internet browsing going fine, only I have been facing issue in Teamviewer and MSN messenger.

Skyp is also running fine. Please help 

[Raju Sekharan]

Hi Fahad,

Are you going to subnet the current 10.10.0.0/16 in to smaller subnets?

Is the server continue to be the one which has connecion to internet?

Thank you

Raju

[faamin011]

Are you going to subnet the current 10.10.0.0/16 in to smaller subnets?

We will chanage the 2nd octet like 10.11.0.0/16, 10.12.0.0/16 and so on, as in presence of whole /16 subnet we cann't split 10.10.0.0/16 into smaller subnets otherwise conflict with Vlan 1 will occur. We have to see the production environment as well.

Is the server continue to be the one which has connecion to internet? Yes, basically we have planeed to move internet connection to Layer 3 and advertise New VLAN subnet on L3 which will be treated as Externel network of Internet Server, also the proxy on cleints. But it is future plan, at the moment I have to focus on Step 1 by changing the gateways to all system.

I can only be move forward to intervlan routing once this done, all things seems ok but the barrier is to run Teamviewer and MSN via new gateway.

Hope this clarify