RE: ISA Not allowing clients to browse

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Brandy Nee [MSFT] (v-branee_at_online.microsoft.com)
Date: 02/28/05 

Date: Mon, 28 Feb 2005 07:00:42 GMT

Hi Michael,

Thank you for the update.

Since this is a random issue, I'm not sure whether it is caused by ISA or
MSN Messenger. At this point, I recommend you to contact MSN support or ISA
PSS support/Partner Newsgroup Support (If you're a partner of Microsoft).

Then, they will analyze the log files and collect necessary info to
continue troubleshooting this issue.

To contact MSN Support:
http://support.msn.com

To contact PSS:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS

[Note] If you are outside the US please see http://support.microsoft.com
for regional support phone numbers.

If you're a Partner, you can also post this question in Partner newsgroup.

Thank you for your understanding. If there's something else we can do for
you, please feel free to post back.

Bill Peng
MCSE 2000, MCDBA
Microsoft Partner Support Professional

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
>Thread-Topic: ISA Not allowing clients to browse
>thread-index: AcUbZEFH4hhUuvsLS1mI6lgICWEtLA==
>X-WBNR-Posting-Host: 205.161.228.186
>From: "=?Utf-8?B?TWljaGFlbA==?=" <Michael@discussions.microsoft.com>
>References: <3E277606-4BC3-418B-AD98-706B0E0D78F8@microsoft.com>
<ccO5YzJGFHA.400@TK2MSFTNGXA02.phx.gbl>
<2973C69E-1372-45D2-AA92-C3C5FD452FB6@microsoft.com>
<dsYEoiWGFHA.2808@TK2MSFTNGXA02.phx.gbl>
<011C36E5-BC1D-48FA-8103-59282E4DF302@microsoft.com>
<R60MDBwGFHA.2568@TK2MSFTNGXA02.phx.gbl>
<1C603DBF-FA7E-447A-810D-C65EC36DC4AC@microsoft.com>
>Subject: RE: ISA Not allowing clients to browse
>Date: Fri, 25 Feb 2005 10:03:05 -0800
>Lines: 99
>Message-ID: <580CD291-5514-42F4-BD79-0E55AF6A341E@microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.windows.server.sbs
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
>Path: TK2MSFTNGXA02.phx.gbl!cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:149710
>X-Tomcat-NG: microsoft.public.windows.server.sbs
>
>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.
>> >
>> >
>> >
>> >
>

Quantcast