Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I have a webpage for the teachers at the school, and it's found on localhost. (192.168.1.1)
I can reach that page out of school also. (example.com)
I want to solve the following: If they at the school and want to open example.com, don't have to go to the internet and back to the school with the request.
I want to host all example.com requests to 192.168.1.1 at the inner server. And if someone called example.com at the school, it would be over LAN and if out of school, it would be over Internet.
You can choose between (I would rather the second one):
1) Modify the "hosts" file in each machine (by hand) to force example.com to 192.168.1.1 (it is hard)
You can find this file:
Windows: %SystemRoot%\system32\drivers\etc\hosts (by default the system root is c:\windows, so if you are using Windows, your hosts file is most probably c:\windows\system32\drivers\etc\hosts)
Linux: /etc/hosts
Mac OS X: /private/etc/hosts
2) Set up a transparent proxy at school, so all requests will go through this proxy, and you will only have to add this rule in your new proxy machine.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
I can access the web site from the local network (192.168.2.120 My Local IP)
but i cant access the web site from global network (95.10.239.XXX My External IP)
I opened 8080 port from the modem
IIS Edit Bindings Image
I opened 8080 port from firewall
Im using Windows 10
First of all you need to check if port 8080 is accessible from outside. You can use this tool: http://www.yougetsignal.com/tools/open-ports/
If it is accessible, then it should work, if you will try to open in browser http://95.10.239.XXX:8080/
If it is not accessible, then you might need to do this steps:
Set up port forwarding and(or) DMZ in your router. It depends on your router.
Open firewall on your machine. You mentioned that you did that already.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
We are running a Java based web-application, and were in the process of updating the site from http:// to https:// (by installing SSL cert),but encountered issues with bringing the site online.
On further analysis, we found that the port 443 was being blocked, which was preventing this site from being accessible on https://
We informed the same to the Network team, to open firewall on port 443. But the problem is, they keep coming back asking for the destination port.
We provided the source IP (IP of the application server)...what would be the destination IP (is there a specific destination IP if a site needs to be accessible on https://) ????
My question is, what would be the destination port, to open firewall to make a site accessible on https:// ??
Most likely they want to setup NAT so that incoming requests coming to NAT:443 are routed to :443 , and for this they do need an IP of the server within the local network.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I have vsftpd set up at my home PC. I use a airtel broadband connection with a router, hence I have a public IP address and then a private IP address, none of which is static. Locally I can access my FTP through my private IP address, I wanted to know how would I access my computer though a remote location. I'm pretty sure
ftp://xx.xx.x.xx // my public IP wont work
You have to go into your router settings and give your PC a static local IP address. Then tell your router that every incoming request for ftp (usually port 21) is to be directed to that local IP address.
Specific instructions would be hard because every router is different and they all have a habit of changing their gui every chance they get.
Really surprised no one's answered this yet. Rocket science it's not.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
I just started to learn about networking and decided to run my own node.js server
The problem is i have almost no idea what im doing :(
I installed a virtual ubuntu 64 server, installed nodejs and all the prereqs.
I downloaded a sample (https://github.com/ry/node_chat) and dont know if its working or not.
i run node on the server file and get "server running at 127.0.0.1:1337"
How do i see it on my host (physical) machine?
Thanks!!
ps i have no domain, virtual is running on NAT network and my physical is behind a router
In your virtual machine (ubuntu 64bit) start the terminal and run
ifconfig
This should give you the ip address assigned to your virtual machine (192.168.x.x) something like that. On your host open up a browser and type in http://192.168.x.x: in your case will be 1337.
I would recommend you configure your VM to always have that ip static and setup the hosts files on your host machine to point to the ip address, making it easier to get to the server.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I am setting up multiple sites on IIS7.
What are the pros and cons of:
Setting up all the sites on the same IP address but different ports
versus
Setting up all the sites on different IP addresses.
Also,what are the implications for SSL certificates(any any other aspects that you may know of) between the above two approaches?
First, each site that uses SSL, must be bound to an IP address. SSL sites can only be segmented by IP (and port) and cannot be segmented by host name.
The only implication by segmenting by host is that if a given site goes down (literally stopped) and if there is a site listening only on IP, it will "choose" that site. So, the effect is a user goes to site A and sees the stuff from site B. If all sites segment on host, this isn't a problem.
For public sites that assume 80 and 443 for http and https, you really can only segment on IP or host. Most users will not be expecting to navigate to something on a different port and you would need to open special ports on the hosting system's firewall to allow for requests on those ports.