SharePoint–TFS–BizTalk 2010 tidbits…

I’m currently working a SharePoint 2010 Integration Project which includes custom Workflows, custom web parts, BCS, WCF Services, REST Services, and BizTalk Server 2010 LOB Adapters…. You should of known BizTalk was in there somewhere Smile I’ll be posting some articles about my experiences here. So I’ll start with the first strange occurrence of external access to our Internal Site, it didn’t work!!!


We have multiple environments: Dev Silo, Dev Network, Testing, QA, Staging, TFS Source Control, TFS Build Server and Production. We mostly setup all the environments, for both the customer, and due to some policy and scheduling, we also have an internal environment of servers at Tellago.

Today we succesfully demo’d our first sprint deliverables and we ran into a small problem. The Client, at the client site could not connect to our internet facing web site. Yet I could. The Client received a authentication dialog as if they were hitting the server, however when logging in, the site displayed “Page Could Not Be Found”. So I tried to log in on my laptop, and no problem. When logging into the server on another computer, same error: “Page can not be found.”

I started to think about this a little bit. Our servers are VMware images setup inside a Active Directory domain. After a little thinking I realized I had set up a host file inside the \%system32%\driver\etc. While I had the host file I easily connected to the server. yet others could not access it. It had nothing to do with permissions, it was all to do with IP Addresses, DNS entries and resolving the server name and access.

Thus I remember this back during the SharePoint 2003 days and remembered a little thing called “Alternate Access mappings”.

Taken from

“Alternate Access Mappings (AAM) is a feature of SharePoint that allows a website to function correctly under different URL scenarios, including, reverse proxies and load balancing. [If you’re interested, in learning more, there is this video, ] where Hilton Giesenow, host of SharePoint podcasts, demonstrates how to configure and make use of the this feature under different scenarios, including extending an existing site collection.

Check it out!!!

In anycase this is all I needed to do was add an Alternate Access Mapping of the exact IP address for the extranet, and my client could access the site and start using our developed components.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s