2003 RRAS VPN stops responding to external VPN logon requests...

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Greetings...this one has me absolutely baffled...

I have a 2003 server (standard) SP1, fully patched, so far as I can tell,
running RRAS to process VPN conections. You boot the server, the WAN
interface is pingable from the cloud, and you can immediately logon via a VPN
client. no problem so far.

Then, after an undetermined period of time, when one attempts tc connect
from the cloud in the same fashion, the WAN interface is no longer
responding. It is no longer pingable, and will not process VPN logon
requests. There are no errors in the event viewer, and the RRAS service
appears to still be up and running.

Reboot the server, and all is well again.

This has baffled me for some time. I've replaced the WAN NIC a few times,
so I can't see how that's the problem. The only thing I HAVE noticed is this
problem seems to be post-SP1. Has anyone heard of such a problem with sp1?
experienced the same? able to offer any suggestions? (short of removing SP1,
which I haven't tried, and would rather not, if at all possible.)

I appreciate all your help!
 
scornflake said:
Greetings...this one has me absolutely baffled...

I have a 2003 server (standard) SP1, fully patched, so far as I can tell,
running RRAS to process VPN conections. You boot the server, the WAN
interface is pingable from the cloud, and you can immediately logon via a VPN
client. no problem so far.

Then, after an undetermined period of time, when one attempts tc connect
from the cloud in the same fashion, the WAN interface is no longer
responding. It is no longer pingable, and will not process VPN logon
requests. There are no errors in the event viewer, and the RRAS service
appears to still be up and running.

Reboot the server, and all is well again.

This has baffled me for some time. I've replaced the WAN NIC a few times,
so I can't see how that's the problem. The only thing I HAVE noticed is this
problem seems to be post-SP1. Has anyone heard of such a problem with sp1?
experienced the same? able to offer any suggestions? (short of removing SP1,
which I haven't tried, and would rather not, if at all possible.)

I appreciate all your help!
Click to expand...
 
I also have this problem restarting the routing and remote access service
seems to resolve the issue temporarily, but it returns within 24 hours
 
Back
Top