From: "Andy O'Shaughnessy" <andrewjoshaughnessy@gmail.com>
To: cygwin-developers@cygwin.com
Subject: NFS share - NtOpenFile() failed, c00000be
Date: Thu, 29 Oct 2015 11:47:00 -0000 [thread overview]
Message-ID: <CABK-G+TZaO+9Q7ZYFPgBJ-XEMfE_VdinjXNPo3L78KLMNnH46w@mail.gmail.com> (raw)
I am able to mount an NFS share from Linux but when I use Cygwin I get
a stranger error:
$ mount //<server>/<share> /tmp/test1
$ ls -lrt /tmp
ls: cannot access /tmp/test1: No such file or directory
total 0
d????????? ? ? ? ? ? test1
But when I run the following I get :
$ /usr/lib/csih/getVolInfo /tmp/test1
NtOpenFile(\??\UNC\<server>\<share>) failed, c00000be
Note : 0xC00000BE = STATUS_BAD_NETWORK_PATH
The mount happened but not properly.
It might be linked to Windows McAfee Firewalls.
I would guess this mailing list will readily know what is wrong
next reply other threads:[~2015-10-29 11:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 11:47 Andy O'Shaughnessy [this message]
2015-10-29 12:09 ` Ryan Johnson
2015-10-29 15:12 ` Corinna Vinschen
2015-10-29 15:55 ` Fwd: " Andy O'Shaughnessy
2017-09-28 11:27 ` Andy O'Shaughnessy
2017-09-28 13:08 ` cyg Simple
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=CABK-G+TZaO+9Q7ZYFPgBJ-XEMfE_VdinjXNPo3L78KLMNnH46w@mail.gmail.com \
--to=andrewjoshaughnessy@gmail.com \
--cc=cygwin-developers@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).