I published a web application to one of app servers. Now, if I am connected within my company network (no login require), I can access the web site no problem. Now, if I am connected from outside of the network over VPN, I can't access the website (Getting page not found appears). Do I need to configure IIS on the app server for allowing the connection over VPN?
Thanks for your time.
It sounds like you do not have your firewall/router configured correctly to allow traffic from external sources. When your connected via VPN it is like you are connected to the internal network. Without the VPN you need to make sure it is routed correctly and visible through your firewall. Can you ping the IP that you are trying to get to?
Do you get DNS resolution when you connect over the VPN? If you are trying to hit an internal machine name address, you might try changing to the IP address of the machine.
Related
There have been many articles on various forums on how to setup mcrosoft active directory domain services. I am a bit new to the field, so please bear with my ignorance. I have a very basic query whose answer i am not able to find. I have an office of 20 people where i would like to deploy AD Domain services to have a better control. i want to know how should i set my network PHYSICALLY. I have a router supplied by my internet provider. Where exactly should i put my server? Can i plug my server anyhere in the network and connect the users through domain, or the main internet wire should plug into the server first and the users in turn be connected to the server. enter image description here I hope i am clear. Should internet ‘flow’ from the server which has AD to users, or i can put the serverver anywhere in the topology.
In a small size network like yours, 1 server should be enough. It should be somewhere behind the router. Plugging it into the switch is fine as it will have a internal address.
You will need DNS on your server which will install when you promote to a DC. All of your computers need to look at your server for DNS. Your Server's DNS should have a forwarder to your ISP DNS or to a public DNS. It doesn't matter if you server or your router does DHCP so long as it gives out the server Internal IP for DNS.
What would I do:
I would plug your ISP into the Router, Your Router into your Switch, and all computers + server into the Switch.
You can place your server anywhere in the topology. It is not necessary for all user traffic to the internet to be routed through the server.
With small-scale deployments (less than 25 Users) I typically just put the server on the same switch and subnet as the users.
I would like to create a local wireless without internet.
I would like to have the possibility to connect 50 clients and access to a website using a domain name.
That means, I need a DNS and DHCP.
I sreach on internet an I found a way to achieve that but not totally and i am not sure if it will work and if it is the best way to achieve that.
I can maybe have a mini PC (server) with ad hoc network and have the client to connect on the server but:
Will it be possible on a connection to assign a ip to the client and set a DNS server ip on the client as the same ip of the server.
I found mini PCs but how can I know if the PC will handle a lot of client ? Which network card to choose ?
I think also that a router and configure DHCP on it to distribute the IPs but I would like to have one box ready object as a mini PC.
I need an advice on the best way to go with what i want to achieve and materials i need to buy and good references.
For a linux domain controler you will need to install bind to host your own DNS. It's a little involved to set up, but necessary if your network doesn't have a DNS server. If you're using a windows domain controller you will need a server OS (expensive). If you only have 50 clients the DNS resources needed will be small and you could run bind from any old box, even a Raspberry Pi. You will also need a host machine for the "website" a.k.a. an intranet. This can be the same machine as your DNS server, but can be any computer on the network. When all is done you will have your router configured with the IP of your local DNS server. The DNS server will point your local domain to whatever box hosts the intranet website.
So I know I can use ngrok to project a website I host on localhost to be available publicly. Can I do the same for another site, which is only available in the local network, but not hosted on my machine?
For example, there is a website hosted on http://testing.stackoverflow.com, which is a version of the website that's only available to people connected to the internal wifi, but I want to so my customer a new feature that's only available on that website, without making it available to everyone. The customer can only access it while somehow connected to my machine. Can ngrok or a similar tool do this?
You can use ngrok to expose any host, accessible to you, to the internet. See https://ngrok.com/docs#non-local.
You have already used ngrok to tunnel traffic between internet and your localhost. Similarly, if you want to expose a web server in your LAN, say 192.168.22.22, just execute ngrok http 192.168.22.22:80, instead of ngrok http 80.
I am hosting an asp.net MVC 3 application on my local IIS 7.5 server. People can connect using my IP and the port I set. I can connect by typing localhost:port in a browser. If I type the IP:port however, the browser says it cannot connect.
Using wamp and other hosting programs (and even IIS at one point if memory serves), I could always connect using my own IP.
How can I set IIS to let me connect using my own IP? Or is the problem somewhere else?
My firewall is disabled, the port is forwarded and other people can connect just fine (people outside my LAN) and I have tried 3 browsers.
You cannot connect to your IIS using static IP, but, howerver you can by adding your Static IP as a lookup entry.
Please check this link:
How to Edit Your Windows Hosts File
The article explains how to resolve the IP to reach the IIS locally.
I have created an ASP.NET application on my local machine. In order to test this application in IE 6, I have created a VPC. I am trying to connect to this web application through the VPC. However, I cannot connect to it. I can however connect to the internet.
What am I doing wrong?
Can you ping from the virtual PC? If not, you have network configuration issues.
Otherwise, check firewalls, and make sure that port 80 is open and sending traffic to IIS.
there are many possibilities. first I'd consider would be any firewall rules on the ASP.NET side preventing incoming HTTP connections.
What is the URL you are using to go to your site? If you are using localhost, you will need to change that to the actual IP address of your development machine, as localhost on the Virtual PC image will be a different IP address than localhost on the development machine.