Fw: ISA Server 2004 Issues Followup
- From: "vesterby@xxxxxxxx" <vesterby@xxxxxxxx>
- To: isalist@xxxxxxxxxxxxx
- Date: Mon, 13 Sep 2004 14:15:39 GMT
I tried implementing the suggestions that both Jim and Tom made to resolve the
Java app issue, but none of them worked. It seems the only way I'm going to
resolve this is to give the java app users static IP addresses, create a
separate network object with those IP addresses with authentication turned off,
and then create a new access rule with the new network object. Any other
suggestions on that?
I have another issue. My company wants me to implement Microsoft SUS and RIS
on the same box as ISA Server 2004. I found out that SUS listens on port 80,
is dependent on IIS, and can't be changed (according to Microsoft). Any
problems with reconfiguring the ISA server listeners to listen on ports other
than port 80 to avoid potential conflicts? Thanks.
---------- Forwarded Message ----------
Recall that I mentioned we are currently using Proxy Server 2.0 and are going
to get rid of it in favor of ISA Server 2004. When we addressed the java
application issue for Proxy 2.0, we fixed the problem by installing the Proxy
Client software on the client's workstations. This enabled the users to
connect to the java application via Winsock and everything worked. The
authentication issue didn't matter.
In order to fix this issue, isn't there a way to do something similar in ISA
Server 2004? I did try installing the Firewall Client software on my
workstation and attempted to access the java application with that, but it
didn't work. Should I explore the option of using SecureNat? I appreciate the
help.
________________________________________________________________
Get your name as your email address.
Includes spam protection, 1GB storage, no ads and more
Only $1.99/ month - visit http://www.mysite.com/name today!
Other related posts:
