Hi, We have a client who has SBS2003 which has been running for years. They regularly use VPNs to connect in from home and we use the VPN to connect in to support them. These have always worked in the past. Recently their access has started doing something a bit funny. When they try to connect to the VPN it goes through the motions and seems to log them on as you would expect. However once they are connected the VPN reports 'Limited Connectivity' and they cannot access any network resources over the VPN. Checking ipconfig shows that they have the expected IP address, DNS, etc so it all looks like they're connected fine - it's just they can't access the network. Restarting the RRAS service doesn't help, but rebooting the server does. Having said that it is intermittent. The issue can crop up and then go away of its own accord without a server reboot. I was thinking this was limited to one server but we have now had a second site report exactly the same issue. Likewise they have SBS2003 and have had it in place working fine for years. When you look in the event logs on either server it doesn't tell you anything. All you get is the usual pair of messages reporting a user connected, how long for, when they disconnected and how much data was transferred. So everything looks like it's worked. The client connects and gets an IP address as you'd expect - they just can't use the VPN once it's up. I don't really know where to look next. The event logs are not showing anything up, but it's happening on two separate installations. If there a Microsoft Update that has introduced this issue? If so is there a hotfix to resolve it? Any help would be appreciated. Cheers, Neil Info - In case it has relevance at first we found the following events logged on one server, but having followed an article it has not happened in over a fortnight. I include them here for completeness since they relate to RAS in case it does shed any light on the main issue. Event Type: Error Event Source: Microsoft H.323 Gatekeeper Event Category: None Event ID: 21056 Date: 19/06/2009 Time: 12:40:07 User: N/A Computer: SERVER Description: An error has been returned by the <setsockopt> API. API error code: 00002741H. API error text: The requested address is not valid in its context. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. ----------- Event Type: Error Event Source: Microsoft H.323 Gatekeeper Event Category: None Event ID: 21056 Date: 19/06/2009 Time: 12:40:07 User: N/A Computer: SERVER Description: An error has been returned by the <WSAJoinLeaf> API. API error code: 00002741H. API error text: The requested address is not valid in its context. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. ---------------- Event Type: Error Event Source: Microsoft H.323 Gatekeeper Event Category: None Event ID: 21075 Date: 19/06/2009 Time: 12:40:07 User: N/A Computer: SERVER Description: Failed to create a RAS context for the IP address 192.168.16.19. Please insure that no other application or service is using the H.225 RAS ports (1719 and 1718). Context status code: 00002741H Context status text: The requested address is not valid in its context. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. ------------------ I did a search on these messages and found the following article http://support.microsoft.com/kb/937534/en-us which I followed. These messages have not appeared since I followed the article, but it has made no difference to the main symptom so I suspect they are red herrings - I have included them in this description in the interest of giving as much information as possible.