S
SDavis
Hello there,
I am running ISA 2006 STD on a Windows 2003 R2 w/sp2 STD server that is
sitting behind a Cisco PIX firewall. Before the PIX security settings were
implemented it was allowing traffic via port 443 and port 3389 through. This
allowed users via MSIE from the outside to authenticate through the ISA
server which would allow access to a dedicated terminal server which they
could log into. Now the only access the Cisco PIX firewall is via port 443.
When this happened the users could still authenticate in through the ISA
server and access the Remote Desktop Web Connection page, type in the name of
the server and click on connect, however at the next screen where the remote
desktop is supposed to be displayed it times out with an error message
stating something to the effect that the session could not be established due
to an issue with the network.
So the question is what needs to happen to allow Remote Desktop Web
connection to function with the current PIX firewall restrictions in place?
Thanks,
I am running ISA 2006 STD on a Windows 2003 R2 w/sp2 STD server that is
sitting behind a Cisco PIX firewall. Before the PIX security settings were
implemented it was allowing traffic via port 443 and port 3389 through. This
allowed users via MSIE from the outside to authenticate through the ISA
server which would allow access to a dedicated terminal server which they
could log into. Now the only access the Cisco PIX firewall is via port 443.
When this happened the users could still authenticate in through the ISA
server and access the Remote Desktop Web Connection page, type in the name of
the server and click on connect, however at the next screen where the remote
desktop is supposed to be displayed it times out with an error message
stating something to the effect that the session could not be established due
to an issue with the network.
So the question is what needs to happen to allow Remote Desktop Web
connection to function with the current PIX firewall restrictions in place?
Thanks,