Web Proxy does not listen to Dial up connection unless the Dial up is started first
- From: "Mark Davis" <ycibu@xxxxxxxxxxx>
- To: isalist@xxxxxxxxxxxxx
- Date: Sun, 2 Jun 2002 15:26:30 -0600
G'Day,
I have spent two day's trying to solve this but to no avail. Hopefully
someone will have some answers.
I have both ISA and IIS running on a 2000 Server box. I have a couple of
websites running on IIS. I have followed all (and I really do mean ALL)
the steps from Tom Schinders book (and other sources) on Publishing
websites where IIS and ISA exist on the same box.
I have set all the IIS sites to listen on ports other than 80 on the
internal IP address. I have created destination sets in ISA for each FQDN
that point to my server. I have created web publishing rules for each of
these sets that point to the port for each site. All out bound access
works fine.
Now the problem arises (and it took me nearly a day and a half to identify
this) when the Server starts up. On a reboot it starts all the ISA
services first (including the Web Proxy Service), then it starts the Dial
up connection secondly (It automatically does it because I have a dynamic
DNS updater that runs on startup and forces ISA to make the initial
connection). This is fine and works for outward browsing. HOWEVER when I
try to connect to any of my internal sites via their FQDN from a PC over
the internet it throws up 10061 connection refused errors.
I have discovered however that if I have the dial up connetion connect
BEFORE the Web Proxy (i.e. Set the Web Proxy service to manual, dial the
connection, then start the service) it works beautifully. I can connect to
every one of my sites from the internet.
Now I COULD live with this if I had to BUT I want to know why this would
be so? I have ensured that USE DIAL-UP ENTRY is ticked in both the Default
Routing Rule and Firewall chaining sections of Network Configuration.
Another way of verifying exactly what is happening is in the event log.
Once the Dial up is connected and the Web Proxy Service is started, if I
then disconnect the Dial up an entry appears in the Application Log
stating that "The Web Proxy service identified that the address *.*.*.*
(my dial up IP address) was removed from the interface table and stopped
listening on port 80".
If I then reconnect it gives a similar message saying that it has started
listening on port 80 again. This is good as it indicates that the Web
Proxy is paying attention to what is happening with the Dial up
connection.
HOWEVER when I start the Web Proxy service then the Dial up NO SUCH
ENTRIES are made in the event log. No matter how many times I disconnect
and reconnect the dial up connection the application log never gives me
any more messages from the Web Proxy service......
So after that rather long story my question is: Has anyone else found that
they have to connect the dial up connection before the Web Proxy Service
or it WILL NOT listen to incoming requests?
I know how to get round it in a sloppy way but would rather know if there
is a proper way.
Cheers,
Mark Davis
Other related posts:
- » Web Proxy does not listen to Dial up connection unless the Dial up is started first
