← Forum Post Reply →

• ← Group Forum | Forum Topic Directory

  HELP configure Sharepoint sites correctly (3 posts)

• Neil Stirling said 1 year, 7 months ago:

  Hi guyz, (just learning a few new things here so please bear that in mind)

  right this may be long so bear with the explanation.
  Just got a windows server 2008 r2 build up and running, made sure and got all AD services, dhcp, dns all working fine etc.
  Main reason I did this was to run an application server with remotely accesible web apps.

  So got sharepoint 2010
  installed fine, let me work away on whatever sites i want to fine.
  I now want to start testing these sites and access them over the internet.

  So where do i start? hoping someone knows of step by step guides to doing this?

  I have my site/sites ready to go.
  I have a FQDN for my server. The sites are listed in IIS. I have a dedicated adsl line (static ip) which the server is connected to, and made sure all the ports needed to access my sites are open. built in windows server2008 firewall setup to make sure access is allowed to the sites. (no isa)
  LAN is all setup for internal and external IP addresses.

  now obviously i realise this isn't just enough since i obviously cannot access my servers sites over the internet yet.

  Where do i go from here, now i have been looking at other soloutions to my problem, but they are all split down into so many different catagories that im getting a bit confused of where to start and where to look for some of the settings i need to change.

  From what i understand so far. I have to create a DNS record linking my FQDN to my ip address?
  now i assume this is already done since i already have a dns record with my FQDN listing my internal address e.g.192.168.x.xxx

  If this is not the case however, what kind of dns record am i creating and under what folder? cname record? under sites?

  Also then understand that I have to configure AAM in sharepoint. ok, now what exactly am i entering here? obviously not whatever i want. Will have to correspond to the sharepoint site itself yes? so if i add a public url in the internet zone, say"www.mysite.com"
  How do i then access this from the internet?

  Anything guiding me from the processes of finishing designing a site to getting it accesible from the internet would be a great help. So far cannot find anything that does a decent in detail guide.

  If you have any questions that would help you answer my query, please by all means ask away.

• matt said 3 months ago:

  Sounds like you need to configure port forwarding on your perimiter devices firewall/routers to allow the web requests to your FQDN (www.whateveryoubought.com) on port 80 and 443to be routed appropriately through your internal network to the server hosting sharepoint. Having your private network using a FQDN is not the optimum configuration, most employ .local or something to differentiate, but it is not a showstopper. Here is what I would do:

  First: set your DNS resolution on your registrar DNS config page; This is whoever you bought your DNS name from. Most have a web interface. Point the DNS name http://www.whateveryoubought.com to your ADSL static IP.

  Second: in your ADSL router set the port forwarding to point to your SharePoint host. If you have any other devices in line like a hardware firewall or router make sure they will pass port 80 and 443 requests from http://www.whateveryoubought.com to the SharePoint server as well.

  Third: it sounds like you have done this already but make sure you have your internal DNS record for http://www.whateveryoubought.com to your SharePoint server

  Fourth: in IIS>sites>edit bindings make you will need to add a site binding with your FQDN http://www.whateveryoubought.com pointing to the desired internal host port (most likely 80 or 443)

  here is a brief vid on AAM http://technet.microsoft.com/en-us/sharepoint/Video/ff679917

• matt said 3 months ago:

  I guess the way I have set the FW in IIS is not the best way as it circumvents the sharepoint structure and if for some reason you wanted to adjust authentication or manage subsites you would have fewer options at your disposal.