in reply to Re^4: server with IO::Socket::INET
in thread server with IO::Socket::INET

What do you get if you type ping 192.168.1.67 into a command line on your client machine?

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.

The start of some sanity?

Replies are listed 'Best First'.
Re^6: server with IO::Socket::INET
by Rudolf (Pilgrim) on Mar 11, 2012 at 21:20 UTC
    that's actually the IP of the machine, and when I ping it it from the client machine it sends 32 bytes and 4/4(100%) reply back 0ms Ave
[reply]

      ohh, sorry I missunderstood you, I pinged on the server machine. I pinged the address from client machine and it timed out.

[reply]

        So, the server isn't visible from the client. Either they aren't on the same subnet, or the server has its ports cloaked by a firewall.

        With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
        Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
        "Science is about questioning the status quo. Questioning authority".
        In the absence of evidence, opinion is indistinguishable from prejudice.

        The start of some sanity?
[reply]

In Section Seekers of Perl Wisdom