Welcome to ISAserver.org

`Web proxy for External Domains

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA 2006 Web Proxy] >> Web Proxy Client >> `Web proxy for External Domains

Page: [1]

Message

<< Older Topic Newer Topic >>

`Web proxy for External Domains - 20.May2008 5:29:45 AM

robertmi

Posts: 3
Joined: 19.May2008
Status: offline

I am a bit new to isa server so I hope my question is understandable.
My company is using isa on the local AD domein for webproxy. For a subsidiary company that has it's own AD (with no trust between the domains) we want to provide Internet access.
We also want to control and monitor the webaccess of the subsidiary company.
I tried to realise this by making a userset that gets the external domain info via LDAP. But this doesn't work for webproxy, only for Publishing of websites.
Is their someone out their who has experience with providing web access to external domains.

Post #: 1

Featured Links*

RE: `Web proxy for External Domains - 20.May2008 7:23:18 AM

elmajdal

Posts: 4959
Joined: 16.Sep.2004
From: Lebanese in Kuwait
Status: offline

hi,

check this : http://www.isaserver.org/tutorials/Providing-Branch-Office-Access-ISA-2006-Firewalls-Web-Proxy-Listener.html

HTH,
Tarek

_____________________________

Tarek Majdalani

MS Forefront Edge Security MVP
Website : http://www.elmajdal.net/ISAServer
New Section : http://www.elmajdal.net/Win2k8

(in reply to robertmi)

Post #: 2

RE: `Web proxy for External Domains - 20.May2008 8:53:12 AM

robertmi

Posts: 3
Joined: 19.May2008
Status: offline

Hi Tarek,

Thanx for your reply. I had a look at the http://www.isaserver.org/tutorials/Providing-Branch-Office-Access-ISA-2006-Firewalls-Web-Proxy-Listener.html

In the first instance I thought this will work for me until I read the following

One drawback of Integrated authentication is that both the ISA firewall and the user machines must be members of the same domain, or you must mirror the local user accounts on the ISA firewall or in the target domain in which the ISA Firewall participates.
For example, if the branch office computers are not domain members, you must have the user name and password information for all the users at each branch office and create accounts on the ISA firewall�s local SAM that mirror those user accounts or mirror those accounts in the main office Active Directory domain. This can lead to significant administrative overhead, depending on how you enforce password change policy for branch office users.

In my senario the ISA server and the user machines are in a separate domain. This will mean that I have to miror the accounts of about 1000 accounts. The accounts are no problem but passwords is a no go.

(in reply to elmajdal)

Post #: 3