Thanks Paul He actually connects, if you look in his connection monitor, and the log shows keep alive communication going on, but he can't access any of our resources. He can't even ping one of our private ip addresses. I had his net admin open ports 500 and 15 on their firewall with no luck. Any ideas?
On Thu, 2002-09-19 at 18:49, Arnold, Paul wrote: > It might be a routing issue. > The one on a LAN - verify that he has no route to the destination > network. If he doesn't, then make sure his Default Gateway does not > assign a route to the same private range. (i.e. if he is trying to get > to 172.16.0.0 and his DG has a route to 172.16.0.0, the software client > will not work) > > It might be a traffic issue: > If his DG does not allow VPN traffic out or ISAKMP (UDP 500), then that > will stop you too. > > HTH > Paul > > > -----Original Message----- > From: Lee Griffin [mailto:[EMAIL PROTECTED]] > Hi All, > I've got a user who can't vpn, who has the exact same policy > configuration as another user that can vpn. They are on different > networks. The one who can't vpn is on a LAN with the ip 172.17.128.2, > the other has a random ip assigned when he dials in to his ISP. Is there > something that must be done on the LAN of the guy who can't vpn > (firewall, router, etc.) in order to allow him to vpn to a PRO-VX? --- [This E-mail scanned for viruses by Declude/F-Prot AV] =================================================================================================== To unsubscribe, send email to [EMAIL PROTECTED] In the body of the email put the following: unsubscribe sonicwall your_name The archive of this list is at http://www.mail-archive.com/sonicwall%40peake.com/
