Enzino78

Enthusiast ✭✭
Avatar

Join the Conversation

To sign in, use your existing MySonicWall account. To create a free MySonicWall account click "Register".

Enzino78 Enthusiast ✭✭

Badges (9)

3 Year Anniversary2 Year Anniversary5 LikesFirst Answer1 Year Anniversary10 CommentsName DropperFirst CommentPhotogenic

Comments

  • Thanks Michael ;-) I've traced the packet arrived to firewall and the only one dropped is the one depicted above for UDP port 137, sourced from SSL VPN connected client (10.0.10.10) with broadcast destination 255.255.255.255. Dropped by Policy (?), no output interface indicated. I belived such drop was caused by IPHelper.…
  • Thnaks @BWC used it but doesn't work in the customer scenario
  • Hello, Partner have tested the configuration with DHCP over VPN for remote gateway and it works smoothly as per they desiderata. Integrating the VPN configuration depicted in the below screenshots to the KBs you linked, he solved: Anyway thanks for your help.
  • I'm looking on some KBs to provide customer with directions to use this configuration in his environment. If you have some notes should be useful since on the SonicWall Knowledgebase I'm not able to find any related docs. Thanks
  • Thanks Thomas. Hope everything fine!
  • Hello Shipra, I've done some tests since I have avialbility of both TZ570 and SonicPoint Ni. As you mentioned, on Gen7 there is all the configuration needed to address the SonicPoint Ni usage. So, I've configured the firewall to manage such AP setting a dedicated WLAN zone and a proper provisioning profile. Then I've…
  • Thanks Shipra. I can confirm this, but I know from a partner with the same scenario, SonicPoint Nis aren't visibile in a gen 7 firewall UI and thus impossible to manage. But there is no official statement that Gen 7 firewalls support that generation of SonicPoint (Ni/Ne). Are you albe to provide any official docs?
  • Hello @JohnG as per I know, SonicWall has considerably reduced the price of its own SFP/SFP+ modules. Now are correctly priced and aligned with competitors. Ask your Distri.
  • Thanks Michael. I've received also this feedback: I would use Advanced BWM type, as it does not require any settings on the interfaces. - http://help.sonicwall.com/help/sw/eng/9410/26/2/3/content/Firewall_BWM.071.5.htm
  • Same situation here. Any confirmation the timeframe for the upgrade/update operation has ended at 9 am CEST? (SonicWall indicated The release window has been extended to 72 hours from 12am on Saturday May 15th to 12am on the Tuesday May 18th 2021 - all times in US Pacific Daylight Timezone)
  • Sohpos and Zyxel are recognized... no mentions for the other relevant security vendors. Michael, I think you're right.
  • During a SonicWall webinar, I was able to take this picture that officially solve this issue:
  • Ciao Paolo, in your mysonicwall account there is a section named Report Issues that allow you to provide a sampel file to SonicWall team in order to verify a false positive or a false negative. Have a look below: Maybe this can help you for a future problem, since for this the time went by. Cheers
  • I'm quite sure there will be no problems. Some concerns on Ne AP that are already EOS. But as you have senteced Time will tell. ;-)
  • Thanks Ajishlal for your feedback. So maybe there is an issue in the description: both of them are indicated as 802.3AT injector (up to 30W) but 02-SSC-0003 is marked PoE+ while 01-SSC-5545 is marked PoE instead. What is correct? If both adhere to 802.3AT they are classified as PoE+ injector. Or... 01-SSC-5545 is 802.3af…