Quote:
deccan said:
Hmm, telco says the package includes a NAT secure capable modem / router whatever that means....
|
What that means is you'll have to provide a "translation" for the router to pass traffic to your FTP server.
For instance, within our network we have a web server with 3 separate web sites running on it. So I want to have one of the web sites available to outside folks. I have a translation config with one line that looks like this:
ip nat inside source static tcp 192.168.1.13 1000 216.195.222.6 80 extendable
Now this line is specific to this Cisco router but the theory is the same. See, I have our DNS entry for our web site pointing to IP address 216.195.222.3 (port 80 is assumed for WWW protocol). What this code does is say that any requests to our web server need to be passed inside to the address 192.168.1.13:1000 (that's port 1000 'cause we have multiple instances if IIS running on that box).
What you should be able to do (if the router is NAT compatible) is something similar. You WILL have to have a static IP address for the CPU inside your network for this to function properly. Check your router documentation for NAT stuff.
Yeah, those tech support folks probably will not help you with this. They rarely ever go beyond the basic setup. In fact, if you ask, they'll probably tell you to hook a PC with DHCP up to it. If that can surf the web, then their responsibility ends there.
Does that help any?