Re^4: server with IO::Socket::INET

Can not connect to client: 192.168.1.67 SysErr: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connec ted host has failed to respond.

Comment on Re^4: server with IO::Socket::INET

Replies are listed 'Best First'.
Re^5: server with IO::Socket::INET by BrowserUk (Patriarch) on Mar 11, 2012 at 21:09 UTC
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?	[reply] [d/l]
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]
Re^7: server with IO::Socket::INET by Rudolf (Pilgrim) on Mar 11, 2012 at 21:26 UTC
ohh, sorry I missunderstood you, I pinged on the server machine. I pinged the address from client machine and it timed out.	[reply]
Re^8: server with IO::Socket::INET by BrowserUk (Patriarch) on Mar 11, 2012 at 21:32 UTC
Re^9: server with IO::Socket::INET by Rudolf (Pilgrim) on Mar 11, 2012 at 21:39 UTC