How do I directly access alternate WebAccess Ports
So, I've been able to successfully set up my Web Server (IIS) with a site operating-on/bound-to Port 80, and have had no problems accessing it from the Web using the provided WebAccess URL.
This is very helpful, and the first step of what I need to do. However, I have read in detail that it that we would also be able to access additional ports (443, 8080, 8000-8010) through WebAccess as well. This is exactly what I need...!
However, I've tried binding/running web applications on these other ports (I've tried 8080 & 8000 & 8001), and while they're running fine locally, I am unable to access them directly through the provided URL.
I have taken my base URL:
(This works fine, and goes to Port 80)
Then, I have added my Port indication:
http://xxx.env.cloudshare.com:8000
(However, this never works but always brings me to an error screen)
Please advise me as to what I'm doing wrong...
Is there a different way that I'm supposed to access this opened port?
This is critical as we're aiming to be able to test multiple versions of our web application that has everything configured on one machine. The alternate would be to create extra machines, but this seems unnecessary, as well as would take a lot of time to set up the machines (as there is no way to duplicate a machine within an environment).
Appreciate the help!
-
Hi Rajit,
Great question and one that we often get. Have you tried setting up the various sites you need in SharePoint and assigning the ports there and setting up the Alternate Access Mappings, then mirroring the settings in IIS Bindings as below?
If you set up your sites and then assign each one a different port from our list of opened ports (80, 443, 3695, 8000-8010 & 8080) then you should be able to use the Web Access URL and port number to direct your users directly to the site you want them to see.
On a side note, I noticed you are running SP Foundation Server. You may have a better experience by running one of our SP Enterprise versions with more functionality.
Also feel free to have a look at our pre-built farms in the SharePoint Showcase from our community.
-
Scott, thanks for this information.
However, just to be clear about a few things:
SharePoint was just testing something out; we're not actually using that machine, and I will be removing it from our environment.
We have the other machine primarily setup, and our main usage is to be able to fire-up a collaborative development/testing environment (most of our team is not in same location) that we can work together through.
I have been able to get the IIS and everything set up for our sites. However, if I try to bind it to a port other than 80 (using one of the identified-permitted ports such as 8080), and I try to access the site directly from the URL it never works.
At core the main question is this
How do I actually access these permitted alternate ports directly from the external web access url?
(as putting a port identifier URL:8080 does not work, but just brings an error)
From your post above:
If you set up your sites and then assign each one a different port from our list of opened ports (80, 443, 3695, 8000-8010 & 8080) then you should be able to use the Web Access URL and port number to direct your users directly to the site you want them to see.
This is what i'm trying to do, but I can't indicate the port number.
If you follow-up directly, I will send you examples of URLs that I'm trying to use.
-
Scott / Avi,
Sorry for taking so long to respond; other work had taken me away from this for some time. However, I did alter the Local Firewall Settings on the Server and was able to successfully connect through the permitted alternate/additional WebAccess Ports. This is exactly what we needed!
Thanks for your help... this is now completed!
-
Hi:
I have a similar need but much simpler. Using Web Access I want to get to a different site collection than the one on the root URL (/sp2010/sites/SiteName). But it is the same port (80). When I try Web access with the root site collection it works fine: http://xxxxxx.env.cloudshare.com/. However, http://xxxxxx.env.cloudshare.com/sites/SiteName does not work (status 404). What is missing in the mapping between the local host name of sp2010 and the internate URL of http://xxxxxx.env.cloudshare.com?
Thanks,
Bruce
-
If anyone runs into similar problems like this, it can be a tricky one and comes up often.
90% of these types of issues can be sourced back to Alternate Access Mappings and IIS. So when in doubt, check that the Web Access URL (or Vanity URL) is assigned to your site in SharePoint AAMs and in IIS.
Web Access and Vanity URLs are pretty dynamic, so you may not always need to update your standard URL with the Vanity version in AAMs & IIS - but it's good practice to check.
Please sign in to leave a comment.
Comments
8 comments