Internet Gateway not pass Ping

[Feng]

The company I work or has several agencies and a seat. The gateway that enables users to communicate with headquarters agencies is 193.10.10.195; agencies have routers with IP @ 193.10.11.195 form, 193.10.12.195, 193.10.13.195 and so on. The Internet gateway is 193.10.10.196 (headquarters). I installed Citrix XenApp on a server to optimize bandwidth and antivirus (Bitdefender) to protect against virus attacks. I implemented various configurations on the network card to allow the server at once, can be reached from the agencies and have access to the Internet to update the antivirus. But each time the same problem arises: At certain times of the day, the server can no longer communicate with positions in agencies and vice versa, I found this by running a ping to the router from one of Agencies: I get timeouts, fault it for that I restart the ping password again. And later the same problem arises. Please help me out.

[Big Fish]

It would be much better for us to know, if you provide the settings of your Internet Gateway.!! Also I think that you should be aware of route that can be helpful in such scenarios. The Syntax for it as below :

route [-f] [-p] [Command [Destination] [mask Netmask] [Gateway] [metric Metric]] [if Interface]]

Its Parameters :

• -F : Clears the routing table of all entries are not That host routes (routes with a netmask of 255.255.255.255), the loopback network route (routes with a destination of 127.0.0.0 and a netmask of 255.0.0.0), gold multicast route (routes with a destination of 224.0.0.0 and a netmask of 240.0.0.0). If then this is Used in Conjunction with one of the commands (Such as add, change, delete Gold), the table is cleared Prior to running the command.
• -P : When Used with the add command, the specified route added to the registry IS am and is Used to initialize the IP routing table Whenever the TCP / IP protocol IS started. By default, added routes are not Preserved When the TCP / IP protocol IS started. When Used with the print command, the list of roads still IS displayed. This parameter IS Ignored for All other commands. Persistent routes are Stored in the rental registry HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ Tcpip \ Parameters \ PersistentRoutes.

[Feng]

First extremely thanks for trying to help me. The following are the settings that can be useful for you to help me.
Configuration 1

IP: 193.10.10.170
Mask 255.255.255.0
GW: 193.10.10.195
Then I go into advanced settings:
I change the default gateway setting the metric to 1 and
I add a second gateway: 193.10.10.196 with the metric 2, finally
I Set the interface metric (193.10.10.170) 2

Configuration 2

IP: 193.10.10.170
Mask 255.255.255.0
GW: 193.10.10.195
Then I go into advanced settings:
I change the default gateway by setting the metric to 1 and then
I add a second gateway: 193.10.10.196 with the metric one, finally
I leave the metric of the interface (193.10.10.170) in automatic.

[Shen]

I would say a prior:

0.0.0.0 / 0 gw 193.10.10.196/32
193.10.0.0/16 gw 193.10.10.195/32

Thus to access networks 193.10.xy we pass the bridge (VPN?) 193.10.10.195, and to find the rest of the world, passing through the Internet gateway. That tells a trace route when you lose connectivity?

[Steve123]

Large gains in the metric column of the routing table are the result of Allowing TCP / IP to Automatically determines the metric for routes in the routing table based on the configuration of IP address, subnet mask, and default gateway for EACH LAN interface. Automatic determination of the interface metric, enabled by default, determined the speed of Each interface and adjust the metrics of routes For Each interface so That the fastest interface Create the roads with the Lowest metric. To remove the large metrics, disable the automatic determination of the interface metric from the advanced properties of the TCP / IP protocol For Each LAN connection. Names can Be Used for a year if appropriate Destination entry exists in the local Networks file a Stored in the systemroot \ System32 \ Drivers \ Etc folder. Names can Be Used For The gateway as long as THEY can Be resolved to an IP address-through standard host name resolution techniques have SUCH Domain Name System (DNS) queries, use of the local HOSTS file Stored in the systemroot \ system32 \ drivers \ etc folder, and NetBIOS name Resolution.