Comments
-
Thank you @Arkwright for following this. I did follow the discussion in the article, had the loopback set correctly apparently, then as you suggested, double-checked everything. The one set I had not been re-checking every time were the routing rules. I found a mistake there, and now things seem to be working to the new…
-
Thanks @Arkwright, As far as I can tell, the inbound NAT on .98 is just like the inbound NAT on the other xx.93-102s to the .100. And I do have a loopback on the 101.43. The loop back may be wrong (I think I don't completely understand loopback), it's set up as orig: Firewalled Subnets→xx.98, translated: xx.98 → 101.43 I…
-
Thanks @Markd. Yes traffic is passing through the firewall externally to internally and vice-versa. I don't understand the relevance of your question to the time-out period of the user interface for configuration.
-
Well, here's what I've tried most recently (which is not working), trying to get xx.xx.xx.98 ←> 192.168.101.43 X1: WAN ip's xx.xx.xx.93-102 X0: LAN 192.168.100.1 most of the Access/NAT rules apply to this mapping to multiple VMs X2: LAN 192.168.101.1 Access Rules: xx.xx.xx.98 → ANY allowed, and xx.xx.101.43→ ANY allowed…
-
Thanks, sorry I wasn't clearer. I'm working in configuring addresses, and NAT settings for 12 internal ip addresses on a TZ270. I test by setting a laptop to one of the internal addresses and pinging and telnetting from another on the same internal net. Often, but the time I've finished configuring the laptop to listen (a…
-
I have the same problem, and I have tried the setup in that KB article. It did not work for me. I have asked this same question, (sorry didn't see this thread) here: I've tried the packet monitor, and with the NAT external set to xx.xx.xx.98 and internal to 192.168.101.x the packets are dropped.
-
With a few hours of support from SonicWall support, who couldn't figure it out, (packet capture was showing nothing no matter what they did) they realized that this router was a replacement for one that was returned and asked, "Did you upload a configuration from the old router?" So we reset to factory settings, added in a…
-
Thank you. Found it after the very scary "The follow features are unsupported" warning.
-
This knowlegebase article "" seems to have the same issue I'm seeing and the suggestion is to add a static ARP, which I did, but am still not able to access the second IP address.
-
@ARKWRIGHT Thank you for your response. As an experiment I removed all Access rules, static ARP, and custom NAT entries. Then created, using the wizard, one set of 1 Access Rule and 3 NAT entries for Ping[Group], HTTP and HTTPS WAN to LAN, etc. for anywhere to .94. No response to ping. The .44 machine can ping the .10…
-
Thanks @ARKWRIGHT, WireShark capture of ICMP to .94 shows (no response found). I am NAT'ing Ping to .44 And I have .94 set up as a static, published ARP.
-
Hi @Preston, I have a TZ270 (7.01), and can't find the 'Enable Secondary Subnets'. Can you give me a pointer? It doesn't seem to be in my Diagnotics group anywhere (or anywhere else I can find) Thanks.
-
I'm having difficulty with this as well. I have a VM hosting multiple servers, and 13 static IPs from my ISP all coming in on one wire. I need to be able to assign specific static IPs to specific VMs. I've read all the postings I can find, have set up Access Rules, NAT policies and even static ARP routes. X1 is assigned…