mmm, maybe my post was a bit confusing. When I tried 'localhost ' on my own machine, I did that because my machine's name is not 'foo'. You better put the same IP-address in both scripts. If you put 'localhost' in the 'LocalHost' hash-key to build a new socket this socket will not be accessible from other machines on the network (under normal circumstances).

But even with LocalHost => 'localhost' in your script I'd at least expect you to see a listening port when you do a 'netstat -a'. Maybe it's better to do 'netstat -an' so your TCP and UDP portnumers are not translated to servicenames. Another way to see if you've got a listening TCP port is to use telnet to connect to this service. For instance to check a connection on TCP port 1800 on host 1.1.1.1:

telnet 1.1.1.1 1800
[download]

This will give you either a (useless) connection or a connection refused.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.