The latest version of the Exchange 2007 update is Update Rollup 5 for Exchange Server 2007 - this can be downloaded from here (64 bit and 32 bit versions now available).
Microsoft plan to do these releases rather than issue hotfixes as the method of engineering Exchange has changed since the previous versions, and KB937194 describes why this is. Each update rollup contains all the previous updates, so you only need to deploy this patch and not any earlier patches as well.
If you have not yet installed Exchange 2007 yet, copy this patch to the Update folder on your installation point and it will get slipstreamed into the installation automatically upon running Setup.
Note that unlike updates #1 and #2, a 32bit version of this update is available so this update can be applied to test and virtual computer systems and labs.
Friday, October 26, 2007
Wednesday, October 03, 2007
Error Code: 500 Internal Server Error. The network logon failed. (1790)
This is an error visible in the web browser when connecting to a HTTPS web site behind an ISA Server.
The problem is that the firewall access rule for this web site in ISA Server is forwarding the requests to an internal server on a port that it is not listening on. For example you connect to https://server.example.com and the ISA Server forwards this request to http://internalsrv. On the Bridging tab check that the mentioned port(s) are actually working on the internal server. For example if you are listening in ISA Server on 443 for a SSL connection and the SSL/HTTPS port is ticked make sure that the port is 443, and that the web server internally is listening on 443. If its another number make sure that it is meant to be the other number and not really 443 or not ticked at all. Ditto for the HTTP port, which is 80 by default.
The problem is that the firewall access rule for this web site in ISA Server is forwarding the requests to an internal server on a port that it is not listening on. For example you connect to https://server.example.com and the ISA Server forwards this request to http://internalsrv. On the Bridging tab check that the mentioned port(s) are actually working on the internal server. For example if you are listening in ISA Server on 443 for a SSL connection and the SSL/HTTPS port is ticked make sure that the port is 443, and that the web server internally is listening on 443. If its another number make sure that it is meant to be the other number and not really 443 or not ticked at all. Ditto for the HTTP port, which is 80 by default.
Subscribe to:
Posts (Atom)