Route sentry not working on windows 7..HELP!?

[Fishzn]

I have tried all your suggestions but the only time when I don't get routing errors in Route Sentry (and when my routes are in fact setup correctly) is when I untick the "Use default gateway on remote network" option on both connections
Reply With Quote

Yep tried this before and can confirm that it does in fact work for me too however it does not work all the time, in addition eventually the connections stop working even though they remain connected, only a disconnect/reconnect works to sort it out. Right now the batch file is working perfectly for me on startup

 

[Pada]

Fishzn, I have spoken to w.m. a couple of times yesterday, trying to figure out how to get RouteSentry working on Windows 7. One thing that I have to say is that you should NEVER untick that "Use default gateway on remote network" on the international connection! If you do that, it will cause international & some local traffic to go through the international connection.
Like if you have a WebAfrica account for international traffic and you tick that option, then it would result in ALL 41.*.*.* destinations going through your international connection, instead of going through the local only one.

w.m. said that RouteSentry was unable to setup the routing table if the international connection wasn't dialed first.
What I would suggest is: dial the international connection before you even open RouteSentry. Then open RouteSentry and enable the options that RouteSentry must automatically dial the connections.

You can test if the routing is working correctly by opening command prompt, and typing in:

tracert -h 2 mybroadband.co.za
tracert -h 2 telkom.co.za
tracert -h 2 www.sun.ac.za
tracert -h 2 google.co.za

The first 3 destinations are all local (mybb, telkom & stb univ) and google.co.za is international. Thus the routing info to the first 3 destinations should look exactly the same, where as the one going to google.co.za MUST look different.
eg.:

Tracing route to mybroadband.co.za [41.203.21.136]
over a maximum of 2 hops:

  1    24 ms    22 ms    22 ms  dsl-185-78-1.dynamic.wa.co.za [41.185.78.1] 
  2    44 ms    46 ms    46 ms  wgw-cr-1.wa.co.za [196.220.59.238] 

Trace complete.

Tracing route to telkom.co.za [196.43.22.222]
over a maximum of 2 hops:

  1    24 ms    23 ms    22 ms  dsl-185-78-1.dynamic.wa.co.za [41.185.78.1] 
  2    46 ms    46 ms    46 ms  wgw-cr-2.wa.co.za [196.220.59.250] 

Trace complete.

Tracing route to stbweb03.stb.sun.ac.za [146.232.20.38]
over a maximum of 2 hops:

  1    22 ms    23 ms    26 ms  dsl-185-78-1.dynamic.wa.co.za [41.185.78.1] 
  2    43 ms    46 ms    46 ms  wgw-cr-2.wa.co.za [196.220.59.250] 

Trace complete.

Tracing route to google.co.za [64.233.169.104]
over a maximum of 2 hops:

  1     *        *        *     Request timed out.
  2    45 ms    42 ms    43 ms  196.6.121.38-backbone.cybersmart.co.za [196.6.121.38] 

Trace complete.

* Note: this trick might not show a difference between local & international destinations when both your local & international accounts are from the same ISP (eg.10GB WebAfrica local only via SAIX & 3GB WebAfrica international via SAIX).

The best way would be to download rs-help-v3.1.bat to a specified folder (ie. desktop / my docs), then run it and follow the instructions. That way I can check whether RouteSentry setup the routing table correctly.