Redirecting http requests from new users to a local site

i am trying to redirect http requests of new users of my network to a local site on the pc with BWM installed. I did everything the help document says
Unfortunately, after everything, only internet explorer was redirected.Opera and firefox weren't. they give a reply that it is a never ending request.
IE however works one moment and the next moment it doesn't.

Well, the software is not entirely foolproof I assume the IIS web-server is installed on the same computer with BWM. It seems the web-browsers end-up with an infinite redirection loop.

Here's why:

1. A client 192.168.0.x is trying to access Google, for example.
2. His request is coming through BWM and is being trapped by the "Redirect" rule.
3. BWM is replying with a HTTP reply 302 and redirected the client to the local web-site
4. If the local web-site sits on the BWM computer, the newly initiated request (due to the redirection) is coming through BWM again, and then steps 2 to 4 run infinitely.

In order to input Not local, simply specify 'Local host' at the Destination tab, and then check 'Invert destination address' at the Advanced tab. Link this rule with the port mapping.

Update: I just forgot to mention that you will also have to add a rule explicitly allowing connections to the local host port 80, otherwise the blocking rule at the end will reject the redirection. So, add one more rule (not linked to a port mapping) above the "Redirect" rule:

I don't understand what you are suggesting...
Typically the web site to be redirected to is NOT on the BWM PC. So if I want 192.168.1.100 ( a customer behind my firewall ) to have his port 80 web request ( to any external web site ) to be redirected to a web server on 192.169.1.200
What rules do I set up? Is there an actual "redirection" rule -- or you just suggesting calling (naming) the rule "redirection" or "redirect".

Is this type redirection really a function that I can do with the latest production release?

a) If the web-site is on the customer side, so he can access the web-server without going through the BWM PC, then this can be done with a simpler rule. Define a port mapping as shown below and a corresponding rule:

This merely instructs BWM to reroute a HTTP request from the user and reply with HTTP code 302, taking him to the URL specified in the mapping. Finally the user's browser makes a HTTP request to 192.169.1.200 and receives whatever content you put there.

b) If the web-site is on the other side of the BWM PC, so accessing 192.169.1.200 is only possible through the BWM PC, things get slightly more complex. You need to add an exception in the rule, to make requests to 192.169.1.200 itself not redirected. Otherwise, you will end up with an infinite loop. Therefore, we need to make the rule as follows:

This rule is just like the first one, yet it ignores any requests to 192.169.1.200. In order to implement Not, enter 192.169.1.200 as the destination address and then on the advanced tab check Invert destination address.

Hope this helps. If anything remains unclear, please ask.

P.S. This thread could celebrate an anniversary, it is exactly one year old