My company's Sharepoint 2010 site currently has two different bindings: [A] for use inside my company's local network and [B] for external use.
One of our sub-sites created in ASP.NET is located on Port 8001 which we will call [C].
Whenever a user tries to access [C], there is success when the user tries accessing http://[A]:8001/[C] but the page cannot be displayed if the user tries to access http://[B]:8001/[C].
I'm looking for solutions in IIS 6.1 but I have found nothing. If anyone has any experience with IIS binding issues, it would be much appreciated.
It sounds like it could be a few things The most common are probably:
1) one is that C may not be bound to both internal and external IPs/interfaces. But rather is bound only to A
2) Port 8001 on your external facing IP is being blocked by your firewall/intrusion devices. For that matter it could be being blocked by windows firewall too.
Related
I used Visual Studio and IIS to successfully deploy a web project to the localhost. Go to localhost on port 51? Great, it pulls up. Wonderful.
Then I tried to add a binding so I could type in "example:51" and it would pull up the website. I then got the following error in chrome:
This site can’t be reached
example’s server DNS address could not be found.
ERR_NAME_NOT_RESOLVED
Looking around, some answers said to alter the hosts file in Windows. I did that, and it solved everything. I type in "example:51", I'm directed to localhost, which pulls up the website.
Then I completely removed the "example" binding from IIS, and it still worked fine. I wasn't so much adding a binding as changing the way "example" is interpreted. It also sends me to localhost on every other port as well, including 80, which I don't think a binding would have done.
So now I'm thinking I didn't solve the bindings problem correctly. Should I have done something differently?
IIS bindings tell IIS how to respond when it receives a request for a specific hostname.
You probably have IIS configured to respond with your site regardless of hostname, so that doesn't matter.
IIS bindings have nothing to do with DNS or name resolution, which is how the browser knows that example should resolve to your host.
I've created a workflow that will send a user an email that contains the URL for the entity. Somehow it's putting the wrong URL (specifically subdomain is wrong).
Does anybody know if there is a setting that controls this and what it is?
It gets the server URL from the setting in Deployment Manager, as far as I know. If in DM you specify the server URL as:
mycrmserver:5555
this may cause an issue. Using a FQDN will probably give better results:
mycrmserver.mydomain.com:5555
But obviously make sure you have DNS on your domain pointing to the internal LAN IP of that for internal clients (using mycrmserver.internal.local style FQDN won't work if you need IFD)
I'm not 100% sure this will fix it, but certainly worth looking at.
Open Deployment Manager -> Right Click on Microsoft Dynamics CRM -> Properties -> Select Web Address tab -> Make sure that the domain name specified under Web Application Server is correct
I'm having trouble finding info on this one, even having access to my company domain controller I still can't see what configuration is causing the same behavior I want to mimic on my home server.
I'm working from a test environment on my home PC and would like the following behavior. Note that I do not require any of these sites be accessible anywhere but my local machine, again, I just want to learn.
My Goal:
To configure IIS to host multiple sites, accessible via "aliases" which map to different ports. For example:
home -> localhost:81
test -> localhost:82
dev -> localhost:83
Furthermore, I want the url in my address bar to actually BE what it says on the left, not simply redirect, BLEH! So if I type "home/" in my address bar, it should load the page at "http://home/".
How can I achieve this? Thanks... ;)
Here's what I have configured in my bindings for the site so far, but no cigar...
first you need to edit your hosts file (probably C:\WINDOWS\System32\drivers\etc) so that you resolve home for example to localhost, add records like this:
127.0.0.1 home
127.0.0.1 test
...
Then you should be able to set up your IIS site with the Host name as home, but leave the port to the default of 80.
When I create a site in IIS I select for IP "All Unassigned" and then make a unique port.
I access my sites via the outside world like this:
http://mbdev.myftp.biz:8004
http://mbdev.myftp.biz:8006
Those all go to demos sites.
I have inherited a system with a number of servers, but I have never worked with IIS before.
Currently there is a web server set up using IIS, it holds a number of 'test' sites and the server is called Staging. I have network access to the files on the server and I can login to the server via VNC. What I cannot do is view any of the sites in the 'webs' folder. I know they are all switched on and working as they have been used by my predecessor.
I have tried putting into the url bar the IP address, the IP address with the folder appended, the name of the server and still I cant access the sites.
I am behind a firewall so these sites should be accessible to anyone in the network, but obviously I am mising something.
Any tips, anything I can look at to try and find the site. Annoying thing I only need to look at one of the sites in the D:\webs\test site folder for about 5 seconds :(
Look in the IIS properties of the site and look at what IP address and host header values have been assigned to the site.
I have an application that is currently deployed (ex. www.example.com ). However, now we have a "secure" subdomain, which will take all of the requests that need to be encrypted (ex. secure.example.com). The site that is at www.example.com is currently mapped to C:\inetpub\example.com\wwwroot\, and I've mapped secure.example.com to C:\inetpub\example.com\wwwroot\secure.
However, since secure.example.com was setup as a new website within the IIS Manager, when the secure site is visited, it displays an error since there is no web.config associated with this website; however, this is the way I want it since I want this to be a part of the application that is in the parent directory.
I think what you really meant to do was just right click on the web site for example.com and edit the bindings. In there you can add host names to that site.
Make sure you add them for port 443 which is SSL.
Map both the IIS virtual directories/web sites to the same directory, and check that are both using the same IIS application name.
(Not tried this, but can't recall seeing anything to say it would not work.)