Re: ISA not authenticating....

From: Gabe Matteson (gmatteson_at_inquery.biz.nospam)
Date: 03/16/05 

Date: Wed, 16 Mar 2005 14:15:10 -0500

Thanks Jim,
    I created a protocol rule for tcp outbound 8080 named Web Proxy
Connections and now the logs show up as Web Proxy Connections. Thanks,
appreciate it.

"Jim Harrison (MSFT)" <jmharr@online.microsoft.com> wrote in message
news:uvu9rIbKFHA.2724@TK2MSFTNGP10.phx.gbl...
> This traffic isn't *through* ISA; it's *to* ISA.
> This is the client at 172.18.5.53 making connections to the web proxy
> listener on 172.18.1.9.
> This is normal traffic for web proxy clients.
> It shows as "unidentified" because the protocol/port combinaiton doesn't
> have a definition in the ISA protocol list.
> --
> --
> Jim Harrison [ISA SE]
> Read the help, books and articles!
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Gabe Matteson" <gmatteson@inquery.biz.nospam> wrote in message
> news:Oa2oK%23aKFHA.2724@TK2MSFTNGP10.phx.gbl...
> Here you go..
> 172.18.1.9 - isa internal interface. What else I don't understand is why
> the
> rule isn't showing up..
> I have a rule that states All Outbound AUTH - all outbound traffic from
> internal to external for all authenticated users...
>
> destination ip destination port protocol
> action rule client ip
> source network destination network
>
> 172.18.1.9 8080 unidentified ip traffic
> initiated connection 172.18.5.53 internal
> localhost
>
> (I have caching disabled right now)
>
>
> "Jim Harrison (MSFT)" <jmharr@online.microsoft.com> wrote in message
> news:%23LLVAzaKFHA.904@tk2msftngp13.phx.gbl...
>> Hi Gabe,
>>
>> That log data would be much more useful if you copied to a text file...
>>
>> --
>> --
>> Jim Harrison [ISA SE]
>> Read the help, books and articles!
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Gabe Matteson" <gmatteson@inquery.biz.nospam> wrote in message
>> news:eZU$kDaKFHA.1476@TK2MSFTNGP09.phx.gbl...
>> I created a rule that allows all outbound traffic for all authenticated
>> users. I look in the isa logging and it does not show a username. The
>> client
>> machine is a firewall, secure-nat and web proxy client... Does the
>> username
>> not show up for web pages and only shows up for when the firewall client
>> passes the connection to the firewall if a client is using a winsock
>> application such as a p2p or some other client application? I've attached
>> a
>> screenshot to show you the logs
>>
>>
>>
>>
>
>
>

Relevant Pages

  • Re: ISA not authenticating....
    ... I created a protocol rule for tcp outbound 8080 named Web Proxy ... Connections and now the logs show up as Web Proxy Connections. ... > This is the client at 172.18.5.53 making connections to the web proxy ...
    (microsoft.public.isa.configuration)
  • Re: ISA not authenticating....
    ... I created a protocol rule for tcp outbound 8080 named Web Proxy ... Connections and now the logs show up as Web Proxy Connections. ... > This is the client at 172.18.5.53 making connections to the web proxy ...
    (microsoft.public.isaserver)
  • Firewall access rule on ISA2004 for web proxy
    ... I need help getting the web proxy working for browsing the web. ... Connections to port 8080 get denied by a rule further down in the rule list ... All failed entries are client user anonymous. ...
    (microsoft.public.isa)
  • Re: VPN Site Client to access Internet
    ... In the connections tab of internet explorer select the vpn connection from ... > The remote office client need to access internet using main office's ISA ... > I have try a lot method(Firewall client and web proxy), ...
    (microsoft.public.isa)
  • RE: Force use of ISA Firewall Client
    ... You see three types of ISA 2004 firewall clients in ISA console, ... the system will use Web Proxy ... protocols, this need Firewall client. ...
    (microsoft.public.windows.server.sbs)