Changing to non-standard port

 >-----Original Message-----
 >On Tue, 24 Feb 2004 21:59:01 -0800, "TJH"
 ><anonymous.TakeThisOut@discussions.microsoft.com> wrote:

 >Well, PHP runs fine on IIS and ASP can sort of run on
Apache...

Hmm. I ran into scripting errors using PHP on IIS until I
switched. Eh, something to look at later on...


 >A second IP works easier, but there's no reason a non-
standard port
 >shouldn't work on IIS with an Access database. Access
doesn't care
 >what port IIS uses, and doesn't need a port of its own.

Ok, here's what I have done. I shutdown Apache, and
restored IIS to use port 80. Since it was my first time
running DAPs, I wanted to run through the instructions to
the key. Using the following configuration:

3 tier config - Windows Challenge/Response Authentication
to the DAP, set the dbase to readonly in the msdfmap.ini
config, and verified the MSADC virtual directory
settings. Typed in the url
(http://website.com/dappage.htm) and it worked flawlessly.

So, with the structure working, I changed website (thru
IIS) to use a non-standard port (8080) and went back to
the URL (now, <a style='text-decoration: underline;' href="http://website.com:8080/dappage.htm" target="_blank">http://website.com:8080/dappage.htm</a>). This
time, it gives me "Internet Client Error : cannot connect
to server".

The structure of the DAP page comes up, but will not
connect to the database. However, if I set IIS back to
use port 80, it works fine again.

What you're saying makes perfect sense, since Windows
Challenge/Response Auth works fine on any port I set IIS
to use and the dbase is running "internally" to the web-
server (so it wouldn't need a port).

Hope this provides some more info.

Thanks<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Changing to non-standard port