XP can't resolve OWA site

  • Thread starter Thread starter Chris Hall
  • Start date Start date
C

Chris Hall

Greetings,

I have an XP Pro box with sp2. It's joined to the domain and ip is correctly
configured through dhcp. When I open Internet Explorer and type in
https://server/exchange, I get 'page can't be found'. I can ping the server
by name. I checked for any weird Explorer settings, but found none. Nothing
should be blocking this. Also, tried back reving the nic driver. This
machine is on the same local network as the server and also has entries in a
host file. This is probably more of an Exchange thing, but thought I'd start
here. Any thoughts?
 
In
Chris Hall said:
Greetings,

I have an XP Pro box with sp2. It's joined to the domain and ip is
correctly configured through dhcp. When I open Internet Explorer and
type in https://server/exchange, I get 'page can't be found'. I can
ping the server by name. I checked for any weird Explorer settings,
but found none. Nothing should be blocking this. Also, tried back
reving the nic driver. This machine is on the same local network as
the server and also has entries in a host file. This is probably more
of an Exchange thing, but thought I'd start here. Any thoughts?

Hi Chris.

With the info you provided, it's pretty much guesswork at this point.

This sounds *possibly* more of a number of other things than an Exchange
thing, provided you can connect to OWA from the local Exchang server.

But then again, it may be depended on if you correctly configured the SSL
cert (public or private CA?), if you have a hostheader configured for the
website in IIS, is WINS being used in a multi-subnetted environment (because
you are attempting to connect via the NetBIOS name of the machine) and if
the name "server" (as per your description) is entered in the WINS database,
if you have multiple Exchange servers and trying to connect thru the FE,
what DNS server is the XP machine configured with in it's IP properties
(assuming ONLY the internal DNS server hosting the AD zone, as what it
should be and not an ISP's DNS), is "server" a CNAME (which makes it a bit
more difficult to configure), etc etc etc etc....

And what are you doing with hosts files? Let DNS centrally manage all your
host records. Hosts files are basically administrative overhead, and are
legacy.

So you see, a better description of your infrastructure, if SSL is
configured, if it works on another machine and not this specific machine,
what hostheader is being used in the default website's properties, are there
other websites on the machine other than the default, FE/BE, etc, an
ipconfig /all of the client and of the Exchange server, if using WINS, would
be helpful to diagnose this.

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

If you are having difficulty in reading or finding responses to your post,
instead of the website you are using, if I may suggest to use OEx (Outlook
Express or any other newsreader of your choosing), and configure a newsgroup
account, pointing to news.microsoft.com. This is a direct link into the
Microsoft Public Newsgroups, and it is FREE and DOES NOT require a Usenet
account with your ISP. With OEx, you can easily find your post, track
threads, cross-post, and sort by date, poster's name, watched threads or
subject.

Not sure how? It's easy:
How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Windows Server Directory Services
Microsoft Certified Trainer
Assimilation Imminent. Resistance is Futile.
Infinite Diversities in Infinite Combinations.
=================================
 
Ace Fekay [MVP]"
In

Hi Chris.

With the info you provided, it's pretty much guesswork at this point.

This sounds *possibly* more of a number of other things than an Exchange
thing, provided you can connect to OWA from the local Exchang server.

But then again, it may be depended on if you correctly configured the SSL
cert (public or private CA?), if you have a hostheader configured for the
website in IIS, is WINS being used in a multi-subnetted environment (because
you are attempting to connect via the NetBIOS name of the machine) and if
the name "server" (as per your description) is entered in the WINS database,
if you have multiple Exchange servers and trying to connect thru the FE,
what DNS server is the XP machine configured with in it's IP properties
(assuming ONLY the internal DNS server hosting the AD zone, as what it
should be and not an ISP's DNS), is "server" a CNAME (which makes it a bit
more difficult to configure), etc etc etc etc....

And what are you doing with hosts files? Let DNS centrally manage all your
host records. Hosts files are basically administrative overhead, and are
legacy.

So you see, a better description of your infrastructure, if SSL is
configured, if it works on another machine and not this specific machine,
what hostheader is being used in the default website's properties, are there
other websites on the machine other than the default, FE/BE, etc, an
ipconfig /all of the client and of the Exchange server, if using WINS, would
be helpful to diagnose this.
Hi Ace,

Thanks for the reply. The situation mysteriously resolved itself. Don't know
how....
 
In
Chris Hall said:
Hi Ace,

Thanks for the reply. The situation mysteriously resolved itself.
Don't know how....

Maybe a restart or something else?

Since it's now working, if it ain't broke, don't fix it.
:-)

Ace
 
Back
Top