We have a set of bonded T1's which are only used as a failover in the event that our fiber connection goes down. Occasionally, we'll use these T1's as a test environment when configuring network appliances for our branch locations.
We've run into a very strange issue that has us completely baffled. We purchased an ASA 5505 for one of our branch locations and brought it onsite but for some reason we couldn't get it working with the Verizon DSL connection that we have there.
We brought the 5505 back to our main office and tested it on our failover T1's but still couldn't get it to work. Thinking that something must be wrong with the appliance, we RMA'd it and got a replacement. This time around we decided to test it on the T1's prior to going out to the branch location, however the replacement didn't work either.
We confirmed that the T1's are working by reconnecting the Sonicwall NSA 240 that we have pre-configured in case of an emergency. With the NSA plugged in, everything works fine.
That being the case, we decided to order a small Sonicwall TZ 105 for the branch however when we tested it on the T1's (with the same settings as the NSA) it would not establish a WAN connection.
We spent about 3 hours on the phone with Sonicwall support who finally gave up and sent us a new TZ 105 which we just received this morning.
We plugged it into the T1's and sure enough, it also will not pass any WAN traffic. We cannot even ping the ISP gateway address (T1 router)
- We've opened up ANY > ANY (WAN > LAN / LAN > WAN) on the firewall
- We've confirmed that the WAN settings are the same between the working NSA and the TZ.
- We've rebooted the T1 router several times during the troubleshooting process
- As I mentioned, we've spent hours on the phone with Sonicwall support.
We've tried everything we can think of which is why I'm reaching out to the experts here on Spiceworks to see if you guys have any ideas as to why we cannot get these appliances working.