Changes in RRAS require IPSEC Services Restart???

[vbman213]

I've been working on configuring a L2TP w/ ipSec on my home server using Windows Server 2003. I keep running into a problem with making configuration changes to the Routing and Remote Access Services causing IPSEC to deny connections.

Basically, the PPTP Server responds and functions properly. However, for no reason what-so-ever, the L2TP server refuses all connections unless I reboot RRAS (RemoteAccess) and IPSEC Services (PolicyAgent).

I have to run this script every time I make configuration changes in Routing and Remote Access:

net stop RemoteAccess
net stop PolicyAgent
net start PolicyAgent ------ Very important that IPSEC restarts before RRAS
net start RemoteAccess

Why?

[jdc2000]

Depending on what changes you are making, that behavior may be by design. More details might be helpful, however, this is the sort of question that may be hard to answer.

[SpywareDr]

I have to run this script every time I make configuration changes in Routing and Remote Access:

net stop RemoteAccess
net stop PolicyAgent
net start PolicyAgent ------ Very important that IPSEC restarts before RRAS
net start RemoteAccess

Why?

Because the configuration is read once on bootup.

If you make a change after bootup, you need to force the computer to re-read the configuration. One way is with the four commands you posted, the other way is to reboot.