Why Experts Exchange?

Experts Exchange always has the answer, or at the least points me in the correct direction! It is like having another employee that is extremely experienced.

Jim Murphy
Programmer at Smart IT Solutions

When asked, what has been your best career decision?

Deciding to stick with EE.

Mohamed Asif
Technical Department Head

Being involved with EE helped me to grow personally and professionally.

Carl Webster
CTP, Sr Infrastructure Consultant
Ask ANY Question

Connect with Certified Experts to gain insight and support on specific technology challenges including:

Professional Opinions
Ask a Question
Did You Know?

We've partnered with two important charities to provide clean water and computer science education to those who need it most. READ MORE

troubleshooting Question

Cisco RV VPN - Attempt to Compromise Security

Avatar of intcomser
intcomser asked on
Windows NetworkingDNSInternet Protocol Security
5 Comments1 Solution624 ViewsLast Modified:
Hello -

I just setup a Gateway-to-Gateway VPN using two Cisco RV042 firewalls (to keep costs down) to support a temporary office.  The VPN works correctly in that workstations at the remote office can contact the server and other resources at the main office.  However we seem to have a 'rolling' error wherein some of the VPN workstations can't access server resources and instead get the dreaded 'Attempt to compromise security' message.  I have been over everything I and Google can think of so I am hoping someone here can offer some advice.  Here are the specs on the VPN and network:

Windows SBS 2011 Network (fully patched)
Single domain controller at main location
Windows 7 workstations at remote location
Two Cisco RV endpoints (fully patched)
Windstream Metro Ethernet at main location
Verizon DSL at remote location (modem is NOT bridged)
All workstations use the single domain controller as their only DNS server

I have ensured that all workstations are using the domain controller as their only DNS server and that name resolution is working correctly.  I can ping the DC from the workstations but anything that requires Kerberos authentication simply doesn't work.  I have played with MTU settings, NAT Traversal, etc. (everything is currently back to the default configuration.  If I shut everything down at the remote location and bring it all back up a few workstations will simply refuse to connect.  If it bring it all down and back up again a different set of workstations will refuse to connect.  There are only 7 workstations at the remote location and bandwidth/throughput is good (no problem opening files or accessing the Exchange server when they properly authenticate).  There is a wireless network at the remote location (just an access point hanging off the RV) and sometimes switching from wired to wireless (or vice versa) will allow a previously non-working workstation to connect.  

The only issues I can think of would be bandwidth related, or just the fact that I went cheap and used RV models.

This has me absolutely puzzled.  Any thoughts would be greatly appreciated.
Avatar of Rich Rumble
Rich RumbleFlag of United States of America imageSecurity Samurai
This problem has been solved!
Unlock 1 Answer and 5 Comments.
See Answers