Trying to configure access (from internal) to a website in the DMZ that uses port 2002. I have a web access rule (for http, https) that allows Internal access to Perimeter. I have a protocol rule for port 2002 that allows access from Internal to Perimeter.
My logs show Initiated Connection for the protocol rule, but my client browser simply times out on the page. What am I missing? Internal to Perimeter is setup to ROUTE traffic.
Both web proxy and firewall clients. If we disable the firewall client, it works. I was just wondering if there was a way to do it without the extra step for the users.
You can create a new protocol definition for the new protocol and then create an Access Rule that will allow Firewall and SecureNAT clients to access the site on the alternate port. The Web proxy client doesn't require this because all it knows is that you're allowing access to HTTP, so the port number is irrelevant.
I have an access rule that allows the protocol definition (configured as outbound 2002) from Internal to Perimeter for the specified user (Active Directory) groups who need access.
Do I need to do something extra to 'allow Firewall and SecureNAT clients to access the site'?
Still only works with firewall client disabled. If it's enabled, the site times out within the browser.
My bad. I had a local exception setup in my proxy settings to bypass that adddress. That's why it was working. When I remove that address from any bypass list, it does not work no matter what I enable/disable on the client.
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Printable Version
All Forums >> [ISA Server 2004 Firewall] >> DMZ >> DMZ website with unique port 
DMZ website with unique port - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread