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.
Related
Since a recent web server migration to Windows Server 2019, when someone tries to access files in a UNC share remotely via VPN (programmatically or via File Explorer) , it causes a WebDAV request with the PROPFIND method. The UNC share is not inside the web root, is not listed as a virtual directory, and is not even on the same drive. These requests to not occur when accessing the share from inside our network.
WebDAV Publishing is not installed in the Add Roles and Features UI (Web Server (IIS) > Web Server > Common HTTP Features > WebDAV Publishing)
WebDAV is not listed as an installed module in IIS
What is causing these requests, and how can I prevent them? I just want the UNC share to be a normal shared folder - not accessible from the web.
User-Agent making the requests: Microsoft-WebDAV-MiniRedir/10.0.18363
I have a server at a remote office running Server 2008 R2. This server is a local domain controller for that office. I was having issues with Active Directory not replicating and I disabled the network adapter by accident. Now I am unable to login to the machine and my local user at the site cannot login with domain admin credentials. As this is a domain controller I am unable to login as a local user.
Is there a way to enable the network adapter by modifying a file within windows if I boot via Linux or something?
So for anyone else dumb enough to make this mistake, here's what worked for me.
Boot to Linux, and turn the adapter back on via Windows registry.
Is it possible to remotely manage an IIS server, running on Server 2016 NANO using the IIS Manager 10 from the client?
I have a newly created nano VM. I've installed IIS, dotnet, IIS Administration API, and File Services on it. IIS is working from the client side. I can see the default page when I browse to the VM's IP address. I can authenticate to the IIS Administration API through the browser. I can copy files from the client machine to the server's inetpub\wwwroot directory through Windows Explorer. Everything seems to be working but when I open IIS Manager 10 on my client machine and try to connect it to the nano server, I get an error message that says "Could not connect to the specified computer. Details: The remote server returned an error: (401) Unauthorized."
I've already followed the instructions at
https://blogs.iis.net/adminapi/microsoft-iis-administration-on-nano-server
That's how I've gotten as far as I have but now I'm just stuck and can't seem to find any path forward.
EDIT: BTW, I am able to connect to the site and administer it with http://manage.iis.net/
As far as I can tell, it's not possible.
You can see what's available with dism /online /get-feature, but IIS-WebServerManagementTools is not in that list.
I've developed a solution and tested it. It's uploaded to Azure using the convenient method of publishing XML file. Now I realize that it's supposed to be put in on-premise local server (it's an internal application not requiring access to the Internet).
When I go to the server, I use the RDP to access a system. In there, I execute a connection to another RDP. The second system is the one hosting both SQL Server and IIS where the application will reside.
Is it at all possible to construct such a publish XML? If so - how? If not - what should I request form the IT department to open/install on the innermost RDP so I can shove in my stuff by the oh-my-god-I'm-so-lazy press of a button?
You must install webdeploy on your host machine. With IIS and webdeploy installed you can use same publishing techniques as you did with Azure.
I think it goes without saying that you must have direct access to host. If it's on external network you have to open webdeploy's and IIS ports, if you do not want to open this externally I recommend VPN (maybe basic point-to-point) that will create direct line between your dev and host machine.
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.