in reply to net::Telnet to connect public ip

You aren't checking for errors so you don't know if you are successfully connecting.

I am guessing that the client is inside the firewall and has its own private IP address. If that is the case, then it is quite possible that you can't connect to the public IP address. This happens most often when the router is using NAT to map the public IP address to the private IP address. From inside, this mapping does not happen.

Replies are listed 'Best First'.
Re^2: net::Telnet to connect public ip
by sris (Initiate) on Jun 24, 2004 at 04:04 UTC
    Hi Iburrell

    Thank You very much for your reply, your guessing is exactly right

    that the client is in private IP only where i am trying to connect to

    public IP to access some files

    actually there are some files in the Unix system which is given public IP

    to that, now i want to access those files from the Unix system to client

    system (Window O/S is installed in the client system and given Private IP)

    how can i able to solve this kindly help me

    Thanks in advance
[reply]
      How is your network setup that the server only has a public IP address? That implies that you aren't using NAT, or the server is in a DMZ without NAT. In either case, the network should be configured to allow access from private IP addresses to the DMZ public IP addresses.

      One common solution is to use a split-horizon DNS. The internal DNS returns private IP address, and has record for purely internal hosts. The public DNS reutrns public IP addresses.

      Another solution for some protocols is to use a proxy. The proxy would be setup outside (or on the firewall) and connect back inside. This only works for some protocols (HTTP), and raises security issues about securing the proxy and the services from untrusted outside usage.

[reply]

In Section Seekers of Perl Wisdom