Hi Shorty
Saw this post just now. Are you still experiencing this problem? Can
you send us the following logs when it occurs
Execute the following from the command prompt
- netsh ras set tr * en <this enables logging>
- reproduce the issue
- netsh ras set tr * di <this disables logging>
This will generate logs in the %WINDIR%\tracing directory. Please zip the
log files and send them to me at
(E-Mail Removed). Please generate logs
on both the client and server machines using the above procedure.
Also please let me know what kind of error u see on the client when you
setup the connection. Are you using a Windows client?
thanks
Aanand
"Shorty" <(E-Mail Removed)> wrote in message
news:C5D1BE07-948A-46EB-AC71-(E-Mail Removed)...
> We have a Windows 2003 VPN server which is also a Terminal server as well.
> At
> least once per week we can not connect to the VPN and the only fix seems
> to
> be to restart the Routing and Remote Access service. I have switched all
> logging on that I can find under the Routing and Remote Access MMC, but
> there
> are no errors either in the logfile or in the Event viewer for the Remote
> Access filter.
> The rest of the time the service runs ok and we can access all resources
> correctly.
> We recently installed Win 2003 SP2 but this behaviour has carried on
> happening.
> Does anyone know how I can debug this further or fix thi sissue?
> Thanks
>
Similar Threads
Linear Mode
