You may have to check the IIS Metabase itself. If a stale IP address is stuck, it may not show in the IIS GUI.
The IIS Resource Kit has some good tools - or you can mark the Metabase readable and search the XML for the old IP address. --James On Tue, Aug 5, 2008 at 9:28 AM, Miller Bonnie L. <[EMAIL PROTECTED]> wrote: > We've seen something like this (an old IP sticking around) when changing > addresses with IIS before. A couple of places I can think to check on the > server that had the previous IP— > > > > IIS Admin, properties of the website, web site tab. Make sure the IP > address has not been assigned directly to the old IP at some point. Click > the "advanced" button to confirm it does not show up. > > > > Control Panel, Network, properties of the NIC, TCPIP properties, advanced, > IP Settings tab. Make sure the second IP does not still show up here, and > remove it if it does. > > > > -Bonnie > > > > From: E. Peeters [mailto:[EMAIL PROTECTED] > Sent: Monday, August 04, 2008 1:43 PM > To: MS-Exchange Admin Issues > Subject: RE: Strange OWA redirection > > > > I have, and I didn't find either. What has me puzzled is that a "mere" > Refresh solves this issue every time. > > > > ________________________________ > > From: May, Jeff [mailto:[EMAIL PROTECTED] > Sent: Monday, August 04, 2008 3:15 PM > To: MS-Exchange Admin Issues > Subject: RE: Strange OWA redirection > > Have you checked for DNS issues or hard coded IP on the default web site for > your OWA FE server???? > > > > Jeff A. May, Blackberry Certified SA > Client Server Engineer III > Client Server Engineering/IT Messaging Services > Mail Code - 100-99-08-20 > E-Mail - [EMAIL PROTECTED] > > > > From: E. Peeters [mailto:[EMAIL PROTECTED] > Sent: Monday, August 04, 2008 4:10 PM > To: MS-Exchange Admin Issues > Subject: Strange OWA redirection > > > > Hello people, > > > > My problem is with Exchange 2003 on Windows 2003. > > > > Whenever someone attempts to access my OWA for the first time (per session), > the connection is being redirected to an internal (non-routable) IP. Hitting > Refresh on the browser opens OWA correctly, and the problem does not occur > again until the user begins a new session (logs off or reboots their PC). > > > > The IP is the internal IP that the Exchange box was assigned in an earlier > deployment, prior to OWA being made available. The Exchange box has a new IP > and everything seems to be functioning normally, except for this OWA issue. > > > > On the first attempt to connect to OWA, the user is prompted to authenticate > and after succesfully doing so, both OWA frames are loaded but their > respective content isn't displayed. Rather, the generic "web page could not > be found" is shown. Looking at what each frame does, they are both > attempting to load their respective page, but they use the old internal IP > for Exchange rather than the FQDN. > > > > If the user hits Refresh, the content of each frame is loaded using the FQDN > and OWA will function as expected right up until the user logs off or > reboots their PC. Afterwards, the first attempt to use OWA will again fail, > etc... > > > > I have combed the registry to see if I could find any entry that would > somehow point to the old Exchange's internal IP, to no avail. > > > > This issue started when one box was performing all Exchange functions. I now > have front-end and back-end boxes, but the problem hasn't changed. > > > > Any suggestion ? > > > > Eric > > > > > > > > > > > > > > ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~
