I'm trying to set up a http server that's accessible for other PCs in my company's intranet. The machine runs under Windows Server 2008R2, it has static IP and domain. It responds when I ping it from PCs connected to the intrantet.
For test purposes I'm using http-server npm module. When I run it, I can access the web server from the machine it runs on, but not from other machines in the same network. How can I make it accessible for PCs in my company's intranet?
Related
I have a working nodejs server which is served on an Ubuntu 22.04 Desktop os. The server is running on a LAN and it has an IP of 10.0.70.12. I can access this server from all connected computers with 10.0.70.xxx:3000 but I couldn't access it form 10.0.x.xxx:3000.
What should I do to access the website from 10.0.xxx.xxx:3000.
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 am trying to host a website on my machine via IIS with Windows 10 Pro. My machine is currently connected to my router which is directly connected to my Xfinity gateway. On my host machine I get everything set even with my bindings. When I test the site as it should it works properly on the host machine. When I test on my other machine that is directly connected to the Xfinity gateway it just takes me to the Xfinity gateway login page?
We have an VisualSVN Server running on our development server. An external vendor needs to access / use it (primary via TortoiseSVN, sometimes by using the web interface).
Since our IT does not allow external access to internal servers, they need to use a webserver in the DMZ (Demilitarized Zone).
Is there a way to redirect the external SVN access from this DMZ-webserver to the internal development server (preferable by using IIS 7 on the DMZ server)
I have a web application named MANTIS (Open source) and after configuring it, i want to deploy it in our local network in the company.
i used XAMPP on the server and the application is accessible in the server only and it is not accesible from any other computer from the network.
When i put the adress http://192.168.10.150:8080/mantis from any other computer connected to the same network, it shows me an error message.
can anyone help me to make it accessible from any computer connected to the netword ?
we are using
WINDOWS SERVER 2012 R2
IIS