[AccessD] WAY OT: Reporting Services - Publically available

Hi Stuart
Yep way over my head
I'll forward this to the nerds and hope they know what it means
Thanks heaps for taking the time to look this stuff up and replying with a
personalised touch :-)
Many thanks

Darren


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan
Sent: Friday, 10 December 2010 8:41 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] WAY OT: Reporting Services - Publically available

In general:

1. Make sure that your in house web server is NOT configured to only accept
connection from local IP addresses.

2.  Set up Port forwarding on your internet facing router to forward port 80
to your in house web server.

3. Set up an A record on your S.O.A  DNS server pointing  something like
reports.activebilling.com.au to the public IP address of your internet
facing router.

Your  current A and MX records point to 122.201.83.166 which is your public
web host and 
your mustang.turboservers.com.au mail server.   If these are both hosted
internally, that is 
the address you need to point reports.activebilling.com.au to.  If your mail
and web site are both hosted externally, you will have to find the external
address of your internet router ( note tha if your ISP provides a dynamic IP
address for you, you may need to pay them a bit extra to provide a static
address which you can point to.)


--
Stuart


On 10 Dec 2010 at 15:21, Darren - Active Billing wrote:

> Hi Team
> 
> 
> 
> Apologies for the OT Post - It's a brains trust question. Feel free to 
> respond to my personal address.
> 
> 
> 
> We use reporting services over SQL 2005 dBs here at the office.
> 
> People VPN in and they can then essentially spark up the reporting 
> services webpage using http://localdbname/reports
> 
> All good as the VPN logons are the active directory logons so they use 
> the same credentials
> 
> So they are presented with a reporting services logon and it's the 
> same as their VPN logon - So off they go
> 
> Simple
> 
> 
> 
> We now need to make Reporting Services available publically.
> 
> So the http://someserver/reports need to be available from any machine 
> in the world.
> 
> Then when it's entered we need the standard logon reporting services 
> screens need to be presented
> 
> 
> 
> I have no clue on this stuff - it's way over my head and I suppose I 
> need a network gurus assistance
> 
> Can anyone advise what's required to make the reporting services pages 
> we have here available publically rather than through a VPN? I 
> appreciate my descriptions on environment etc. are vague
> 
> 
> 
> Thanks heaps in advance
> 
> 
> 
> Darren
> 
> 
> 
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> 


-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com