Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Friday, July 21, 2017 7:59 PM
After rebooting our corporate computers (Windows 10 Pro) some of the static routes are lost.
Of course they are defined as persistent and if you list them with "route print" they are there, however at least one of them stops working.
This happens in different computers and with different routes so is not computer related nor route related.
The only solution we found so far is to delete the failing route and create it again.
Did you experience a similar problem? Could you give us a clue about what may be happening?
Thanks in advance.
All replies (14)
Friday, July 28, 2017 6:33 AM ✅Answered | 1 vote
Hi Daniel,
First of all, please give us English output for better analysis.
For current situation, please help us confirm these information:
1. Check whether the persist route is correctly bind to the interface.
a. Open command prompt(Admin), type netsh interface ipv4 show route . Please provide us results.
Before routes work correctly, it will check the interface status (up or down), interface index information and so on. After that, the persist route will show in the active routing table.
For example:
Idx is the interface ID. You can get the interface ID from the output of command “route print”
2. How you add persistent routes
To keep the “active” route, it is better to use command “route -p add 192.168.50.0 mask 255.255.255.0 192.168.1.170 if <interface_ID>” to add a persistent route. So you can bind route to the specific interface. (Remember to delete the old route before adding a new one.) Then check whether the persist routes still work after workstation reboot.
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Monday, July 24, 2017 6:21 AM
Hi Daniel,
Please check if the relevant static route records are in the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip \Parameters\PersistentRoutes
And please make sure there is no gateway configured on the Internal NIC as the following steps:
1. Open network and sharing center.
2. Click Change Adapter Settings.
3. Right click on the interface -> Properties
4. Click "Internet Protocol Version 4" -> Click Properties
5. Click "Advanced..."
6. Click on the entry under "Default gateways" and click "Remove" for each.
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Monday, July 24, 2017 12:53 PM
Hi Karen:
Thanks for your answer.
The static routes are correctly defined in the registry key.
All our machines have default gateway defined.
Otherwise, they would lose the possibility of Internet access and access to the rest of the network.
Is there any other alternative to solve the problem?
Thanks!!
P.S.: On windows 7 it worked without any drawbacks
Tuesday, July 25, 2017 10:21 AM
Hi Daniel,
Did you mean after restart, the persistent static route is still listed in route print output, but it's not working?
If yes, please check if at the same time, same route record in another Windows 10 computer is also not working.
Update the route firmware for test.
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Tuesday, July 25, 2017 7:10 PM
Hi Karen:
It's correct.
After restart, the persistent static route is still listed in route print output, but it's not working.
On another Windows 10 computer, the same route at the same time, is still working flawless.
Best regards
Wednesday, July 26, 2017 9:41 AM
Hi Daniel,
If so, to know the issue better, please help me know:
1. What is the symptom of “route does not work”? Is it using another route? If so, does configuring higher metric for the persist route help?
2. Besides, please provide the result of “route print” on the machine that the route does not work. And tell me which route is the one should work.
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Wednesday, July 26, 2017 2:24 PM
Hi Karen:
1. What is the symptom of “route does not work”?
We can not reach the server on the other network:
C:\WINDOWS\system32>ping 192.168.50.1
Haciendo ping a 192.168.50.1 con 32 bytes de datos:
Tiempo de espera agotado para esta solicitud.
Tiempo de espera agotado para esta solicitud.
Tiempo de espera agotado para esta solicitud.
Tiempo de espera agotado para esta solicitud.
Estadísticas de ping para 192.168.50.1:
Paquetes: enviados = 4, recibidos = 0, perdidos = 4
(100% perdidos),
(Note: The messages are in spanish)
2. Besides, please provide the result of “route print” on the machine that the route does not work. And tell me which route is the one should work.
C:\WINDOWS\system32>route print
ILista de interfaces 5...1c 6f 65 c1 84 f5 ......Realtek PCIe GBE Family Controller 1...........................Software Loopback Interface 1
IPv4 Tabla de enrutamiento
Rutas activas: Destino de red Máscara de red Puerta de enlace Interfaz Métrica 0.0.0.0 0.0.0.0 192.1.1.194 192.1.1.202 291 127.0.0.0 255.0.0.0 En vínculo 127.0.0.1 331 127.0.0.1 255.255.255.255 En vínculo 127.0.0.1 331 127.255.255.255 255.255.255.255 En vínculo 127.0.0.1 331 192.1.0.0 255.255.0.0 En vínculo 192.1.1.202 291 192.1.1.202 255.255.255.255 En vínculo 192.1.1.202 291 192.1.255.255 255.255.255.255 En vínculo 192.1.1.202 291 192.168.62.0 255.255.255.0 192.1.1.170 192.1.1.202 36 224.0.0.0 240.0.0.0 En vínculo 127.0.0.1 331 224.0.0.0 240.0.0.0 En vínculo 192.1.1.202 291 255.255.255.255 255.255.255.255 En vínculo 127.0.0.1 331 255.255.255.255 255.255.255.255 En vínculo 192.1.1.202 291
Rutas persistentes: Dirección de red Máscara de red Dirección de puerta de enlace Métrica 192.168.50.0 255.255.255.0 192.1.1.170 1 192.168.60.0 255.255.255.0 192.1.1.170 1 0.0.0.0 0.0.0.0 192.1.1.194 Predeterminada 192.168.62.0 255.255.255.0 192.1.1.170 1
IPv6 Tabla de enrutamiento
Rutas activas: Cuando destino de red métrica Puerta de enlace 1 331 ::1/128 En vínculo 5 291 fe80::/64 En vínculo 5 291 fe80::91ae:2815:4388:b295/128 En vínculo 1 331 ff00::/8 En vínculo 5 291 ff00::/8 En vínculo
Rutas persistentes:
Ninguno
The route "192.168.50.0 255.255.255.0 192.1.1.170 1" does not work and is not in the active routing table.
Same situation with the route "192.168.60.0 255.255.255.0 192.1.1.170 1"
(Note: All IP addresses are private including those of the form 192.1.1.x)
Thursday, July 27, 2017 8:09 AM
Hi Daniel,
The route table looks right. With small Metric, these persist route should have priority over other routes.
The failed ping may not be caused by that the computer selected the wrong route. It is possible that the computer has accessed the gateway but not able to go further. When problem occurs, please run “tracert 192.168.50.1” and “ping 192.1.1.170”, then provide the results.
Besides, are these persists routes all needed? If not, please remove other persists routes, in case that these persist routes are conflicting each other.
Moreover, apart from using the persist route, what about adding a normal route?
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Thursday, July 27, 2017 1:24 PM
Hi Karen:
Here is the result of tracert.
C:\WINDOWS\system32>tracert 192.168.50.1
Traza a la dirección scm-pds [192.168.50.1]
sobre un máximo de 30 saltos:
1 * * * Tiempo de espera agotado para esta solicitud.
2 * * * Tiempo de espera agotado para esta solicitud.
3 * * * Tiempo de espera agotado para esta solicitud.
4 * * * Tiempo de espera agotado para esta solicitud.
5 * * * Tiempo de espera agotado para esta solicitud.
6 * * * Tiempo de espera agotado para esta solicitud.
7 * * * Tiempo de espera agotado para esta solicitud.
8 * * * Tiempo de espera agotado para esta solicitud.
9 * * * Tiempo de espera agotado para esta solicitud.
10 * * * Tiempo de espera agotado para esta solicitud.
11 * * * Tiempo de espera agotado para esta solicitud.
12 * * * Tiempo de espera agotado para esta solicitud.
13 * * * Tiempo de espera agotado para esta solicitud.
14 * * * Tiempo de espera agotado para esta solicitud.
15 * * * Tiempo de espera agotado para esta solicitud.
16 * * * Tiempo de espera agotado para esta solicitud.
17 * * * Tiempo de espera agotado para esta solicitud.
18 * * * Tiempo de espera agotado para esta solicitud.
19 * * * Tiempo de espera agotado para esta solicitud.
20 * * * Tiempo de espera agotado para esta solicitud.
21 * * * Tiempo de espera agotado para esta solicitud.
22 * * * Tiempo de espera agotado para esta solicitud.
23 * * * Tiempo de espera agotado para esta solicitud.
24 * * * Tiempo de espera agotado para esta solicitud.
25 * * * Tiempo de espera agotado para esta solicitud.
26 * * * Tiempo de espera agotado para esta solicitud.
27 * * * Tiempo de espera agotado para esta solicitud.
28 * * * Tiempo de espera agotado para esta solicitud.
29 * * * Tiempo de espera agotado para esta solicitud.
30 * * * Tiempo de espera agotado para esta solicitud.
Traza completa.
If I delete the persistent path and create it again with the same values, the problem is solved.
The recreated route appears in both persistent and active tables.
What I am saying is that when the route is not in the active routing table, the destination server is not reached, even though the route is defined as persistent.
The 192.1.1.170 gateway is actually a "Check Point UTM-1 security appliances" and the ping is blocked by default.
All persistent routes are required.
It's not possible to add a normal route since the users do not have administrator permissions to do it, besides being very annoying having to create the route every time you need to access the other network, after a workstation reboot.
Friday, July 28, 2017 12:56 PM
Hi Karen:
Sorry for the language troubles, but the outputs of my Operating System are in Spanish.
- Check whether the persist route is correctly bind to the interface.
a. Open command prompt(Admin), type netsh interface ipv4 show route:
C:\WINDOWS\system32>netsh interface ipv4 show route
Publicar Tipo Mét Prefijo Índ Puerta enl./Nombre int.
No Manual 256 0.0.0.0/0 5 192.1.1.194
No SYSTEM 256 127.0.0.0/8 1 Loopback Pseudo-Interface 1
No SYSTEM 256 127.0.0.1/32 1 Loopback Pseudo-Interface 1
No SYSTEM 256 127.255.255.255/32 1 Loopback Pseudo-Interface 1
No SYSTEM 256 192.1.0.0/16 5 Ethernet
No SYSTEM 256 192.1.1.202/32 5 Ethernet
No SYSTEM 256 192.1.255.255/32 5 Ethernet
No Manual 1 192.168.62.0/24 5 192.1.1.170
No SYSTEM 256 224.0.0.0/4 1 Loopback Pseudo-Interface 1
No SYSTEM 256 224.0.0.0/4 5 Ethernet
No SYSTEM 256 255.255.255.255/32 1 Loopback Pseudo-Interface 1
No SYSTEM 256 255.255.255.255/32 5 Ethernet
C:\WINDOWS\system32>route print
ILista de interfaces 5...1c 6f 65 c1 84 f5 ......Realtek PCIe GBE Family Controller 1...........................Software Loopback Interface 1
2. How you add persistent routes
I have defined the persistent route bound to the specific interface ("route -p add 192.168.50.0 mask 255.255.255.0 192.168.1.170 if 5") and reboot the workstation.
Everything seems to work properly.
I keep it under observation.
Thank you very much.
Best regards
Monday, July 31, 2017 1:23 AM
Everything seems to work properly.
I keep it under observation.
Thank you very much.
Best regards
Did you mean the issue was resolved?
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Tuesday, August 1, 2017 3:59 PM
Karen:
Sorry for the delay.
I do not know if the problem was solved.
I keep it under observation
Friday, August 4, 2017 1:41 AM
I do not know if the problem was solved.
Is the persistent route working fine after restart?
If yes, it should be resolved.
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Friday, August 4, 2017 6:49 PM
"...Is the persistent route working fine after restart?..."
Yes.
Thank you so much!!!