×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I have just come across something that leaves me not even sure what
terms to Google for.
New customer has an Exchange Server 2003 behind a router that only
allows incoming https. The server is using a self signed certificate.
The DNS is provided by their ISP, uses a static IP, however the RDNS
returns the ISP's domain not the customer's. I am working on getting the
ISP to change the RDNS.
Outside users have been able to use
https://www.customer.domain/exchange/ to access their email.
Now some (not all) users are getting a "Server not found page." If the
user does a nslookup on the domain and then substitutes the IP for the
domain they get the Exchange page. A tracert by name and by IP show the
same successful results.
At first it looked like the unlucky ones were on a different ISP but I
have found at least one on the same ISP (even in the same sub-net) as
the customer that is getting the same failure.
What do I look at next?
Thanks.
Roger Vicker, CCP
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
