Comments
-
@daniel_lilja, Since this was for Gen 7 appliances, I had provided this as a feedback during the beta process. You can use GEN7-11974 as the ID which was created to track this. Thanks!
-
@GAG, I completely agree with @BWC. Please enable user login on the WAN interface and on the access rule created from WAN to LAN, use the Users included field as Trusted Users/Everyone. Leave the NAT policy as it is. I tested this is my lab and it worked as expected. I created a local user on the firewall and once I…
-
@daniel_lilja, Unfortunately, yes. But I would suggest reaching out to your Sales representative and adding your request as well to the existing RFE. That helps us prioritize the requests. Thanks!
-
Hello @daniel_lilja, Yes, I see this already as an RFE. For your reference it is RFE ID: 2471. It is currently under review from development team. Thanks!
-
Hello @daniel_lilja, I tested on my end and also getting the same results. I am checking internally and will keep you posted. Thanks!
-
Hello @Flyers2020, Welcome to SonicWall community. Usually the end computers try to use the primary DNS server configured on their adapter to perform DNS resolutions either internal or external. For the SonicWall to correctly send the DNS traffic for internal and external DNS resolutions, DNS proxy feature can be used.…
-
Yes, it is already created for Gen 7 appliances.
-
@SomeBodyElse, Please try the following. Try to ping 192.168.168.169 from Investigate | System Diagnostics | Select ping in the diagnostic tool and see if that works. If it does, please add the following NAT policy and test the pings from the SSLVPN client. Original source: SSLVPN IP pool (10.11.11.x) Translated source: X0…
-
@SomeBodyElse, What is the status of those packets? Please do a packet capture based on the source IP alone: 10.11.11.1 with Ether type as IP and IP type as: TCP, UDP, ICMP and share a screenshot here of the packet monitor if that's okay. For real time assistance, you can reach out to our Support team. Thanks!
-
Sure, Keep us posted!
-
Hello @SomeBodyElse, Welcome to SonicWall community. Could you please use a different SSLVPN IP pool like 10.11.11.0/24 as 192.168.1.x is the most common private subnet. Also, is this taking place for multiple clients? Have you tested this using a different ISP connection on the client side? Thanks!
-
Hello @Imperial, Welcome to SonicWall community. Based on the syslog server address, the SonicWall checks how it can reach that address and uses the interface IP through which it is reachable as the source address on the syslog messages sent. I do not understand how the routing is done and what is the exact requirement.…
-
@kyar600, Welcome to SonicWall community. The best way to figure out what needs to be blocked is enabling the activity logs for approve device events and when you connect the phone, you should be able to see the activity logs. Then you can easily build the rules to block it. Thanks!
-
@Katz, Welcome to SonicWall community. So, the users that are not part of the domain, when you ping google.com on them, is it failing? Also, if you are pinging 8.8.8.8 from the same machine is that working fine? It is highly unlikely that this would be a NAT policy issue as that would affect the internet access even when…
-
@djhurt1, So, are the wireless clients using RADIUS based EAP authentication or just using a PSK? What exactly is happening to the clients that are not joined to the domain? Are they unable to connect to the wireless network or access internet? Thanks!