Re: Web Listeners

Hi Aman,

My recommended setup is to install the Firewall client on all Windows
client machines and configure all Web browsers as Web Proxy clients. Do
not install the Firewall client on servers, and make the Servers Web
Proxy clients depending on how you manage them. I would make them Web
Proxy clients "just in case", as you can force authentication for any
user who 'happens' to log onto the server, provides an account based
audit trail. 

HTH,
Tom 

-----Original Message-----
From: Aman Bedi [mailto:gurkirpal.bedi@xxxxxxxxxxx] 
Sent: Monday, September 13, 2004 2:43 PM
To: [ISAserver.org Discussion List]
Subject: [isalist] Re: Web Listeners

http://www.ISAserver.org

Cool,

Thanks Jim 

Now I know how it works for firewall clients. ;)

Thanks 

About the 2nd part of question addressed to Tom, everyone else is also
requested to comment 

------------------------------------------------------------------------
----
------------------------------------------------------------------------
----
-----------------------------------

-----Original Message-----
From: Jim Harrison [mailto:jim@xxxxxxxxxxxx]
Sent: Monday, September 13, 2004 3:28 PM
To: [ISAserver.org Discussion List]
Subject: [isalist] Re: Web Listeners

http://www.ISAserver.org

Read this:
http://isaserver.org/tutorials/You_Need_to_Create_a_Split_DNS.html

There's no gain to using an external listener to reach an internal
resource...

  Jim Harrison
  MCP(NT4, W2K), A+, Network+, PCG
  http://isaserver.org/Jim_Harrison/
  http://isatools.org
  Read the help / books / articles!

----- Original Message -----
From: "Aman Bedi" <gurkirpal.bedi@xxxxxxxxxxx>
To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx>
Sent: Monday, September 13, 2004 12:07
Subject: [isalist] Web Listeners


http://www.ISAserver.org

Hi everyone.

 

I have published 2 webservers on our internal domain.

 

When someone accesses the sites from outside they work fine.

>From internal network, I can access the sites thru local ip, but
doesn't
work thru website name or public ip . (securenat clients)

 

It works fine for Firewall clients . 

Any ides ?

 

ALSO 

 

tom, 

whish one is better, to force a client to be firewall client or to force
them to be proxy client?

i read in ISA 2004 "firewall client credentials are forwarded to the web
proxy service".

This is unlike ISA 2000 .right ?

that means if i force users to be firewall clients only, then i can have
rules based on user credentials ...( which was not possible is isa 2000,
as
u said in ur article that to do so we should force clients to be proxy
clients)

please clarify this point.

Thanks

 

 

 

 



------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=isalist
ISA Server Newsletter: http://www.isaserver.org/pages/newsletter.asp
ISA Server FAQ: http://www.isaserver.org/pages/larticle.asp?type=FAQ
------------------------------------------------------
Other Internet Software Marketing Sites:
World of Windows Networking: http://www.windowsnetworking.com
Leading Network Software Directory: http://www.serverfiles.com
No.1 Exchange Server Resource Site: http://www.msexchange.org
Windows Security Resource Site: http://www.windowsecurity.com/
Network Security Library: http://www.secinf.net/
Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com
------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as:
jim@xxxxxxxxxxxx
To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=isalist
Report abuse to listadmin@xxxxxxxxxxxxx


------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=isalist
ISA Server Newsletter: http://www.isaserver.org/pages/newsletter.asp
ISA Server FAQ: http://www.isaserver.org/pages/larticle.asp?type=FAQ
------------------------------------------------------
Other Internet Software Marketing Sites:
World of Windows Networking: http://www.windowsnetworking.com
Leading Network Software Directory: http://www.serverfiles.com
No.1 Exchange Server Resource Site: http://www.msexchange.org
Windows Security Resource Site: http://www.windowsecurity.com/
Network Security Library: http://www.secinf.net/
Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com
------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as:
gurkirpal.bedi@xxxxxxxxxxx
To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=isalist
Report abuse to listadmin@xxxxxxxxxxxxx



------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=isalist
ISA Server Newsletter: http://www.isaserver.org/pages/newsletter.asp
ISA Server FAQ: http://www.isaserver.org/pages/larticle.asp?type=FAQ
------------------------------------------------------
Other Internet Software Marketing Sites:
World of Windows Networking: http://www.windowsnetworking.com
Leading Network Software Directory: http://www.serverfiles.com
No.1 Exchange Server Resource Site: http://www.msexchange.org
Windows Security Resource Site: http://www.windowsecurity.com/
Network Security Library: http://www.secinf.net/
Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com
------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as:
tshinder@xxxxxxxxxxxxxxxxxx
To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=isalist
Report abuse to listadmin@xxxxxxxxxxxxx




Other related posts: