Re: not listening

In article <4g5oj6F1lbblrU2@xxxxxxxxxxxxxx>,
Sebastian Gottschalk <seppi@xxxxxxxxx> wrote:
Walter Roberson wrote:

Nothing listening for *new* connections on any port,
but you sure have something listening for returning packets.

Now would you please read RFC 793 and maybe also the POSIX standard to
clearly understand what "listening" means in terms of TCP/IP communication?

We have no reason to expect that the original poster is using a POSIX
compatible sockets -- for example it would be extremely reasonable to
suppose that the original poster might be using Microsoft Windows XP.

http://support.microsoft.com/kb/308259

The Portable Operating System for UNIX (POSIX) subsystem is not
included with Windows XP or with Windows Server 2003. The POSIX
subsystem has been replaced withe a more UNIX-like environment that
is named Windows Services For UNIX. Windows Services for UNIX is
a superset of the original POSIX subsystem and provides greater
functionality for UNIX programs. WIndows Services for UNIX requires
Windows XP Professional Service Pack 1 (SP1) or later.

If you follow this further into Microsoft's Windows Services For UNIX
(SFU), you find that you only get IEEE 1003.1 compatibility promises
for programs developed with the Internix SDK; similarily the earlier
Windows POSIX subsystem only applied to programs specifically built
for that subsystem:

http://support.microsoft.com/default.aspx?scid=kb;en-us;101270

There is little to gain by disabling the POSIX subsystem in
Windows NT because POSIX is only started once a POSIX-based
application is started.

The SFU download page indicates,

Note: The product will not install on Windows 9x or Windows XP
Home Edition.


Now would you please read RFC 793 and maybe also the POSIX standard to
clearly understand what "listening" means in terms of TCP/IP communication?

If you recheck you will find that the original poster did not
specify TCP/IP.
.

Relevant Pages

  • Re: system calls
    ... If you are writing a WIndows App, you are expected to program it using the Windows ... If you are writing a POSIX app, use the POSIX API, and be prepared for whatever it ... to a Unix API, should I write to Gnome, or KDE, or what? ...
    (microsoft.public.vc.mfc)
  • Re: YADQ (Yet another dumb question)
    ... Cygwin has nothing to do with UNIX at all. ... _application_ layer for Microsoft Windows. ... You see, you have POSIX ...
    (comp.os.cpm)
  • Re: [OT] Re: Hello and *++* ?
    ... recommending several unix and POSIX possibilities is that MS would ... nonstandards. ... as he is on Windows. ...
    (comp.lang.c)
  • Re: popen5: New POSIX process module
    ... UNIX (POSIX) only. ... The API is designed to work with Windows as well, ... information about why Windows support is missing, ...
    (comp.lang.python)
  • Re: linux vx windows kernel
    ... Services for Unix provides a much more complete posix subsystem for people who use it. ... This doesn't change much from the kernel point of view, except that NT provides a sort of "generic" API for system calls, while Linux directly implement many Posix calls as system calls. ...
    (microsoft.public.win32.programmer.kernel)