Made a small change and now your client received from server.

You have a line: 
$answer = <$soc>;

[download]
And it should be: 
$answre = <$socket>;

[download]

Use 'use strict' next time, and you can spot this problem yourself;-)

Update:

Now I looked at your server side code, and found that, after it communicated with the first client, it quickly sink into a dead loop, and the rest of your code is not reachable (see my comment made in the code): 
while ($new_sock = $listener->accept()) 
#now you just stuck in this loop
{
    while (defined ($buf = <$new_sock>))
    #where do you reply to your client, start from the second client? 
+ 
    {
        print FILE "$buf";                         
    }
    close FILE;
}

[download]

In reply to Re: Two way socket by pg
in thread Two way socket by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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! —
  • 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:
    & &amp;
    < &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.