Random Timeouts

[eK!]

I posted this to the Sonicwall forum as I have a feeling to could be a firewall problem but got no repsonse. I'm hoping someone has something to point me in the right direction on this!

I'm pulling my hair out on this one :crazy:

Post #1

Has anyone had issues with random timeouts between only certain VPN and public connections? I have no problems connecting to servers on the local lan but certain connections seem to drop when connecting from remote offices via vpn.

Here is an example of what is happening

IP 1 & 2 can be pinged on the local LAN.

IP 1 responds to ping requests from VPN sites

IP 2 does not respond to ping requests from VPN sites

If I keep a constant ping going from the remote site the devices are reachable, otherwise they will "go to sleep"

I thought it was a switch issue at first but I'm not so sure now as the devices are separated.

Post #2

Anyone have any ideas on this? I can only think of 3 possibilities: Switch, Sonicwall and maybe our ISP. The more I look into this the more I notice that a good # of devices are not reachable from the remote networks while other devices on the same network are. I have constant pings going to keep the devices alive, never had this issue before...

[+BudMan MVC]

What are the network segments on both sides of the VPN? An how are you creating the VPN? Why are public connections involved?

The way I read your issue is you have some machine in one location A connected to Location B with VPN.

Location A can ping some machines in location B, but not others? An vice versa?

But if you keep a ping going between A1 and B1 all is good for A1 and B1, if you do not ping B1 can some times be reached by A1 but not other times?

Really need to have some understanding of how you creating the VPN between these locations.

[eK!]

There are 4 locations total, connected via Sonicwall boxes site-to-site VPN. All different private IP schemes (A = 192.168.50.*, B = 192.168.51.*, C = 192.168.52.*, D = 192.168.53.*)

Location A is where the problems have been occuring.

Location A can ping any node at location B,C & D rarely failing.

Location A can ping any node on it's local LAN.

Location B,C & D cannot ping nodes at Location A at times. Any node open to the public (port forwarding) acts the same way, non-responsive.

If I have a constant ping going from location C (or any location) to the critical nodes at Location A they are always responsive. It's been my workaround for the time being.

This is an "old" network, it's been in place in it's current state for 3+ years. I haven't made any changes on my end to hardware, firmware updates etc. I'm thinking it's hardware failure somewhere but I don't want to put in a new firewall or switches and find that it was the ISP doing something funny.