I have been tasked with re-homing sites off of our old Server 2008 host. I have sucessfully migrated all the sites but one.
we use a DNS Alias that points to the correct server so users are not constantly having to update book marks. On the old server if you http://SERVER1 you get the site, however on the new host it is redirecting back to the old server. If I go http://SERVER2/Portal I get the site.
I am able to do a nslookup, and can ping by hostname and that all is resolving fine.
I am at a loss, because everything in the IIS Configuration looks identical.
Thoughts on what the issue is?
Related
I have created a Blazor Server side Application which is working perfectly fine when accessed on a Win 2012 Server in our old Domain, no matter in which Browser.
If I host it on a Win 2019 Server in the new Domain though, it's only working in Internet Explorer.
Edge displays the ERR_CONNECTION_RESET error. I did both of my tests from the same client which is located in the old Domain.
If I try to open it in Edge directly on the new Server, I receive another error: ERR_CONNECTION_CLOSED.
On both Servers it is running on Port 5001 (HTTPS)
Our Firewall department can't find any errors in the Logfiles.
Hope you guys have got an idea what might help.
So far I downloaded and configured IIS (version 10) on my windows machine. I created a domain called kinux, using the hosts file, so when I navigate to kinux.com, I'm brought to my IIS server root directory. I then created a site called localwww and configured ColdFusion to run via this site.
What I'm trying to do is make it so that when I go to kinux.com, it redirects me to my ColdFusion site. Does anyone know how to do this?
hosts
# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost
127.0.0.1 Kinux
127.0.0.1 Kinux.com
localwww site
Default site
Two solutions that I can think of:
Move your ColdFusion site to port 80 and add binding for hostname "kinux.com" such that all incoming requests to kinux.com will be served by your ColdFusion site.
Assuming "Desktop-server" is the website that gets called when you enter "kinux.com, click on it in IIS manager. In the center panel you will find "HTTP Redirect". Set the URL of ColdFusion website here. What will happen now is any request coming in to "Desktop-server" website would be redirected to your cold fusion website.
In solution 2, an important thing to note here is that the when the first request reaches "Desktop-server" site, IIS will indicate to the client (browser from where it is being accessed) that a redirect rule has been set to the new URL. The client will now once again make a new request to the new address (ColdFusion). So please ensure that the URL you enter in HTTP redirect rule can be accessed by client machine as well.
Let me know if you have any questions.
I am currently hosting a website (running with MVC4 website) with HTTP and HTTPS in Windows Server 2008 R2 (IIS 7)
However, after each server restart, the site will always show "The connection was reset". I have to manually reconfigure the "IP Address" at "Binding" in IIS7.
Any possible way to trace how the issue could happened and anyway to fix it?
(Sidenote: I have similar website that hosted in IIS 8, Windows Server 2012 with same configuration, and the issue does not happened to the machine)
Update:
There is no trace in Event Viewer, so I have no idea what are the possible issues that happened.
Update:
The websites are virtual hosted on the same port in same server with binded DNS, where all of them using wildcard certificate based on domain for all HTTPS site. When I edit binding on one of the website with the HTTPS port, the rest of websites will work just fine without touching any binding.
I have 2 servers, server A and server B. Both have IIS7 and same OS. I published through my VS2008 the same website on both servers. the problem is on one the application in IIS7 website works on the other it doesnt.
Server A - IIS7 - WebsiteA - Application (Works)
Server B - IIS7 - WebsiteA - Application (Does not work)
what are the things that i could be missing to configure IIS7 in server B ?
You need to find out what machine the IP Address is referring to.
It's possible you have firewall's, routers, and host configuration files which are effecting this.
Run a tracert to your server, and to the ip address and see where your route is going wrong.
Check you don't have multiple IP Addresses assigned to the same machine.
If you can, ask a member of your network team to help you out.
To help you more, we need to know the details of your infrastructure.
This is driving me nuts. I am trying to setup a webiste on our dev server with a specific url name www.mystpidsite.com as an example. mystupidsite is not the same name as the dev server.
1) specify a specific url to use for the website I create in IIS
2) run it and use that url to access it
I have:
1) created a new site in IIS 7 in Server 2008
2) attempted to access it via the site name which I set to the desired url and port 8888. So if we want it to be www.mystupidsite.com I setup the website name to mystupidsite in IIS 7.
3) I even tried to create an application under mystupidsite with the same name in IIS 7.
The server is definitely accessible and pingable on the network from my local PC, we have other stuff installed on this new server. Do I need to create an application or is just creating the website enough in IIS 7? I specified the IP as the server's IP in the website I made.
For the host name in the bindings of the site I put www.mystupidsite.com
when I try to access the site via www.mystupidsite.com it can't find it and the site in IIS7 on the dev server is running. It's running on a HyperV instance which is our dev server. Everything else has worked just fine. I just wnat to understand how to get a specific url by name setup.
Do I need to add something in the hosts file on the server or something?
You're not going to be able to have a site on your dev box answer to both the mystpidsite.com and mystupidsite.com domain names.
Unless you have the domains registered and have your domain's nameserver directing that name to your dev machine, IIS is only going to answer to requests either the machine name on the network or the IP address of your machine (in addition to 127.0.0.1 and localhost).
The only thing you're going to be able to do outside that scenario is set up two sites on two different ports on your machine and access them from http://localhost:80 and http://localhost:8888 (or network computer name equivalent).
you need to have an entry in dns to be able to hit the server when using www.mystupidsite.com
Because you have the site running on an alternate port you should be able to get to it by http://your-server-IP-address:8888
If you want to test it locally using the host name and do not have access to dns you can add the appropriate entries to the hosts file on your local machine (c:\windows\system 32\drivers\etc\hosts)
What happens when you type 'nslookup www.mystupidsite.com'? Do you get the IP address of the virtual server?
Do you have the windows firewall enabled on the server? if so, did you add an exception for port 8888?
add a default binding (no host header / blank) and try accessing it by IP