TZ 200 having problem contacting sonicwall license site because the default MTU 1500 is a problem.
Their tech guy changed MTU to 1492. He said he observed this problem with PPPOE connections
Sonicwall is using salesforce.com for their job-logging.
Sonicwall tech is using logmein123.com for remote access.
Overall, it is a very good support case.
Showing posts with label TZ 200. Show all posts
Showing posts with label TZ 200. Show all posts
Friday, May 7, 2010
Tuesday, March 23, 2010
configure TZ 200 sonicwall - use wizards to configure just like EBS/SBS of MS
TZ 170 is slow handling 25 users.
now TZ 200 is used instead.
well, the problem with it is not new. manually doing it is Not working for incoming connections.
the proper way to setup is to
1. add network objects
2. add services
3. group objects
4. run wizards (especially the Public server wizards)
the most important thing is now RUN Wizards ... this way will auto-populate some NAT rules which are not present in manually configuring simply firewall rules like lan-wan, wan-lan
Public Server Configuration Summary
Please review the settings below and click "Apply" to create the new objects listed below.
Server Address Objects
1. Create 'SonicwallTZ200mgmt Private' assigned to LAN Zone for Host 192.168.1.1.
2. Reuse 'WAN Primary IP' address object assigned to WAN Zone for 2xx.xxx.xx.xx.
Server Service Group Object
1. Create 'SonicwallTZ200mgmt Services' with HTTPS Management Service.
Server NAT Policies
1. Create Inbound Server NAT Policy to rewrite packets to original destination 'WAN Primary IP' to translated destination 'SonicwallTZ200mgmt Private'.
2. Create Outbound Server NAT Policy to rewrite packets from 'SonicwallTZ200mgmt Private' to translated source 'WAN Primary IP'.
3. Create Loopback NAT Policy to allow access from all internal zones to the server at public IP address 2xx.xxx.xx.xx.
Server Access Rules
1. WAN > LAN - Allow 'Any' to 'WAN Primary IP' for Service Group 'SonicwallTZ200mgmt Services'.
Similar rules will be created from all lower security zones to the LAN zone.
To apply these settings, click Apply.
now TZ 200 is used instead.
well, the problem with it is not new. manually doing it is Not working for incoming connections.
the proper way to setup is to
1. add network objects
2. add services
3. group objects
4. run wizards (especially the Public server wizards)
the most important thing is now RUN Wizards ... this way will auto-populate some NAT rules which are not present in manually configuring simply firewall rules like lan-wan, wan-lan
Public Server Configuration Summary
Please review the settings below and click "Apply" to create the new objects listed below.
Server Address Objects
1. Create 'SonicwallTZ200mgmt Private' assigned to LAN Zone for Host 192.168.1.1.
2. Reuse 'WAN Primary IP' address object assigned to WAN Zone for 2xx.xxx.xx.xx.
Server Service Group Object
1. Create 'SonicwallTZ200mgmt Services' with HTTPS Management Service.
Server NAT Policies
1. Create Inbound Server NAT Policy to rewrite packets to original destination 'WAN Primary IP' to translated destination 'SonicwallTZ200mgmt Private'.
2. Create Outbound Server NAT Policy to rewrite packets from 'SonicwallTZ200mgmt Private' to translated source 'WAN Primary IP'.
3. Create Loopback NAT Policy to allow access from all internal zones to the server at public IP address 2xx.xxx.xx.xx.
Server Access Rules
1. WAN > LAN - Allow 'Any' to 'WAN Primary IP' for Service Group 'SonicwallTZ200mgmt Services'.
Similar rules will be created from all lower security zones to the LAN zone.
To apply these settings, click Apply.
Subscribe to:
Posts (Atom)
