RE: ISA Not allowing clients to browse

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Michael (Michael_at_discussions.microsoft.com)
Date: 02/25/05 

Date: Fri, 25 Feb 2005 10:03:05 -0800

Followup: I have messenger working properly now from the server and
"somewhat" from the clients. I can now log into messenger on the workstation
but when i send a message to an outside contact it only goes through about 2
out of 5 tries. Same applies when sending from a remote user to the network
workstation, sometimes it gets there, most times it does not. The
administrator on the server gets and sends just fine?

"Michael" wrote:

> Hi Cliff,
> Thanks again for your suggestions. After deleting the extra "allow" rules,
> (there were 3 setup during install), I did the exclusions and created a
> seperate allow rule for the subject group and it worked as it should. I guess
> there was some conflict with the other "allow" rules. ? Still have two small
> hurdles to overcome, now I cannot reach windows messenger even though i have
> added the protocal and opened the ports. The message i get from the server is
> I dont have the correct username and password for the proxy server
> (integrated auth). From the workstation, it just says there is a problem with
> the internet connection. The second problem is when using OWA (from a
> remote), the interface display is not correct, it is like parts are missing
> and there are blue lines around links. Also, i cannot reach the OWA from
> within the network either from a server or workstation, it won't accept my
> password.
> I will be researching these in the newsgroups, but if you have a suggestion
> or two, I would greatly appreciate it.
> Thanks again for your suggestions, they were on the mark!!
> Michael
> ""Cliff Zhang [MSFT]"" wrote:
>
> > Hi Michael,
> >
> > Thank you for your update!
> >
> > I reviewed the whole thread and found you installed ISA after you have
> > configured things up so I'd like to know if you have run through CEICW
> > again after the installation of ISA. If not, you would rerun it with all
> > settings touched excluding the Exchange configurations.
> >
> > At this time, i suggest you do the following steps:
> >
> > 1. Open ISA Management.
> >
> > 2. Create a Destination Set in Policy Elements | Destination Set, and then
> > add the permitted sites into it.
> >
> > 3. Point to Access Policy | Site and Content Rule, delete any rules that
> > allow all outgoing traffic.
> >
> > 4. Double click BackOffice Internet Access Site and Conent Rule, click
> > Apply To tab, click Add button under Exceptions, and then add the user
> > groups that you want to give them limited access.
> >
> > 5. Create the following Site and Content Rule:
> >
> > Rule Name: Allow only permitted sites
> > Destinations: <select the Desntination Set created in Step 2>
> > Applies to: the user groups that you want to give them limited access.
> >
> > 6. Restart the Web Proxy service. Does it work?
> >
> > Please do not hesitate to let me know if you have any further concerns.
> >
> > Sincerely,
> >
> > Cliff Zhang
> > Microsoft Online Partner Support
> > MCSE 2000/2003
> >
> >
> > When responding to posts, please "Reply to Group" via your newsreader so
> > that others may learn and benefit from your issue.
> >
> > =====================================================
> >
> > Business-Critical Phone Support (BCPS) provides you with technical phone
> > support at no charge during critical LAN outages or "business down"
> > situations. This benefit is available 24 hours a day, 7 days a week to all
> > Microsoft technology partners in the United States and Canada.
> >
> >
> > This and other support options are available here:
> >
> > BCPS:
> > https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
> >
> > Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/
> >
> >
> > If you are outside the United States, please visit our International
> > Support page:
> > http://support.microsoft.com/default.aspx?scid=%2finternational.aspx.
> >
> > =====================================================
> >
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> >
> >
> >
> >

Relevant Pages