Comments
-
Hi @BERNHARD_WINTER, We can avoid ARP issues between Primary and Secondary FW's by enabling Virtual MAC on the HA settings. The Virtual MAC is applicable to all interfaces.
-
Hi @JKJUNG, Thanks for your patience. I verified internally and seems like there are no similar issues found. Could you please upgrade firmware on one of the HA pairs to 6.5.4.8-89n and check for the same issue?
-
Hi @JKJUNG, Let me check for possible reported issues and get back to you. Please standby. Appreciate your patience.
-
Hi @JKJUNG, Thank you for visiting SonicWall Community. While the IP address is 0.0.0.0 on the active unit after failover, could you please check the IP address on the standby unit for WAN interface? Does it also show 0.0.0.0? What is the firmware on your TZ 500 and NSa 4650? Is this issue common to both the models of the…
-
Hi @ITWARLORD, Does it happen frequently? If so, could you please perform a packet capture on the SonicWall for pinging destination IP addresses as the firewall's local interface IP and any external IP address like 4.2.2.1? We can see what happens to the packets via SonicWall and find out the root cause.
-
Hi @NTI, I assume both the Computers are from different locations. If yes, possibly creating a DYNDNS on the Computer B location and blocking the same in the SonicWall WAN to WAN access rule for the SSLVPN service. Thereby we allow only the required IP's or domain names to connect to the SSLVPN on the firewall. There is…
-
Hi @NTI, Thank you for visiting SonicWall Community. It looks like you are trying to block remote access to computer on the local network where the SSLVPN user physically resides and allow remote access to the office computer when SSLVPN connection is in place. I'm afraid this may not be feasible with SSLVPN feature on the…
-
Hi @LARRYSCHWENK, Thanks for the answers. Have you used the subnet 192.168.0.x anywhere on the local network nor on the SonicWall? Could you please try the native bridge option as well and check for possible same issue?
-
Hi @SHATY, Thank you for visiting SonicWall Community. I have my SonicWall running on 6.5.4.8 firmware version. I don't see any issues. Could you please explain your scenario in detail? What clients (LAN users or VPN clients) are you referring too?
-
Hi @LARRYSCHWENK, Could you please check the DHCP scope on the SonicWall? Have you connected the laptop directly to the X4 port and received a IP on different subnet? Also, please make sure there is no common switch used between all these portshielded interfaces. If used, please ensure they are all segregated using VLAN's…
-
Hi @DIONDP, Thank you for visiting SonicWall Community. Your Guest users are behind the SonicWall and you have enabled the SSLVPN on the Guest VLAN. Your SSLVPN users should use the Guest VLAN interface IP (X0:V10 IP) in the Server field on the Netextender client. Being behind SonicWall and then trying to connect to the…
-
You are most welcome @AronS. I'm happy that I could help you!!!
-
Thanks @Larry for sharing the case and status.
-
@LARRYSCHWENK - No additional config required. By portshielding all interfaces with X0, all interfaces+X0 interface should be treated like they are on the same subnet and hence the devices connected to all these interfaces can talk to each other. This should work this way. Please give a try and let me know.
-
Hey @ARONS, The echo replies are treated to be high risk because firewall tends to allow access for ping. Any access allowed by the firewall is going to treated as high risk. Hence we diligently allow the accesses that are must for our requirement by creating specific rules. Security Service IPS by default has built-in…