<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: socket program to communicate between WindowsNT and Unix in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/socket-program-to-communicate-between-windowsnt-and-unix/m-p/2515230#M596032</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I presume your perl program in the Unix side is the server, just do&lt;BR /&gt;&lt;BR /&gt;netstat -a|grep &lt;SERVER_LISTENING_PORT&gt;&lt;BR /&gt;&lt;BR /&gt;is the port under LISTENing state?&lt;BR /&gt;&lt;BR /&gt;~Philip&lt;/SERVER_LISTENING_PORT&gt;</description>
    <pubDate>Tue, 10 Apr 2001 00:03:08 GMT</pubDate>
    <dc:creator>Philip Chan_1</dc:creator>
    <dc:date>2001-04-10T00:03:08Z</dc:date>
    <item>
      <title>socket program to communicate between WindowsNT and Unix</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/socket-program-to-communicate-between-windowsnt-and-unix/m-p/2515228#M596030</link>
      <description>Hi.&lt;BR /&gt;&lt;BR /&gt;(I apologize for my english)&lt;BR /&gt;&lt;BR /&gt;I have developed a socket program : the client (developed in PERL) is on a unix station and the client (developed in C) is on a windows station. &lt;BR /&gt;&lt;BR /&gt;It doesn't work. &lt;BR /&gt;While the server has already been launch, when the client is launched (with the ip address of the server and on the same port as the server) the connect api fails (connection failed). &lt;BR /&gt;&lt;BR /&gt;I don't understand. I haven't this problem when I put the server program on a windows station.&lt;BR /&gt;&lt;BR /&gt;Do you know if their is any particular thing to check, or to do for this client/server application to go on??&lt;BR /&gt;&lt;BR /&gt;PS: the 2 stations can ping each other&lt;BR /&gt;&lt;BR /&gt;Please Help Me. In advance, Thank you very much.&lt;BR /&gt;&lt;BR /&gt;Best regards, Sylvie.&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 09 Apr 2001 17:30:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/socket-program-to-communicate-between-windowsnt-and-unix/m-p/2515228#M596030</guid>
      <dc:creator>borges</dc:creator>
      <dc:date>2001-04-09T17:30:39Z</dc:date>
    </item>
    <item>
      <title>Re: socket program to communicate between WindowsNT and Unix</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/socket-program-to-communicate-between-windowsnt-and-unix/m-p/2515229#M596031</link>
      <description>I do this sort of thing quite often and have no problems. One thing that does occurs to me is that HP's delivered perl is quite old; you should probably get a newer version (5.6) from&lt;BR /&gt;&lt;A href="http://www.perl.com/CPAN." target="_blank"&gt;www.perl.com/CPAN.&lt;/A&gt; I would then get the two&lt;BR /&gt;machines talking through perl using the simple examples listed in the O'Reilly book 'Advanced Perl Programming'. You should then be able to debug any network/OS problems much faster than in c.</description>
      <pubDate>Mon, 09 Apr 2001 20:46:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/socket-program-to-communicate-between-windowsnt-and-unix/m-p/2515229#M596031</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2001-04-09T20:46:09Z</dc:date>
    </item>
    <item>
      <title>Re: socket program to communicate between WindowsNT and Unix</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/socket-program-to-communicate-between-windowsnt-and-unix/m-p/2515230#M596032</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I presume your perl program in the Unix side is the server, just do&lt;BR /&gt;&lt;BR /&gt;netstat -a|grep &lt;SERVER_LISTENING_PORT&gt;&lt;BR /&gt;&lt;BR /&gt;is the port under LISTENing state?&lt;BR /&gt;&lt;BR /&gt;~Philip&lt;/SERVER_LISTENING_PORT&gt;</description>
      <pubDate>Tue, 10 Apr 2001 00:03:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/socket-program-to-communicate-between-windowsnt-and-unix/m-p/2515230#M596032</guid>
      <dc:creator>Philip Chan_1</dc:creator>
      <dc:date>2001-04-10T00:03:08Z</dc:date>
    </item>
    <item>
      <title>Re: socket program to communicate between WindowsNT and Unix</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/socket-program-to-communicate-between-windowsnt-and-unix/m-p/2515231#M596033</link>
      <description>A. Clay Stephenson, can you please send me a simple example of the O'Reilly 'advanced perl programming' in order to i can test that.&lt;BR /&gt;&lt;BR /&gt;My email : sylvie_borges@yahoo.fr&lt;BR /&gt;&lt;BR /&gt;Thanks.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 10 Apr 2001 07:04:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/socket-program-to-communicate-between-windowsnt-and-unix/m-p/2515231#M596033</guid>
      <dc:creator>borges</dc:creator>
      <dc:date>2001-04-10T07:04:53Z</dc:date>
    </item>
    <item>
      <title>Re: socket program to communicate between WindowsNT and Unix</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/socket-program-to-communicate-between-windowsnt-and-unix/m-p/2515232#M596034</link>
      <description>Hi.&lt;BR /&gt;&lt;BR /&gt;Thanks to all for your help.&lt;BR /&gt;&lt;BR /&gt;I typed the command 'netstat...', and my is LISTENing on the port.&lt;BR /&gt;&lt;BR /&gt;I typed the command : "netstat -a" on my NT station and how was surprised to see that line:&lt;BR /&gt;&lt;BR /&gt;Proto | Local Address | Foreign Address |State &lt;BR /&gt;TCP  | ntPC:port1  | unixPC:port2 | ESTABLISHED&lt;BR /&gt;&lt;BR /&gt;Does it mean that the connection was established? What happens?&lt;BR /&gt;&lt;BR /&gt;PS: Both port1 and port2 are not the port that I have indicated. &lt;BR /&gt;&lt;BR /&gt;Thanks for your help.&lt;BR /&gt;Sylvie.</description>
      <pubDate>Tue, 10 Apr 2001 07:11:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/socket-program-to-communicate-between-windowsnt-and-unix/m-p/2515232#M596034</guid>
      <dc:creator>borges</dc:creator>
      <dc:date>2001-04-10T07:11:34Z</dc:date>
    </item>
    <item>
      <title>Re: socket program to communicate between WindowsNT and Unix</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/socket-program-to-communicate-between-windowsnt-and-unix/m-p/2515233#M596035</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Note the user privileges you are using to run the client and server daemons. Note that if you are non-superuser, you are not allowed to use a port number &amp;lt; 1024.&lt;BR /&gt;&lt;BR /&gt;Hope this helps. Regards.&lt;BR /&gt;&lt;BR /&gt;Steven Sim Kok Leong&lt;BR /&gt;Brainbench MVP for Unix Admin&lt;BR /&gt;&lt;A href="http://www.brainbench.com" target="_blank"&gt;http://www.brainbench.com&lt;/A&gt;</description>
      <pubDate>Tue, 10 Apr 2001 07:23:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/socket-program-to-communicate-between-windowsnt-and-unix/m-p/2515233#M596035</guid>
      <dc:creator>Steven Sim Kok Leong</dc:creator>
      <dc:date>2001-04-10T07:23:21Z</dc:date>
    </item>
    <item>
      <title>Re: socket program to communicate between WindowsNT and Unix</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/socket-program-to-communicate-between-windowsnt-and-unix/m-p/2515234#M596036</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I guessed the connection you saw was just some other connection services, because the server port number is static.  For example if your server is set to listen to port 2345, then "netstat -a|grep EST" should shown that number as well.&lt;BR /&gt;&lt;BR /&gt;First thing that you should check is whether the server process is really listening, so just run the following command at the server side&lt;BR /&gt;&lt;BR /&gt;netstat -a | grep LISTEN&lt;BR /&gt;&lt;BR /&gt;is your server listening port number on the list?&lt;BR /&gt;&lt;BR /&gt;Rgds,&lt;BR /&gt;Philip</description>
      <pubDate>Tue, 10 Apr 2001 07:28:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/socket-program-to-communicate-between-windowsnt-and-unix/m-p/2515234#M596036</guid>
      <dc:creator>Philip Chan_1</dc:creator>
      <dc:date>2001-04-10T07:28:15Z</dc:date>
    </item>
    <item>
      <title>Re: socket program to communicate between WindowsNT and Unix</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/socket-program-to-communicate-between-windowsnt-and-unix/m-p/2515235#M596037</link>
      <description>Thanks to all.&lt;BR /&gt;&lt;BR /&gt;I'm not superuser and i'm using a port over 44000.&lt;BR /&gt;&lt;BR /&gt;When i do 'netstat -a|grep port' on my unix station, i saw my server listening on the port i've specified to him. &lt;BR /&gt;But, it is when i do 'netstat -a' on my NT pc that i've seen different ports on communication with my NT pc and my unix pc.&lt;BR /&gt;&lt;BR /&gt;It proofs that there i communication; unless, my netstat wouldn't have the ip my unix station. Whereas, the connection failed. &lt;BR /&gt;&lt;BR /&gt;Thanks for your help.&lt;BR /&gt;Sylvie.</description>
      <pubDate>Tue, 10 Apr 2001 07:37:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/socket-program-to-communicate-between-windowsnt-and-unix/m-p/2515235#M596037</guid>
      <dc:creator>borges</dc:creator>
      <dc:date>2001-04-10T07:37:16Z</dc:date>
    </item>
    <item>
      <title>Re: socket program to communicate between WindowsNT and Unix</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/socket-program-to-communicate-between-windowsnt-and-unix/m-p/2515236#M596038</link>
      <description>Hi!&lt;BR /&gt;&lt;BR /&gt;Instead of having a PERL Unix server communicating with a C NT client; I have now a PERL Unix server communicating with a PERL NT client.&lt;BR /&gt;&lt;BR /&gt;IT WORKS!!!!&lt;BR /&gt;&lt;BR /&gt;My question : what's the problem the C client? Is it a problem of incompatibility??&lt;BR /&gt;&lt;BR /&gt;Thanks for your help.&lt;BR /&gt;Sylvie.</description>
      <pubDate>Tue, 10 Apr 2001 12:41:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/socket-program-to-communicate-between-windowsnt-and-unix/m-p/2515236#M596038</guid>
      <dc:creator>borges</dc:creator>
      <dc:date>2001-04-10T12:41:41Z</dc:date>
    </item>
    <item>
      <title>Re: socket program to communicate between WindowsNT and Unix</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/socket-program-to-communicate-between-windowsnt-and-unix/m-p/2515237#M596039</link>
      <description>Sylvie,&lt;BR /&gt;Attached is the example TCP socket client/server perl code that you requested.&lt;BR /&gt;You can also find many examples at&lt;BR /&gt;ftp.oreilly.com/published/oreilly/nutshell&lt;BR /&gt;via anonymous ftp.&lt;BR /&gt;</description>
      <pubDate>Tue, 10 Apr 2001 19:49:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/socket-program-to-communicate-between-windowsnt-and-unix/m-p/2515237#M596039</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2001-04-10T19:49:04Z</dc:date>
    </item>
  </channel>
</rss>

