Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Question about NAT'ing

Status
Not open for further replies.

euni

MIS
Jan 5, 2005
4
0
0
US
Hello,

I'm new to networking.. can someone provide me some insights about NAT'ing between two private networks.

Device A (192.168.1.4) in Network 1 needs communicate with a device B (10.0.0.5) in Network 2 using a tcp port.

On the NAT router - device B (10.0.0.5) is NAT'd to (192.168.1.5) so that we can reference 10.0.0.5 as 192.168.1.5 internally. We need to use a RemoteAdmin type software to connect to 192.168.1.5.

Here's the config:

!
interface FastEthernet0/0
ip description WAN interface
ip address 10.1.5.1 255.255.255.248
ip nat outside
speed 100
full-duplex
!

ip route 10.0.0.0 255.0.0.0 10.1.5.2
ip nat outside source static 10.0.0.5 192.168.1.5
!

I can ping 192.168.1.5 from 192.168.1.4. However, I cannot run the Remote Admin software to 192.168.1.5.

The acls are not restricting it because tcp access has been allowed between both networks.

Any ideas on how I can do this... much appreciated!

EM
 
Let's see if I understand the config here. If not, please correct me.

Network-1
=========
Device-A 192.168.1.4

Network-2
=========
Device-B 192.168.1.5 with a NAT address of 10.0.0.5

If that's the case, then for Device-A to communicate with Device-B it has to talk to 10.0.0.5 instead of 192.168.1.5. Also, Netork-1 will need to provide a NAT address for Device-A to use or else Device-B will not be able to respond. Since each router will see 192.168.1.x on its own internal network, it will not send the packet outside. To communicate with the other network you will need a NAT address for each one.

Something like this:

Network-1 Network-2
192.168.1.0 /24 (router)[NAT IP]<--WAN-->[NAT IP](router)192.168.1.0 /24

For Device-A to talk to Device-B, Device-A needs to connect to 10.0.0.5. Network-1 and Network-2 can only communicate with each other's NAT addresses and not their internal addresses.

Since you can ping from 192.168.1.4 to 192.168.1.5 I'm thinking you have another device on Network-1 with 192.168.1.5 that's answering.

If you do a "ping -a 192.168.1.5" from a computer on network-1 do you get a host name back? That should say what is answering.

Hope this helps.

BierHunter
CNE, MCSE, CCNP
 
Network-1
=========
Device-A 192.168.1.4

Network-2
=========
Device-B 10.0.0.5 with a NAT address of 192.168.1.5.

I wanted to connect to 10.0.0.5 using the NAT address 192.168.1.5 from Network-1.

The packet wasn't traversing the WAN interface to be translated. It appears the problem was routing... i had to put in a ip route.. to fix the issue.

It's working now!

Thanks! appreciate ur comments!

EM


 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top