Re: Requiring Authentication Kills Symantec for Exchange Live Updates



To configure HTTP settings for LiveUpdate

1 On the Windows menu, click Start > Control Panel.

2 In the Control Panel window, double-click Symantec LiveUpdate.

3 In the LiveUpdate Configuration dialog box, on the HTTP tab, click I want
to

customize my HTTP settings for LiveUpdate.

When this setting is checked, the Use a proxy server for HTTP connections

option appears and is checked by default.

4 In the Address box, type the IP address of the HTTP proxy server.

5 In the port box, type the port number.

Typically, the port number for HTTP is 80.

6 Click I need authorization to connect through my firewall or proxy server

when a user name and password are required to access the HTTP proxy

server, under HTTP Authentication, and then type the user name and

password.

7 Click OK.

ftp://ftp.symantec.com/public/english_us_canada/products/sym_mail_security/5.0_mse/manuals/sms_imp_guide.pdf



page 219

"Alan" <alan@xxxxxxxxx> wrote in message
news:uPnLuanwGHA.4616@xxxxxxxxxxxxxxxxxxxxxxx

Hi All,

I have an issue whereby, if I turn on the requirement for clients to
authenticate through the ISA Server, it seems to kill the live updates of
Symantec Mail Security for Exchange Server.

I am turning on the option to require authentication as follows:

ISA Server Management - MyServer - Configuration - Networks
Select the 'Internal' network (in my case this is 10.0.0.0/24)
Tasks - Edit selected network
Web Proxy Tab
Authentication
Click the box to 'Require all users to authenticate'

I am guessing that Live Update is trying to make an anonymous connection
and this is failing. Has anyone else encountered this problem? I have,
and will continue to, investigate via Symantec but I fugured someone in
ISAServer land might have come up with a solution already?

Thanks,

Alan.
--

The views expressed are my own, and not those of my employer or anyone
else associated with me.

My current valid email address is:

1bupdvc02@xxxxxxxxxxxxxx

This is valid as is. It is not munged, or altered at all.

It will be valid for AT LEAST one month from the date of this post.

If you are trying to contact me after that time,
it MAY still be valid, but may also have been
deactivated due to spam. If so, and you want
to contact me by email, try searching for a
more recent post by me to find my current
email address.

The following is a (probably!) totally unique
and meaningless string of characters that you
can use to find posts by me in a search engine:

ewygchvboocno43vb674b6nq46tvb






.



Relevant Pages

  • RE: Outlook RPC over HTTp deosnt work
    ... try to use RPC over HTTP to connect the Exchange Server. ... What SBS is running on the problematic Server? ...
    (microsoft.public.windows.server.sbs)
  • Re: RPC over HTTP
    ... I will help you with the PRC over Http issue in this thread. ... and go through the Internet option. ... On the Web Server Certificate page shows. ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: RPC over HTTP
    ... Are there any other ways of configuring the RPC over HTTP? ... Outlook Web Access, Business Website and so on. ... On the Web Server Certificate page shows. ...
    (microsoft.public.windows.server.sbs)
  • Re: MSAS Licensing Part II
    ... wish to use http access then you must have Enterprise Edition. ... PTS looks at the server name. ... You will note that all of this is totally transparent to the client. ...
    (microsoft.public.sqlserver.olap)
  • Re: RPC over HTTP Question
    ... allow specific traffic transfer and publish some web services to internet. ... On the Web Server Certificate page, ... The wizard automatically configures Exchange, IIS, and the RPC proxy ... >Subject: Re: RPC over HTTP Question ...
    (microsoft.public.windows.server.sbs)

Loading