public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Marco atzeri <marco.atzeri@gmail.com>
To: cygwin-xfree@cygwin.com
Subject: Re: Unable to open socket for inet
Date: Thu, 04 Aug 2011 06:19:00 -0000	[thread overview]
Message-ID: <4E3A39EC.2020104@gmail.com> (raw)
In-Reply-To: <OF588CFB32.7C276118-ON852578E1.007BB5C2-852578E1.007C0DBA@comerica.com>

On 8/4/2011 12:35 AM, J T Halliley wrote:
> Just installed Cygwin/X on WIndows XP Pro, Version 2002, SP 3.
> When I invoke startxwin, here's what I get:
>
> ----------------------
> bash>  startxwin
>
> Welcome to the XWin X Server
> Vendor: The Cygwin/X Project
> Release: 1.10.3.0
> OS: Windows XP Service Pack 3 [Windows NT 5.1 build 2600] (Win32)
> Package: version 1.10.3-1 built 2011-07-19
>
> XWin was started with the following command line:
>
> X :0 -multiwindow
>
> _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
> _XSERVTransOpen: transport open failed for inet6/GP3JDP1-E6410:0
> _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6
> _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet
> _XSERVTransOpen: transport open failed for inet/GP3JDP1-E6410:0
> _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet
> _XSERVTransSocketOpenCOTSServer: Unable to open socket for local
> _XSERVTransOpen: transport open failed for local/GP3JDP1-E6410:0
> _XSERVTransMakeAllCOTSServerListeners: failed to open listener for local
>
> Fatal server error:
> Cannot establish any listening sockets - Make sure an X server isn't
> already running
> winDeinitMultiWindowWM - Noting shutdown in progress
> ----------------------
>
> It seems as though there's a general networking issue:
>
> ----------------------
> bash>  ping 127.0.0.1
> icmp: unknown protocol
> ----------------------
>
> but using Windows ping from a DOS prompt works fine:
>
> ----------------------
> Microsoft Windows XP [Version 5.1.2600]
> (C) Copyright 1985-2001 Microsoft Corp.
>
> C:\>ping 127.0.0.1
>
> Pinging 127.0.0.1 with 32 bytes of data:
>
> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
>
> Ping statistics for 127.0.0.1:
>      Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
> Approximate round trip times in milli-seconds:
>      Minimum = 0ms, Maximum = 0ms, Average = 0ms
> Control-C
> ^C
> C:\>
> ----------------------
>
> I am in the Administrators group, so raw sockets should work.  We do run
> McAfee, so that could be an issue.
>
> Any ideas?  Both for XWin and for ping?  Are they related?
>
> Thanks,
> Tom

check using cygwin ping, if this fail than something is blocking
the communication.

The windows ping has more "authorization" so it could
misses the problem.

regards
Marco


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/


  reply	other threads:[~2011-08-04  6:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-03 22:35 J T Halliley
2011-08-04  6:19 ` Marco atzeri [this message]
2011-08-04 20:18 J T Halliley
2011-08-04 20:59 J T Halliley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E3A39EC.2020104@gmail.com \
    --to=marco.atzeri@gmail.com \
    --cc=cygwin-xfree@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).