In Azure, I set up the Windows Server 2012 R2 FTP service properly and have no problems connecting via the standard Windows 7 FTP client when the server-side setting is "Allow SSL". My endpoints are properly defined, etc.
However, when I change the setting to "Require SSL", I am unable to connect. I set endpoints for FTP SSL ports 989 and 990. I have a certificate installed properly (bound to HTTPS port 443). I selected the same certificate for use with FTP.
Note: When the server is set as "Allow SSL", Filezilla connects using TLS successfully. Neither FileZilla nor the Windows 7 FTP client can connect when the server is set as "Require SSL".
I want to require SSL connections when using the Windows 7 FTP client. I do not care about FileZilla (that was just for testing). I cannot find any walk-throughs or examples where the author uses the "Require SSL" setting on an Azure machine.
Suggestions to fix?
Related
I am setting up EAP-TLS authentication using the manual https://networklessons.com/wireless/peap-and-eap-tls-on-server-2008-and-cisco-wlc/.
My server and client details are below:
Server: NPS 2008
Client: Linux
I generated the server certificates on the NPS server as well as the CA cert. I imported the CA cert to the Linux server but after this the manual I am using tells me to log into the IP of server using a web browser and request client certificate from there.This is the part I am stuck in.
I tried curl -k https://< ip of server > but this returned an error:
curl:(7) couldn't connect to host error.
Any help will be appreciated.
Have you checked:
httpd is running on the server
httpd is listening for TCP on port 443 (I like ProcessMonitor from MS for this)
https://localhost/ access from the NPS server (to itself) works as expected
firewall on the server is shut down or is allowing https access on the correct
network interface
https://ip_address/ access from the NPS server (to
itself) works as expected
https access works from another client on
the same LAN segment
I have a Win 2012 server with IIS 8 running on that. Also installed Management Service with Remote Access allowed.
Another admin-user account is used to set up few default websites and now when I login to the same server using my admin-user account, I cannot see anything in the IIS.
I have tried connecting to server as localhost and with computer name as well but not allowing me to connect.
Any help on this would be great.
Found the issue -
There is a firewall implemented for the domain users to access. And when I tried to login as an Admin who is not permitted by firewall, I am just able to access the machine and internally my IIS component is not able to connect with the localhost or local server.
I have a web role which is configured for 2 endpoints, one http, one https 443:
Then I have 3 certs (one is the main and 2 are CA). I have uploaded all of these and also checked thumbprints are correct.
But when I deploy, the http site works fine but the https site does not. Fiddler shows:
Authentication failed because the remote party has closed the
transport stream
Any ideas?
Note: Also worth noting this https works fine when on local machine through Visual Studio and only reports the certificate error, which is expected.
First, open the portal and enable RDP to the instances, then connect to the role instance, open IIS, and verify the HTTPS binding is configured properly. Try accessing the site using https locally from the server and verify it works.
Report with the findings.
I understand pretty well that Windows RDP works on TCP port 3389, I came across Remote Desktop Web Connection feature in IIS that adds tsweb access, my question is, does Remote Desktop Web Connection use http protocol as a transport protocol over port 80? Or is tsweb just an ActiveX control that acts as an rdp client and connects normally to 3389?
Windows Remote Desktop Services (RDS) role have a IIS feature called "Remote Desktop Gateway". This gateway makes the TSWeb ActiveX to tunnel the RDP session through an HTTPS channel (port 443) instead of having it acting as an RDP client (using the mstsc COM object probably) on port 3389.
If you don't mind trying an open source alternative, written in C# (.NET) and also using a IIS gateway (but not the RDS one), without any plugin browser side (and working in all browsers, HTML 4 and 5), I released recently Myrtille.
The Remote Desktop Web Access role (formerly Terminal Services Web Access) installs a website on a Windows Server machine. "TSWeb" is a website : you access it using the http protocol.
If you access this website with Internet Explorer, IE will ask you if you want to download an ActiveX. This ActiveX will allow you to connect to remote machines via port 3389 (RDP). However, "TS Web Access" itself is not an activeX, it is a website containing an activeX.
FYI, other browsers do not support activeX objects. On such browsers, the "TSweb" website will make you download a .RDP file instead of launching a remote connection via the activeX. When you double click on this file, or launch it with Remote desktop client, the remote connection is established via port 3389.
I have written a program that uses webDAV to download documents from a sharepoint server. It works well with client OS (XP, Vista, 7) but it doesn't on the 2003 server it's supposed to work.
How can I enable WebDAV client (not server) on Windows server 2003 x86 ?
On Server 2003 Web Folders (WebDAV client) is not installed by default. You can install it from Microsoft website: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=15123
Note that this will install Web Folders extension. In case you wish to use Map Network Drive wizard (mini-redirector, another WebDAV client) follow this steps:
Make sure WebClient service is running. Open Services snap-in and find WebClient service. On Windows Server 2003 this service is disabled by default. If the service is disabled open WebClient Properties dialog and on General tab set Startup Type to Automatic. Restart the computer.
Your WebDAV server must be located on a default port 80. Map Network Drive wizard will fail to connect to any ports other than 80 displaying “The network path http://server/folder/ could not be found” message. Map Network Drive feature does not support SSL / HTTPS connections.
Your WebDAV server must accept anonymous connections or use Integrated Windows Authentication. Map Network Drive will fail to connect to WebDAV servers using Basic or Digest authentication. Use NTLM or Kerberos instead.
Connect to a folder on a WebDAV server rather than to the site root. The Map Network Drive wizard on Windows XP and Windows Server 2003 will fail to connect to URLs such as http://server/. Instead specify an existing folder: http://server/folder/.
The WebDAV client should be installed on all Windows since Windows 2000. Probably the service is not on by default for server platforms. Check if the WebClient service is running.