This was my bad.
I thought I had configured everything that could be configured. Added rules, disabled firewalls in both Windows and the router, tried it on different networks and different environments, etc. Having tried it through AWS, my office's guest network and primary network with the same results, I was totally convinced the problem was on the other side of the fence.
Ultimately, it was the router settings. I couldn't find anything on IPSec in the manual so I ran the policy update for it shown above. This should have been obvious, but that doesn't affect anything on the router side.
Jake and Jason from JHM spent over an hour walking through the issues I was experiencing and stuck with it until it was connecting. I owe them a big thanks for that.
After I got off the phone, I was able to tweak the security and restore some of the settings I changed in trying to get things going.
Here are the takeaways:
- The Windows firewall can stay on.
- I didn't need any Windows firewall rules for the Nortel client or UDP (Inbound or Outbound).
- The router firewall needs to be off. (I can probably add rules there. Need to look into it more.)
- I have a new Asus RT-N65R. The IPSec settings can be found under Advanced Settigns > WAN > Nat Passthrough. You want to enable IPSec Passthrough.
- The one thing I avoided trying because of aforementioned reasons and the fact I wouldn't be able to flash the car this way, was directly connecting to the modem. I should have just done it anyway.
- This was going to be the next step, but in hindsight, it would have been better to call my router mfg first to definitely eliminate this as the problem. Keep that in mind if you can't connect to the remote host through the router, but you can if you bypass it.
Now that the connection issues are resolved, I will commence flashing.
Bookmarks