I have several sites on hosted on my local iis that I cannot access all of sudden.
Error I'm getting in all browsers I have installed (Chrome, IE, Edge) is- server DNS address could not be found.
Last thing I was doing before things wend wrong- installing Web Deploy 3.5, but uninstall did not help.
I checked hosts file and bindings in iis- both are valid.
Another thing I've tried with no luck:
Reset WINSOCK entries to installation defaults : netsh winsock reset catalog
Reset TCP/IP stack to installation defaults : netsh int ip reset reset.log
Flush DNS resolver cache : ipconfig /flushdns
Renew DNS client registration and refresh DHCP leases : ipconfig /registerdns
Flush routing table : route /f (reboot required)
Ping cannot file host as well
Ping request could not find host XXX. Please check the name and try again.
At the same time htt://localhost shows Default Web site with IIS welcome page.
This appeared to be a problem with permissions on host file- somehow those got broken
Related
guys please anyone can help me to solve this problem, after generating link by ngrok and when I have try to access this link browser replay : server IP address could not be found
There are many reasons for this error, you can try the following steps to solve this error:
Reset IPv4 settings.
Using cmd, we can issue netsh commands to reset IPv4 settings. launch CMD prompt as administrator, and type netsh winsock reset and hit Enter. Now restart your PC. Open CMD again and type netsh int ipv4 reset reset.log and keypress Enter. Again restart your PC and check if you can connect to the internet. This will completely reset all the IP configurations and changes that we made in our system to default one for automatic resolution.
Flush DNS Cache.
You can also flush the Domain Name Server (DNS) information that is cached on your system. Open cmd as admin and type ipconfig /flushdns, If everything is running right, you should get this as output — Successfully flushed the DNS Resolver Cache.
Change IP and DNS settings.
In most cases, the options are set to default. However, if you’ve made any changes or any antivirus software has deliberately misconfigured it, then you can just revert back the changes.
I have create a very simple site in IIS Server version 8.5 using port 85. The site only have one index.html that shows the word "test" the page. When I access the site inside the server I can access it successfully: "http://localhost:85" is working.
Trial 1:
I try accessing it from my computer that is connected to the same network with the server using url "http://servername.test.com:85", the browser goes loading for long time and finally ends in with error "Connection Reset".
Trial 2: I try updating the Site Binding's Host name with our "Vanity Name" and "IP Address", but after this I still get a "Connection Reset" error.
Trial 3: Now I also check for opened ports using netstat, and I can see that port 85 is open. So I don't know why I'm getting Connection Reset error
Trial 4: I added Connection timeout value on the settings. But still I'm getting Connection Reset error.
Please kindly help with advise how to fix this Connection Reset issue. I can't find what is the reason behind this issue. Thank you in advance.
According to your description, I guess you may not bind the right IP address for the servername.test.com domain or use the wrong ip address bind with servername.test.com domain.
I suggest you could firstly try to use the server's ip address to access your web application to make sure you firewall setting and IP setting is right.
If your client server and the IIS server are in the same domain and you have installed an DNS server, then you could access the web site by domain. Details about how to set the DNS server, you could refer to this article.
If you just want to test, you could try to modify the hosts file in the C:\Windows\System32\drivers\etc path in your client server.
For example:
127.0.0.1 www.example.com
I've found the solution. I issue was caused by Firewall enabled on the server and the ports are not opened by the Network Administrators. So I just opened the Ports that I will be using and it works now. Installing IIS Failure Tracing help me catch the error also. Thank you for all those who answered.
I'm used to using a Mac, and ngrok is a breeze; all you need to do is specify a port, but I'm new to IISExpress, and I can't figure out how to use ngrok and/or IIS correctly. To be clear, I've inherited a Windows machine from a coworker (who has left the company) and the set up works great locally.
The local url is similar to:
thing.somedomain.com
In the bindings section of IIS, I've got:
Type Host Name Port IP Address
http thing.somedomain.com 80 *
I've used this page for reference: https://www.twilio.com/blog/2014/03/configure-windows-for-local-webhook-testing-using-ngrok.html
The instructions seem reasonable, but they don't work for me. These instructions indicate that the file applicationhost.config needs to be altered for IIS. I have found this file, and found the correct section for the site I need to ngrok. The binding info does not match what's in the IIS gui though:
<binding protocol="http" bindingInformation="*:4085:localhost" />
As per the instructions, I have added:
<binding protocol="http" bindingInformation="*:4085:whatever.ngrok.io" />
(Here every time I run ngrok on windows I get ngrok.io instead of ngrok.com, which seems odd. I've tried accessing both ways with no luck.)
I have restarted the site on IIS (in the actions menu). When I try to access the ngrok url from a remote machine, ngrok returns 502 bad gateway, and the remote machine shows:
Failed to complete tunnel connection
The connection to http://whatever.ngrok.io was successfully tunneled to your ngrok client, but the client failed to establish a connection to the local address localhost:4085.
Make sure that a web service is running on localhost:4085 and that it is a valid address.
The error encountered was: dial tcp 127.0.0.1:4085: ConnectEx tcp: No connection could be made because the target machine actively refused it.
When I try to go to localhost:4085 locally, I get "This webpage is not available". When I try to go to localhost:80, I get a redirect to a different site the IIS is serving. When I try 127.0.0.1:80, I get a 404 error.
I have tried using netstat -a -b, and have tried all of the ports associated with 127.0.0.1, and nothing turns up the correct site (yet still thing.somedomain.com still works correctly).
I'm completely mystified, and don't know what to try next, or where the problem lies (in how I'm starting ngrok, in how I'm accessing ngrok, in how the bindings are mapped, in how IIS restarts, a firewall issue, or some other voodoo). This should be bloody simple!
So it turns out that there was nothing to change in the ApplicationHost.config file, AND I was looking at the wrong ApplicationHost.config file (the real file is normally hidden from view in C:/Windows/System32/inetsrv/Config, but you can open it in Notepad from a Command Prompt that has elevated privileges (Run as Administrator)). The actual binding info was:
<binding protocol="http" bindingInformation="*:80:thing.somedomain.com" />
Which is what matched what IIS was showing. That said, what I needed to change was how I invoked ngrok:
ngrok http -host-header=thing.somedomain.com:80
And that was it. I also allowed external traffic to the hostname with this:
netsh http add urlacl url=http://thing.somedomain.com/ user=everyone
There is a way to make it easier. Let's say your IISExpress website is http://localhost:63254
Just start ngrok like this:
ngrok http --host-header=rewrite localhost:63254
I have 2 servers which are located in different networks. On each of them IIS is installed. When I try to connect to the first IIS server from the second, it gives me error: "Could not connect to the specified computer. The remote name could not be resolved". Fierwall is switched off. Maybe I should configure something in DNS or somwhere else?
Update:
Ping is ok, no packages are lost.
What happens when you "ping" the address from the command prompt?
If it comes up with host not found, then you either need to configure DNS on the server trying to get to the remote computer OR create a static hosts file entry pointing the name to the ip address...
I'm Unable to access CouchDB remotely. I'm using a Windows 2008 virtual machine in Azure.
I did the following,
1) Installed IIS on windows server 2008.
2) Created an endpoint for port 5984
3) Installed CouchDB & verified the same by using futon
http://127.0.0.1:5984/_utils
4) Created a subdomain ( db.mydomainxyz.com ) with my domain registrar & verified. If I type http://db.mydomainxyz.com/ in browser - IIS7 default page gets displayed.
5) Made couchdb to listen on all network adapters by setting => bind_address = 0.0.0.0
6) Created vhosts to point to my domain = > db.mydomainxyz.com:5984 = /db/_rewrite/
After doing all these things I'm still unable to access CouchDB remotely http://db.mydomainxyz.com:5984/
Is there anything I'm missing ?
After changing the bind_address, CouchDB must be restarted. The problem is that its daemon is very resilient. So even if you tried to restart it, it probably never stopped. Restart your virtual machine instead.
See the similar discussion on ServerFault for more information.
This command solves the issue:
netsh advfirewall firewall add rule name="Apache CouchDB" dir=in action=allow service=any enable=yes profile=any localport=5984 protocol=tcp