RAS Redial vs. Alternative Reconnect Methods: Pros and Cons
Summary
- RAS Redial = built-in Windows redial settings (rasphone.pbk / RedialAttempts, RedialSeconds, RedialOnLinkFailure).
- Alternative methods = Task Scheduler + rasdial/rasphone scripts, PowerShell monitors, third‑party reconnection tools, persistent VPN client features.
Comparison table
| Attribute | RAS Redial (rasphone.pbk) | Task Scheduler + rasdial/PowerShell | PowerShell script/loop | Third‑party client / vendor feature |
|---|---|---|---|---|
| Ease of setup | Low–medium (edit pbk file) | Medium (create scheduled task) | Medium–high (scripting) | Low (GUI) |
| Reliability | Basic; can fail for some disconnect types | High if event triggers correctly | High — flexible logic & retries | Very high (if vendor supports) |
| Granularity of control | Limited (attempts, delay, link‑failure flag) | Good (trigger on events, network changes) | Excellent (custom backoff, alerts) | Excellent (built‑in recovery, split-tunnel handling) |
| Visibility / logging | Minimal | Good (EventLog triggers, task history) | Excellent (custom logs/notifications) | Varies by product |
| Security (credentials) | Stored in profile (may require saved password) | Can pass saved creds or store securely | Can use secure vaults / Windows credential manager | Usually secure integrated auth |
| Cross‑platform | Windows-only | Windows-only | Windows-only (unless ported) | Varies; some vendors support macOS/Linux |
| Maintenance overhead | Low after set | Low–medium (tweak triggers) | Medium (maintain script) | Low (vendor updates) |
| Advanced actions (failover, alerts, alternative servers) | No | Possible | Fully possible | Often built-in |
Pros and cons (quick)
-
RAS Redial (rasphone.pbk)
- Pros: built into OS; simple numeric settings; no extra services.
- Cons: limited triggers; may not handle all failure codes; unreliable in some environments.
-
Task Scheduler + rasdial/rasphone
- Pros: trigger on RasClient/NetworkProfile events; reliable reconnect on network restore; minimal custom code.
- Cons: needs correct event IDs and testing; saved credentials often required.
-
PowerShell/scripted monitor
- Pros: full control (exponential backoff, multiple servers, alerts, credential vaulting); robust logging.
- Cons: requires scripting skill and maintenance; must run continuously or as service.
-
Third‑party / vendor VPN clients
- Pros: engineered reconnect, session persistence, failover, cross‑platform options, support.
- Cons: may be paid; adds third‑party software; administrative overhead.
Recommendations (practical)
- For simple use: set rasphone.pbk RedialAttempts/RedialSeconds and RedialOnLinkFailure, test.
- For reliable automatic recovery: create Task Scheduler triggers on RasClient event 20226 and NetworkProfile event 10000 to run rasdial (or a small PowerShell reconnect script).
- For complex needs (failover, alerts, multi‑server): use a maintained PowerShell service or vendor VPN client with built‑in reconnect/failover.
Useful specifics (Windows)
- rasphone.pbk path: %USERPROFILE%\AppData\Roaming\Microsoft\Network\Connections\Pbk\rasphone.pbk (or %ProgramData%\Microsoft\Network\Connections\Pbk for all users). Edit keys: RedialAttempts, RedialSeconds, IdleDisconnectSeconds, RedialOnLinkFailure.
- Task Scheduler useful events: RasClient EventID 20226 (disconnect reason codes like 829, 629), NetworkProfile EventID 10000 (network connected). Action: %windir%\System32\rasdial.exe “ConnectionName” [user [pass]].
If you want, I can produce a ready Task Scheduler XML or a PowerShell reconnect script tailored to your VPN name and environment.
Leave a Reply