Open GoogleCodeExporter opened 9 years ago
cmd+ping to ip-adresses works better, so it might be DNS related (then maybe
this is a duplicate of issue #200). However programs (for example Firefox,
FileZilla) are still experiencing trouble even when entering ip-addresses
instead of URLs.
Original comment by helmerde...@gmail.com
on 29 Apr 2011 at 4:27
Why is nobody struggeling with this problem then? I can't find anything about
this problem, but you also experience this ? Interesting.
Original comment by links4...@gmail.com
on 29 Apr 2011 at 5:35
Yes I am and I'm amazed this is even possible; why should it matter where an
executable is located, to allow it to have a proper network connection?
Original comment by helmerde...@gmail.com
on 30 Apr 2011 at 8:41
I also was confused by this. And I found a clue AT
http://social.msdn.microsoft.com/Forums/en-US/wsk/thread/3076a9cd-57a0-418d-8de1
-07adc3b486bb. That means programs in the dokan volume got a 10022 when create
a socket.
Call Stack is the same:
Here's the "call stack"
socket()
WSPSocket()
SockSocket()
(...seems that NtCreateFile "/device/afd/endpoint" got an error )
Original comment by Whx...@gmail.com
on 13 Jun 2011 at 1:08
I found somewhat of a workaround.
1) You have internet access via IP4 ip addresses, just not via DNS.
2) if you map your mounted drive (my mount is n:\ removable storage) to say
Y:\, cmd into Y:\ and run the Ping.exe (after you have all the other necessary
files that ping needs in it) it will run as you expect.
Original comment by liverm...@gmail.com
on 19 Sep 2011 at 4:39
Did anybody found any solution for this issue?
Can't establish a socket connection from application running on a Dokan mounted
VFS.
Original comment by eugenj...@gmail.com
on 4 Nov 2011 at 2:21
I'm having the same issue with Dokan 0.60 using Windows 8.
Original comment by jozsef.k...@gmail.com
on 24 Nov 2012 at 1:13
Original issue reported on code.google.com by
links4...@gmail.com
on 27 Apr 2011 at 11:42