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

Routing public ip to internal ip using Cisco E1000

Hello All,
I'm using a Cisco Linksys E1000 router. everything works fine.
I'm setting up an FTP server on the inside of the E1000 router with an internal ip 192.168.1.50
ISP gave me a public ip 184.186.x.x
how can I route the public ip 184.186.x.x to 192.168.1.50 (which is my ftp server on the inside of the router)?
I went into Setup/Advanced Routing, but not sure what to fill in. please screenshot attached.
Thanks

Routing1.png
0
Paul-AC
Asked:
Paul-AC
  • 4
  • 3
3 Solutions
 
acl-puzzCommented:
0
 
Hypercat (Deb)Commented:
This is not a routing issue.  What you want to do is go to the "Applications and Gaming" tab and there you will see something called (I think) "port forwarding." You want to forward TCP port 21 to the internal IP address of your server, i.e., 192.168.1.50.
0
 
Paul-ACAuthor Commented:
May be I didn't give all the info.
If I don't enter this public ip 184.186.x.x into somewhere in my router, then how does anyone see it on the internet? Because this is not what I use on the outside of my router.
This is a COX cable modem, this is the way I hook it up now:
cable goes into the cable modem. The other side of the modem goes into my E1000 router. and I've configured 192.169.1.1 for the gateway.
Whatismyip is not 184.186.x.x (which my ISP gave me, but some other ip). Do I have to assign the ip 184.186.x.x to my cable modem?

I think what I need is NAT routing, am I correct? if so, then how do I set it up?

Thanks
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
Hypercat (Deb)Commented:
What is happening here is that your cable modem has a router on it which is doing the NAT portion of the routing, and may also (probably is) firewalled.  In that case, you'd have to gain access to the router on the cable modem itself and redirect the traffic from there.  Or, alternatively, you could set the cable modem in "bridge" mode, which means that it will stop NATing the incoming traffic.  Then, you could assign your public IP address to your Linksys router, let it do the NAT portion and also the port forwarding as described in my previous post.
0
 
Paul-ACAuthor Commented:
Thanks hypercat,
The Cable Modem is in "bridge" mode, the public ip address has been assigned to the Cisco/Linksys router, and port 21 has been forwarded, but it still not working.
I used FireFTP and it said, unable to connect....



PortForwarding.png
0
 
Hypercat (Deb)Commented:
According to your OP, you are using 192.168.1.50 as the IP address of your internal FTP server, but you have the forwarding set up to 192.168.1.41. If your internal FTP server is .50, then you have to forward to port to .50.

Also, what type of FTP server software are you running internally? Is it a Windows server, and what version of Windows? Have you tried connecting from the Windows client command line just to see if it will work?
0
 
Paul-ACAuthor Commented:
it is working.
0
 
Paul-ACAuthor Commented:
Thanks so much.
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

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