I am really novice in IIS related task.so I am facing a problem that i can not solve I tried different solutions from the internet but unable to solve it. Let me describe what i tried .
I created an api which I hosted in IIS and I can access this from my local server using the IP address .but i have a real IP of that server so that i can access the hosted API from external server or any device but when i replace the real Ip with the local Ip I can not access the api for example the real Ip is like below.
I tried the url
113.240.113.132 refused to connect.
113.240.113.132 is the real Ip OF 192.166.100.1
I Tried using this ..
<binding protocol="http" bindingInformation=":12105:113.240.113.132" />
with the real IP of the local IP
By using the local IP 192.166.100.1 I can access The API ,But When I Use the real IP 113.240.113.132 i can not access the api from my browser or any device .Help Needed
Related
I am recently learning web programming
there is a problem that confuses me:
I want to access some web like www.google.com, but the default DNS server used in my school's network is down, so I can't do it. Can i fix it by changing my default DNS server address to another school's DNS server IP address?
thank you first.
I have a node js server set up on AWS using Linux instance(Ubuntu 14.04) I have started the server using the command npm start How do I access the localhost:3000. And when I do it locally I am able to access all the webpages by going to the browser. How can i access it when the server is on cloud?
The localhost host name is resolved to IP address 127.0.0.1 (or IPv6 equivalent) which is routed to the loopback interface so that you cannot reach any other host than your own with that. That's why it's called localhost in the first place.
To reach your host from the outside you need to know its external IP address or a domain name that resolves to its external address. You should be able to see your external IP in the dashboard. If you can't then see this answer.
I have a Azure Website with virtual IP (ip based SSL), however, in my cloudservice I have to specify the address of my website to whitelist. Somehow I think I'm missing the obvious here since I cannot connect to my webservice when I deny all BUT my website. If I remove the Deny All -rule I can connect fine.
I now have, which wont work:
<AccessControl name="accessRestriction">
<Rule action="permit" description="permit-site" order="1" remoteSubnet="VIRTUALIPADDRESS/32" />
<Rule action="deny" description="deny-public" order="2" remoteSubnet="0.0.0.0/0" />
</AccessControl>
</AccessControls>
EDIT:
my website cannot connect to the webservice.(Unable to connect to the remote server)
EDIT2:
In my intellitrace log I can see that indeed the website is trying to gain access but is blocked
'Requested registry access is not allowed.'
Side note: If I add a permit-rule for my local home IP I CAN reach the webservice if my run my website locally (and connect from home).
2nd, off-topic question, In a lot of tutorials I see people using 'Order=100' and, 200 and then 300, instead of just using 1,2,3, why 3 digits? (answered)
EDIT3: both website and service are now https, still no connection possible with ACL enabled.
Thanks!
IP SSL does not guarantee the outbound IP address for outgoing connections, but it only associates the inbound IP with your site. You will need to whitelist all possible outbound IP addresses for your site according to what region your site is in.
For the list of outbound possible IP addresses you can look at https://social.msdn.microsoft.com/Forums/azure/en-US/fd53afb7-14b8-41ca-bfcb-305bdeea413e/maintenance-notice-upcoming-changes-to-increase-capacity-for-outbound-network-calls?forum=windowsazurewebsitespreview
The reason for this is that Azure Websites is a multitenant environment and the outbound IP address cannot be guaranteed at the site level.
I am able to access my website via the domain name outside of the network.
On the internal network I am able to access the site via "localhost/websiteName/", "internalIP/websiteName", and "computerName/websiteName", but I am unable to hit either "http://example.com" or "http://www.example.com".
I was able to get it to work on a computer by adding the ip and website to the hosts file, but I am still unable to access the website using the domain via mobile devices on the internal WiFi.
I completely disabled the firewall, so I know that that is not the problem.
I have bindings set up for www and without www with all IP Adresses unassigned.
I did try adding a binding for both www and not, using the internal and external IP addresses, both IPv4 and IPv6.
I am running this on http without any certificates.
I have a cname record for www
My # record is pointing to my external, static IP
The website is set up separately from the default website and it is not a virtual directory.
I am using Comcast Business with their Cisco DPC3939B router.
This is initial setup of the website, and it is not an issue that just started after having worked previously.
I figured it out. All I did was add an # record to the DNS to resolve the website to the internal IP. Here is a really great reference for accessing websites on a Local Network: devside.net
I created a IIS site in my windows server 2012 virtual machine. I want to be able to access it online on my android phone. I can access it locally on the server. The ip address of the server is 199.86.19.2 and for the IIS site its 192.168.113.133. Also the server is a dynamic ip. I have tried using an online site called noip.com to make a domain. I created a domain
mydomain.no-ip.biz and gave it the ip address 192.168.113.133. I even installed the client program so it keeps my ip up to date. However when I visit mydomain.no-ip.biz. it says it cannot be found.
Does anyone know what is wrong here?
Thanks.
192.168.113.133 is your local IP address on your network. 199.86.19.2 is your external IP address that your IPS assigned to your server (until it expires). I'm assuming you are doing this at home so you would need to make sure if you have a router, you need to configure it to set it up to port forward to your local IP address.
Set your 'mydomain.no-ip.biz' ip address to 199.86.19.2 and make sure your router (if you have one) is forwarding to 192.168.113.133.