VPN Access

Well, w/o being there to look at the network my first question would be is there an intrusion detection system that might be thinking you are doing a ping sweep on the network. So basically, look for some firewalls that might be turning off ping for that address. Second, make sure that the users are properly authenticating with on-site servers if in a domain/active directory environment. W/o knowing more I can't really guess what the problem would be.

I was recently having a problem with this kind of a situation. As it turned out, I had the VPN address going to the server's address in the wrong subnet mask. i.e. we have a subnet that covers the first 64 addys, I had it authenticating to x.x.x.11,but it's address was going to be x.x.x.106. Once I had it connecting to the server's address in the right scope, it worked fine.

How do I get clients to connect using to proper subnet mask. Clients are always assigned 255.255.255.255 as a mask and there's no where to change it. Thanks

Go into your TCp/IP properties (in the properties screen for your connection) and take off DHCP, set it up manually. Use the IP address you want to use, subnet mask of 255.255.255.whichever one you want, and set your default gateway as your DHCP server.

Thank you very much for your suggestions but I've resolved the issue. We have a watchguard firebox between our router and LAN, the box was set to use the same range of IP addresses for its' VPN users as the Windows 2000 server so the packets were being dropped. I've changed the Win2K address range and am working great now. Thanks again