WilliamIMS2
asked on
Creating an Access Rule in SonicWall 2040 pro - Enhanced OS
We are trying to open up port for our customer on their Sonicwall 2040.
They originally had port 25 opened to a group of IP ranges which works fine, i tried to duplicate this rule with our IP ranges but it didn't work (I created a new network object with our range and then added a access rule).
I then added our range to the group that they already had set up and this works fine.
However, we now need to open up another port (service) to our IP range so I'll need to create a new rule, however our connections are still being rejected.
Sorry for the vagueness, but do you have any ideas what I'm doing wrong?
They originally had port 25 opened to a group of IP ranges which works fine, i tried to duplicate this rule with our IP ranges but it didn't work (I created a new network object with our range and then added a access rule).
I then added our range to the group that they already had set up and this works fine.
However, we now need to open up another port (service) to our IP range so I'll need to create a new rule, however our connections are still being rejected.
Sorry for the vagueness, but do you have any ideas what I'm doing wrong?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You can change the priority ranking of an access rule by clicking the Arrows icon in the Priority
column. The Change Priority window is displayed. Enter the new priority number (1-10) in the
Priority field, and click OK. 1 being the highest priority.
Thank you.
column. The Change Priority window is displayed. Enter the new priority number (1-10) in the
Priority field, and click OK. 1 being the highest priority.
Thank you.
ASKER
Hi dpk,
This is exactly what we did.
1. We created a new network object with our IP range
2. Created a wan --> lan rule to allow access to port 25 from our network object
3. Moved the rule to the top of the list
Our connections are then immediately rejected.
I then changed the rule too allow access from 'any' and our connections were still immediately rejected.
However, adding our Network object to their already defined rule for port 25 allowed us access.
I now need to open up port 389 and we are having the same problem. I'm creating a rule that is identical to the one that works but the firewall immediately rejects our connections - I'm sure there is something simple that I am overlooking.
Thanks a lot for your help.
This is exactly what we did.
1. We created a new network object with our IP range
2. Created a wan --> lan rule to allow access to port 25 from our network object
3. Moved the rule to the top of the list
Our connections are then immediately rejected.
I then changed the rule too allow access from 'any' and our connections were still immediately rejected.
However, adding our Network object to their already defined rule for port 25 allowed us access.
I now need to open up port 389 and we are having the same problem. I'm creating a rule that is identical to the one that works but the firewall immediately rejects our connections - I'm sure there is something simple that I am overlooking.
Thanks a lot for your help.
Can post some sanitized logs which would indicate what is blocking the traffic; also have you configured NAT for the internal server.
Thank you.
Thank you.
ASKER