Search results for query: *

I see from the log that NAT is detected. I assume it is trying to take some action to accomodate the NAT. I suggest testing with a direct non-NAT'ed connection and see if that works. If so you would then need to figure out what they are trying to do when NAT is detected.

What VPN product are you using?

Barring an ISP problem or diffeences between upstream and downstream speeds there are two things I would look at. First I would check the port speed and duplex settings of your uplink. If that's not it, I would also look into the MTU settings on the VPN routers. I have had issues where a...

What you described sounds like a bug in the v6 code. My only thought is that the issue may be fixed in the v7 release that came out this week.

I believe the Contivity can support what you suggest. Are you having a particular issue in the implementation?

Another thought is to make sure that the tunnel is not "nailed up". Allowing the tunnle to tear down when not needed may help clear the bogus networks.

The option to upgrade the OS is under the Administration menu. The VPN server uses FTP as a client to pull the new OS from an FTP server. I can post more/better details a bit later today when I am looking at the GUI.

Unfortunately there is nothing you can do with this one. Only one application can bind to IPSec. It is much like trying to run two web servers on port 80. One will work , and one will fail. If using multiple vendors IPSec servers is a requirement, you could try something like RSA's Keon product.

It sounds like this is one of the many network address translation issues. The problem is that when the server sends a keepalive or rekey request back to the client using UDP port 500, the NAT table does not know which session to send it to, so the packet, and eventually the session gets...

If it is not working at all it is most likely that UDP 500 traffic is not passing in both directions. If the connection come up for some time and then drops, it is probably because UDP 500 is not allowing inbound traffic from the IPSec server.

I have had the same issue, here is how I fixed it: Use regedit to search for and delete the following entries: ipsecshm contivity extranet nortel Some edits may need to be done in safe mode. After a reboot you should be ok barring any other issues. Steve