I have a REAL IP. XXX.XXX.XX.XXX, with that, i have DNS, Subnetmask, gateway and secondary dns from my ISP provider.
I have connected my PC (windows 10) with that setting in TCP/IP v4. And network is fine for outgoing.
Now I build a simple html web site and created a site in IIS 10. in Binding, I used the REAL IP, with port 80. From that pc, after hitting the IP Address, I am getting into the site. But from outside the network, via internet, If I hit the IP, nothing comes except Problem loading page with respond timeout.
How can I access the IP from outside internet?
Related
I have windows 2008 R2 server. It is located behind a firewall called Fortigate.
I need to access an application on local iis from outside.
I opened a free account on cloudflare for this. I forwarded the A record of localsite.mydomain.com to my own ip address.
I opened a port in Firewall and forwarded it to my server.
My aim is only to be able to access the port on the server from localsite.mydomain.com, other than that, by typing the ip address, port scanning programs and so on. I don't want it to be accessed.
I thought of typing the cloudflare ip address from the server's firewall, but the cloudflare ip address is constantly changing. How can I do it?
I am new to networking and routing.
I have hosted my website (enabled https) in azure vm having firewall settings. Have opened the ports for the websites.
But still unable to access my website from internet.
I have 2 sites running. the main website which is running on port 443. To access this site , it is directed to openid oauth2 identity site running on port 44300. Both the ports are opened. The site is running perfect when i access from the hosted server and also other servers.
I am trying to access this main site from my home internet. It is not working.I want to access this site from internet as well.
additional info:
Main website hosted in server which is connected to internet with a Connection which has got a IPv4 Default Gateway - eg; A
My own pc connected to internet with a different connection with different IPv4 Default Gateway.
With this above setup, it is possible to achieve my requirement?
Can anyone help what has to be done to access my website from outside world?
Thanks
I have installed IIS server on Windows 7 professional.
I am able to access the server using IP lets say 172.8.5.1 but when I try to ping the site outside of company network I get a network error (tcp_error)
Any one knows what needs to happen in order to access it over WWW?
Make sure that you have a static IP adresse,and then authorize incoming http request on port 80 from your router or your firewall.But the ip adresse should be accessible by internet
I have a laptop running Windows 8.1.
I have IIS up and running. I have Web Services there.
To use my company's resources, I should connect to it's VPN. I need this VPN access, so my Web Services can connect to database using Windows Authentication. However, VPN was used (even if connected) only for those resources. So, when I was browsing stuff in Internet, sites saw my real ISP's IP and not VPN's.
Starting from today this was changed. Now, if I'm under VPN, I have company's IP and I can't access my laptop from anywhere. Previously, I could access it using my real IP.
I asked admin, what happed. The answer -
Split tunneling when on VPN has been disabled in response to US
Federal Government requirements.
So, everything is working, except access from outside to my local IIS.
Is there any way, I can put some local (on my laptop maybe) routing, so external can access my laptop?
We are installing a security camera system in our company which comes with a DVR that hosts a website on which you can view the cameras via the web.
I have setup the DVR with a static IP of 192.168.120.199 on our network and can view the website while on our network (either when at work or logged in via VPN). The camera DVR uses port 80 for viewing the webpage and port 9000 for Media Port.
We use GoDaddy to host our DNS info and I have added an Host(A) record of 'cameras' that points to the address of our server. I have also added a forward lookup Host(A) to our domain's DNS manager of 'cameras' that points to 192.168.120.199. When I use the address 'cameras.mysite.com' within our domain the website displays properly, but when I try the same address from outside our domain (ie, at home) it displays the default IIS 7 page (from our domain server).
Two questions about this setup:
Why does the forward lookup work when inside our domain but not outside (why does it go to the IIS default page when outside the network)?
How do I get this to forward correctly if not via the forward lookup host?
Because internally you're looking it up on your internal DNS server and you get the right 192.168.x.x machine. When you look it up externally GoDaddy is giving you back the 192.168.x.x, but that's not a publicly routable IP, so doesn't go anywhere. If you really want to be able to connect to your security cameras from outside your facility then I suggest setting up a VPN for security reasons. But if you want GoDaddy to directly route to your internal machine from the public internet then you'll have to give it a publicly routable IP.
As a further note on that - 10.x.x.x, 192.168.x.x and 172.16-31.255.255 are not publicly routable. They're called private IP blocks.