Today I spent the whole day investigating why I have so many problems with WebDAV.
My Server is running Windows 2008 R2 with IIS7.5.
I created a self signed certificate and added it to the "Default Web Site". I enabled Windows Authentication and installed the WebDAV Extension.
I enabled Locking WebDAV Settings as you see here:
http://www.abload.de/img/webdavydkea.png
I then created a folder called Shares on C:\ and changed added writting permissions for the domain users.
At the end I created the Virtual Directory and set the "Authorization Rules" and the "WebDav Authorization Rules".
At the end I force the usage of SSL with the previously self signed certificate.
Now I try to connect with MAC OS X 10.7 and MAC OS X 10.6 and both mount it readonly.
If I try to mount it in Windows I get the following error message:
The mapped network drive could not be created because the following error has occurred:
A device attached to the system is not functioning.
More details if I try to mount it by using the command line:
System error 1244 has occurred.
The operation being requested was not performed because the user has not been authenticated.
If I now disable the SSL support I can mount it in Windows too including write support. MAC OS X still does only mount it as read only.
Altogether I have the following problems:
Why does MAC OS X mount the WebDAV directory as readonly even so I enabled locking support?
Why does Windows not work if I try to use SSL with the self signed certificate?
I have a similar setup, and just experienced the same "cannot connect from Windows 7" problem.
I found that I can connect from a Win XP machine. On connecting, a popup asks me if I want to trust the self-signed cert -> I accept -> it connects well.
This made me suspect that the Win 7 problem is with the cert (with not showing a popup to let me manually accept the self-signed cert). The solution to make it work is:
Either import the self-signed cert in Win 7 / IE9 into the "Trusted root CA"
cert store.
Or buy a cert that is signed by a known cert authority.
Related
I need to trust an SSL certificate on my windows machine, however, the ways I've tried don't work properly. My problem is the CommonName on the certificate is the name of my machine, not the issuer. Invalidating the access by browser;
My machine:
Device name DESKTOP-B3XXXXX
Processor Intel(R) Core(TM) i7-10750H CPU#2.60GHz 2.59GHz
Installed RAM 16,0 GB (15,8 GB usable)
System type 64-bit operating system, x64-based processor
Edition Windows 10 Pro
Version 22H2
Installed on 24/06/2022
OS build 19045.2486
Experience Windows Feature Experience Pack 120.2212.4190.0
About the certificate:
Version: V3
Signature Algorithm: sha256rsa
issuer: local.example.dev //changed to 'example' here on stackoverflow
Public Key: RSA (2048 Bits)
Subject Alt. Name: DNS Name=local.example.dev
Was generated by the team. My teammates was able to install it on their mac, and the other dev who is using windows, was able to trust on the same .crt;
The methods that I tried to install:
Double click on .crt file and Follow the wizard. In this method, I tried with the following options: Current User/Local Machine and Automatically select the certificate store ... and `Place all certificates in the following store: Trusted Root Certification Authorities;
Open mmc.exe program. Click on File>Add/Remove Snap-In, then Certificates>Add>Computer/My User Account. Finally, right click on Trusted Root Certification Authorities and selected All Tasks/Import...;
Removed all installed certificates, and add again by mmc.exe in method 2;
But still getting the wrong certificate in any browser. I tested chrome, firefox and edge; Inspecting the certificate used by them, show a certificate with CommomName with my computer name DESKTOP-B3XXXXX.
Is it possible with current version of VisualStudio and XCode 11.5 can we access the MacBuild machine over the internet?
I have configured Mac machine with remote login enabled, setup noip, setup SSH port forwarding 22 on router and below are the results.
Initially, Pair to Mac has got the fingerprint but after providing the username and password it failed to authenticate as in picture 2.
any ideas ? or some one already using Pair to Mac over the internet.
I have a small LAN with:
A Synology server where I have installed a Comodo Wildcard
Certificate for mydomain.com.
Three wired clients running Windows 8.1 Pro and Windows 10 Pro, and
one wireless client running Mac OSX.
This LAN is connected via an IPSEC VPN to another remote LAN with
more clients.
My issue:
When I try to connect to my Synology box using https:// from a LOCAL client, using Internet Explorer 11 or Google Chrome, everything works fine. The browsers see that the website has a valid SSL Certificate and I get no errors or warnings of any kind.
However, when I use Firefox, the certificate doesn't work at all, with the following symptoms:
For THREE Wired Clients on LAN using Windows 8.1 Pro/Windows 10 Pro and Firefox:
"The Connection is Untrusted" If I click on the little Globe next to the Address bar it says "The website does not supply identity information. Your connection to this website is not encrypted."
For Wireless Client on LAN using OSX and Firefox:
EVERYTHING WORKS FINE. If I click the lock next to the address bar in Firefox it correctly shows that the website is verified by COMODO.
For Wired Client on another LAN running Windows 7 and connecting via VPN and Firefox:
EVERYTHING WORKS FINE.
So in summary: I can connect via HTTPS using Internet Explorer or Chrome from ANYWHERE with no problems. I only have problems with FIREFOX on SPECIFIC MACHINES. It is like they aren't seeing the certificate AT ALL. What is something I could look at here?
Note that on the Windows 10 Pro machine, it is a BRAND NEW FRESH install. There is nothing else on the machine except browsers. This is a brand new fresh install of the latest Windows with the latest Firefox.
I'm going to leave this here in case someone else has the same or similar problem:
I had installed my private key and certificate on the Synology server, but had failed to include the Intermediate Certificates in the package.
Apparently, Firefox maintains a separate Certificate Store from IE and Chrome, which already come with the necessary Comodo Intermediates.
On some machines, Firefox already had the necessary Intermediates, from other sites that had provided them, but on these other machines where Firefox was rarely used, it was basically a blank slate. After installing Intermediates Certificates on the Synology server, everything was fine.
I'm facing an issue with self-signed certificate in Windows Phone 8 app. I have installed the certificate (.p7b) manually and it works fine when I browse through the site in IEMobile.
But when I visit the same, using the WebBrowser control in my hybrid app, The certificate error still shows and can't be ignored, even after tapping Continue. Isn't the Certificate installed System-wide or is it just for IE?
I have referred many links regarding this but in vain. Any help would be jighly appreciated. Thank you.
I had the same issue, and it turned out to be a hostname mismatch between what the certificate contained and the address I was using to connect to the server. If those match, and you install the P7B file on the Windows Phone device, then you should no longer see certificate warnings.
For the full details of my issues and solution, see this thread on MSDN.
We are developing a WP7 application which is connected to a server using OAuth. It's a low budget project. So, we are only using self signed certificates even on the production server. That worked fine for the android client.
Is there a chance to work with
unsigned certificates on WP7 also?
Is there a way to make the app work
out of the box with this kind of
certs? So, that the user doesn't
need to install the cert manually?
We failed to install the cert on the emulator. Did you have the same kind of problem? How did you solve it?
Does Microsoft allow apps with this kind of certs in their market
How to: Set up an Authenticated Web Service for Windows Phone on MSDN describes how to go about using authenticated services. According to SSL Root Certificates for Windows Phone, the only trusted certificate authorities are:
AOL (USA)
Comodo (USA)
DigiCert (USA)
Entrust (Canada)
GlobalSign (UK)
GoDaddy (USA)
Keynectis (France)
QuoVadis (Bermuda)
So I'd say that a self-signed certificate won't work.
Did you try using the emulator's browser to navigate to the .CER file that represents your self-signed root? That works on the physical hardware, and seems like it might work on the emulator as well. But you absolutely shouldn't expect to ship like this; a Go-Daddy cert is like $15/year.