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.
Related
I am deploying a React app on a virtual machine, windows server 2012, hosted on the IIS server. The website is successfully running on the local server. When I try to access the website through a remote computer, the static components are rendered successfully, but the API doesn't work. The API is written in node.js and installed as a windows service on the windows server with the port number 5000.
I put localhost:5000 as the axios base url in react. But when I try to access from the remote computer, the computer is reading from its own localhost instead of the server's localhost.
Even if I change the axios base url from localhost to the server's ip address, it still cannot read the API properly.
My questions are as follows:
How to make the remote computer reads from the server's localhost without putting the server's ip address?
How to make the local server's windows service accessible to other computers?
What is the best practice to store the API base url in React in production? (store in.env, config, etc...)?
I just solve the issue and I post the answer here for anyone who has the same issue.
Windows
Create a firewall rule (Windows only)
You need to allow other computers to connect through your firewall.
Open the Windows Firewall
Go to “Inbound Rules”
Click “New Rule”
Select “Port” to make a port rule
Under “Specific local ports”, enter 80 and 8000 (for me it's port 5000)
Select “Allow the connection”
Click “next” then choose a name for your rule.
Source of this answer: [https://otree.readthedocs.io/en/latest/server/adhoc.html#windows][1]
I have a .net core 3.1 service running that is using a custom Com dll that is talking to a machine connected on a serial port(serial to usb cable). The service is hosted on a windows 2012 server.
A user is then opening a remote desktop session to the server and forwarding the local serial port where the machine is connected to. When we run the service as a service the custom Com dll cant talk to the forwarded port, but if we run the service as a standalone, not as a service, (kestrel) session inside the remote desktop session it works fine.
Cant a windows service(or IIS service) communicate with a serialport that is forwarded using remote desktop port forward? is the port only available in that "session" and not accessable from the service context?
We have tried to run the service as the current users, local system, network system etc.. we have tried to run the service hosted in IIS and regular window service, we also tried to run it as a scheduled task but with same result.
Anyone have any idea on this?
Thanks in advance!
I hosted a website on IIS, running on port 81. I can access it on the server machine from http://localhost:81/test.aspx.
I also can establish a remote desktop connection to the server, using its ip adress server-ip.
Now I want to access the web site using my PC (or any other PC). However, I type type http://server-ip:81/test.aspx on my web browser and the page is not loaded.
I've already opened port 81, by adding a new inbound rule to the server's windows firewall. The exception for World Wide Web Services (HTTP) is also ticked on. I even shut down the firewall entirely, but I still can't access the web site remotely.
Can somebody tell what the problem may be? Thanks in advance.
Ok i have successfully created a VM Server 2008 on Azure and installed the TFS 2012 express.
I try to access it via visual studio, web interface but i can't.
Port 8080 at the VM's firewall is open for public, however the port appears closed through a port scan.
Any suggestions ?
Note: I know about https://tfspreview.com/ however i would like to setup my own on my own VM :)
Opening the right ports on the firewall is a good start. But you need to let Windows Azure which ports should be opened externally and forwarded to your VM (also supports load balancing).
In order to make port 8080 externally accessible you'll need to go to your VM in the portal, go to the endpoints tab and add an endpoint here (make sure it maps to private port 8080):
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.