• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 941
  • Last Modified:

Sonicwall NSA2400 second WAN ip unprotected

a most likely easy question here:

have a sonicwall NSA 2400..

New fiber service installed for it with TWO WAN ip's (not side by side)

i have put the .122 IP on X1 as primary WAN for the LAN... no problems there all working as it should!

Would like to use .110 for a video conferencing solution OPEN to the internet (NO protection at all!) I have plugged it into X5 port and set it as a DMZ layer 2 bridged connection to X1. Open up traffic to and from dmz>wan... setup the vc box as the 110 address and no joy....

what have i missed??

(i have X2 setup with a local ADSL2+ service in a spillover LB config using ppoe)

thanks community!
  • 3
  • 2
1 Solution
What does "no joy" mean?
just0nAuthor Commented:

basically after i setup the above enable any/any from dmz>wan AND wan>dmz it still not working...
cannot ping the vc solution externally and the vc solution cant ping anything... (except itself)

i am looking again today with 'fresh eyes' as it was a bit of a bad week last week...

I understand...let me know what the fresh eyes find.
just0nAuthor Commented:
ok solution found...

So instead of leaving the VC solution (and assume it was fine) i plugged in a laptop and set it up on the static ip... guess what.. IT WORKED!!! grrr

anyway for those who may run into this with a sonicwall...

I am using a Lifesize Express 200 video conferencing solution (as it MAY be unique to this device)

After much fiddling i found if i set the NIC to 10Mbps (full duplex) rather than AUTO which set the port at 100Mbps full duplex then reboot the VC solution.

After reboot the sonicwall set its port (X5) to 10Mbps HALF duplex and it worked!

If this is not useful mods please remove..

damn last week was bad!
thanks for the support digitap :)

I think the information IS useful.  I was working with a client the other day who received a new ultrasound modality.  After they acquired their images, it would take 10 - 20 minutes before the images would appear on the diagnostic physician workstation.  Rather than contact the vendor they asked me to fix it.  Turned out, the NIC was configured for 100MB/Full Duplex.  I changed it to Auto and the images would appear almost instantly.

Glad you got it worked out!
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

On-Demand: Securing Your Wi-Fi for Summer Travel

Traveling this summer?Check out our on-demand webinar to learn about the importance of Wi-Fi security and 3 easy measures you can start taking immediately to protect your private data while using public Wi-Fi. Follow us today to learn more!

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now