Reverse NAT
Hi, I'm trying to remote to my server located in 192.168.1.2 /24 from a host in 192.168.0.119 /24. Currently I have PAT set up in the Cisco Router where 192.168.0.0/24 represent the outside. Is there a route statement that could allow some 0 network traffic to reach my server?
Cisco G0/0 192.168.0.253
G0/1 multiple networks 192.168.1.0/24, 192.168.2.1/24
Does the router have a route to 192.168.0.0/24?
Can you ping from the router to 192.168.0.119/24?
On your sonic wall, is the interface to you host set to a lower security level than the one connected to cisco router or higher?
Does your sonic wall have a route to the 192.168.1.0/24 network?
Cordially,
Ronnie Wong
Edutainer, ITProTV
*if the post above has answered the question, please mark the topic as solved.
**All "answers" and responses are offered "as is" and my opinion. There is no implied support or guarantee by the ITProTV team.
Cisco IP route. Yes
I can ping the interface 192.168.0.253 from the host 192.168.0.119
But I can't ping from the cisco router to the host.
they belong to the same interface 192.168.0.0/24 network
I can't see the macaddress of this interface.
And no. The SonicWall has no route to the 192.168.1.0 network. So my question is... Will that be fix by allowing both routers to speak Ripv2 or OSPF?
can you do ping from the router to the .119 again...this time source it from the 192.168.1.0/24 network?
then ping from the sonic wall to 192.168.1.0/24 network..
If it's not working, then a route may be the issue. But I'm don't know much about the sonic wall to tell you if security rules are working against you or is it just a routing issue.
Cordially,
Ronnie Wong
Edutainer, ITProTV
*if the post above has answered the question, please mark the topic as solved.
**All "answers" and responses are offered "as is" and my opinion. There is no implied support or guarantee by the ITProTV team.
I can't ping any sub interface in the cisco from the sonic wall.. So the Sonic wall can't route trough it. I can ping the interface 192.168.0.253. and 192.168.0.119 can ping that same interface. But the cisco is not publishing the other interfaces. So I think is more of a Router protocol issue. Maybe with Ripv2 or OSPF the sonicwall and the cisco will learn each others route.
Cisco can ping both interfaces of the the sonicwall. But Sonic wall can ping 192.168.0.253 interface, but Can't ping int G0/1.10 or sub sequence.
I believe that you may have a routing issue...whether it's on the sonic wall or the router...you'll have to figure out where.
Cordially,
Ronnie Wong
Edutainer, ITProTV
*if the post above has answered the question, please mark the topic as solved.
**All "answers" and responses are offered "as is" and my opinion. There is no implied support or guarantee by the ITProTV team.
Is a Nat issue. They are been Nat it. Because from the internal I can ping the sonic wall interfaces
It can be unidirectional routing. Can you ping from .119 to the sonic firewall, then .119 to the inside .1.0/24?
I forgot that you're running nat as well. It could be NAT...easiest way to test this out is to take nat out of the picture
Cordially,
Ronnie Wong
Edutainer, ITProTV
*if the post above has answered the question, please mark the topic as solved.
**All "answers" and responses are offered "as is" and my opinion. There is no implied support or guarantee by the ITProTV team.
