Two things to try / check:
1) In the Watchguard Policy Manager turn the logging level up for the VPN 
connection, and then watch the logs when the RDP drops.
2) In your Mobile User VPN settings (assuming you're used the WG MUVPN 
Client and not PPTP or SSLVPN check the timeout length (set bandwidth to 0 
and time to 24 hours for example).





"Paul Everett" <[EMAIL PROTECTED]> 
08/26/2008 08:53 AM
Please respond to
"NT System Admin Issues" <[email protected]>


To
"NT System Admin Issues" <[email protected]>
cc

Subject
RE: remote access






Anything in the Event Logs on either end?  On the client as far as a 
reason for the connection dropping, or on the server as far as a reason 
for the connection being denied?
The only thing in the event log on the TS is event 551 (logoff).  Below is 
the description.  Event 538 ?sometimes? does not appear after 551, 
sometimes it does.  This may explain why we are unable to reconnect 
immediately after losing connection to the TS, and is probably separate 
from the connection issue.
If a Security 538 message does not appear shortly after the Security 551 
message, a program or service might not be managing its access tokens 
correctly. Although the user cannot access objects, the program or service 
might have cached an access token and therefore retained the ability to 
access objects.
On the client there is a Remote Access event that establishes the VPN, but 
no events are generated when the RDP session is initiated or dropped.
During the RDP drop for one user, can another user still use / connect to 
the server?
 
I don?t know.  There are only a few users who connect at random times.
 
 
Does disconnecting from the VPN as soon as the RDP is dropped, and then 
reconnecting to VPN allow the RDP session to be reconnected?
 
I would have to say ?sometimes?. 
I just got off the phone with a user who was connected to the VPN but 
couldn?t connect to Remote Desktop.  He couldn?t ping anything on my 
network.  After disconnecting and re-establishing the VPN he was able to 
connect to Remote Desktop, but it was dropped after 9 minutes.
 
Last night I connected to our VPN from home and although I could ping my 
network, the connection was so pitifully slow, I couldn?t connect to 
anything.  It affected everything on my computer as well.  I was basically 
dead in the water until I disconnected the VPN.
 
A couple days ago I connected without any problem and stayed connected to 
Remote Desktop for almost an hour before I ended my session.
 
The only consistent thing I?ve found is that none of my users can stay 
connected for more than 20-30 minutes, if they are lucky.
 
We are using a Watchguard firewall for VPN access.
 
Paul

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: Monday, August 25, 2008 8:11 PM
To: NT System Admin Issues
Subject: RE: remote access
 
 
 

 
 

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

Reply via email to